Platform Events

considering you've already gone through docid\ rknln6uow5ow7m1aji6xq section of the documentation, this article will walk you through on how to subscribe to the cldfs cloudfiles event e event, and handle custom logic based on the event type if you've set the `cloudfiles event mode` setting to custom object, go through this article docid\ f v813 cz spqtnq1mw39 basic example trigger cloudfileseventtrigger on cldfs cloudfiles event e (after insert) { //output from geteventdetails list\<cldfs event> returnedevents = new list\<cldfs event>(); //inputs for geteventdetails list\<cldfs geteventdetails flowinput> geteventdetailinputs = new list\<cldfs geteventdetails flowinput>(); //input mapping for geteventdetails for(cldfs cloudfiles event e pe trigger new){ cldfs geteventdetails flowinput singleinput = new cldfs geteventdetails flowinput(); singleinput event = pe; geteventdetailinputs add(singleinput); } //get the event details returnedevents = cldfs geteventdetails geteventdetails(geteventdetailinputs); //process the returned events for(cldfs event e returnedevents){ if(e type == 'document processed'){ system debug('context ==> '+e documentprocessed context); system debug('processed document id ==> '+e documentprocessed processeddocumentid); system debug('processed file details ==> '+e documentprocessed file); } } } apex types for different platform event types line #21 in the example above displays outputs from the docid\ cbqw1iswhv8m ia49ryw event type(i e type number 14 in the list below) depending on your use case, here are the avilable platform event types and their custom apex types that you may use to access relevant information file uploaded docid\ rfrm0ccefnamauhq fj6x file replaced docid\ hmo1wqywiwkrvyegg1hbm salesforce file attached docid\ paouzfslqyfj1r2cpal6a salesforce file copied docid\ mck 6dm yjpvb3ku dzbj folder created docid\ a3 5ipjrcz2hyrozufkvs resource updated docid\ taj9r2evot2fyqtt9viiy content version created docid\ dactalz0owhdo4hgdza4m content version created batch docid\ wput3qqi82o5iuxv hegn file received docid\ fbfquz7bvioclhlke vjg resource attached docid\ sxyta6nleryqqykb60pob document generated docid\ syr eisyvmxipl 2rozje resource cloned docid\ qfvxwwbn8bu71vaxihorr file viewed docid 7vdtenfvihudbxovlaxlk document processed docid\ cbqw1iswhv8m ia49ryw document split docid\ n8qb7lhs9tpldgpju jiz resource deleted docid\ g0m1wfdgbj7jgbxarytqv error event docid omxqz0brj2bv7twjulvh for further information on what each of these event types signify, go through the docid 85vg5ndkui9u58vkafhw3 section of the documentation