CloudFiles Event Object

introduction on various actions related to files, cloudfiles publishes a salesforce platform event named cloudfiles event this event has following fields type type of the event for example file uploaded , folder created etc object type salesforce record type where the event originated example account, case etc do not use fields the data & request id fields are not useful under any circumstances contact us if you feel the need to use them below section gives more details on these event fields type field name cldfs type c this field provides information on the type of event published for example, a cloudfiles event is published whenever a salesforce file is attached to a salesforce record the event is also published whenever a file is uploaded in the cloudfiles widget (i e directly to sharepoint) the type field of this event is going to be salesforce file attached or file uploaded based on the reason of the event there are several types of events published you can find the exact text values for each event type in the respective articles these are indexed in docid 85vg5ndkui9u58vkafhw3 object type field name cldfs object type c this field provides information on the object on which the cloudfiles event or action is performed for example, for a salesforce file attached onto an account record, the object type field of the event is going to be object api name i e account use the salesforce object api name to filter using this field for event originated outside a record context, this field is null do not use fields the following fields should not be used by you in your implementation if you feel the need to use these fields in any way and you have explored all other alternatives, you should contact our team first these fields are not designed to be used by the implementation data data related to the event this field is used internally by the docid\ cfegghvnwso7bcxyevrr flow action to return the event details this does not represent the full event details which is actually returned by the get event details action refer to step 2 & 3 in the docid\ hbil pqlgbixyg81yse9g article request id exists when the event is published as a result of an asynchronous action this is not useful