Document Signed

overview this event is published when a document signing process is completed through docusign integration when you generate a document with docusign recipients and send it for signing, docusign processes the signing workflow and returns the final signed pdf to salesforce, automatically triggering this event how to use this event? to use cloudfiles events, you must first setup your flow as shown in the intercepting cloudfiles events article this article will introduce you to the concepts of the event type as well as event details that are returned by the get event details flow action once you are familiar with these, you will understand how to interpret & use these as illustrated in the sections below event type for decision filter please use document signed as the type filter when selecting this event in the decision element in flow builder output fields from get event details the corresponding get event details flow action returns the document signed details with the same structure as the document generated event, providing useful information including file resource , contentversionid, name and parent id for further use refer to the examples below for the output structure field structure file this field specifies the metadata details of the signed document file this parameter is populated only if the destination input parameter was configured in the original document genrated action (only in case of flows, the call automatically checks for recipient and docusign integration and triggers this action) if not, it will be null field details when saved in salesforce and linked to a record id the signed file's content document id library salesforce name the document name with " signed" suffix other fields will be null when saved in external storage contains metadata details of the file stored in the external storage contentversionid this is the content version id of the signed file if no destination parameter was specified in the original document generated action, the signed file is stored in the salesforce file library this field holds the content version id of the signed document in salesforce name the name of the signed document (typically includes " signed" suffix) recordid record id on which the original document was generated and to which the signed document is now linked docusign integration workflow the docusign integration follows this process document generation when a document is generated with docusign recipients specified, it is automatically prepared for the signing workflow send for signing manual trigger use the send for signing button in the doc gen widget or word template interface to initiate the docusign process flow action when generating documents via flow actions, the sending process is handled automatically without requiring the manual button step docusign processing docusign manages the signing workflow according to the recipient configuration completion callback once all required signatures are collected, docusign returns the final signed pdf to salesforce event trigger the document signed event is automatically triggered, allowing your flows to respond to the completion of the signing process important notes the signed document maintains a connection to the original record through the recordid field file naming convention automatically appends " signed" to distinguish the final document from the original while using docu sign, the file received after signing will always be a pdf, even if the file sent for signing has other file type