Skip to main content
arrow-left Back to Docusign.com

The Salesforce org I’m working in currently has DocuSign implemented via a URL Button that initiates DocuSign from the Quick Actions menu. I’m working to update that functionality to occur in a Salesforce Flow instead. I’d like the same functionality to fire automatically when the flow completes and populate the DocuSign envelope with variables from the flow.

My thought is this would need to be done in Lightning or Apex and called in the flow. I initially tried automatically firing the button on init, but Lightning doesn’t support URL buttons so it won’t fire as expected. Has anyone initialized DocuSign from a Flow before?

Hi Essio, I have recently implemented DocuSign in a flow! If you have it populate an iFrame from a call that is triggered when you reach the specific step in your flow. This is populated from a call sent to the backend, which takes your users credentials and send back the list of templates to choose from. If that template is predetermined, you can send the information from your flow in the request body to populate the templates variables that have been set via tab names. You can refer to the DocuSign Documentation for aligning the tab names to get your users data to autofill.

https://developers.docusign.com/docs/esign-rest-api/reference/templates/templaterecipienttabs/

This is my experience from using the REST API as an ISV.

Happy Coding! 

Thank you for the suggestion, ENateTheGreat! I may look into this next - currently trying to use DocuSign’s invokable action in the flow. Have you used that before?

The problem we are facing is it doesn't populate the fields in the document like the URL button currently does. 

The flow action has two input fields: Envelope Template ID and Source Id. 

I initially put in the DocuSign template ID in the first input, but that threw an exception, so I switched that to the Salesforce ID of the template ID and that seemed to accept it as a valid input. We are invoking from the Task ID so I'm populating the Source Id input with the Task ID variable. It fires the DocuSign notification, but when the document is pulled up, none of the merge field values are present. 

Any thoughts on why the document is not pre-populating? Am I putting in the right inputs into the Action?

Thanks!

Of course! While I don’t have experience with this particular implementation, document pre-population comes from the created envelope. Through a little research, it seems like you need to create a Salesforce Data Mapping that pairs the object with the field to match up the template tab label and the recipient/signer role. Then you attach the data mapping to the template, and DocuSign should autofill the template tabs from the source ID record. 

 

  • Make sure the source ID points to the right object
  • Make sure the template is addressable from the source ID

Hope this helps! Making sure the recipient/signer role names match verbatim is super important!

Code of ConductAccessibility statement

Docusign Community

Code of Conduct