Skip to content Skip to main navigation Skip to footer

Configure Opero Signature Automation

If you are using Opero Documents to generate the document being sent for signature. then you will automate with Opero Documents. Follow the instructions to configure the Document Action to auto send the document for signature here: https://kb.opero.com/signature/knowledge-base/using-opero-documents-with-opero-signature-for-full-automation/

If you are using Opero Signature only, you can use Flow or Apex, in combination with your business process, to create eSign Doc records.

Create an eSign Doc record and set the following required eSign Doc fields:

  • Google Doc ID – Id of the Google document that is being sent for signature,
  • Send To/Send To Lead – Id of the Salesforce contact or lead to which the document is being sent. Can be a field reference or hardcoded Id,
    • NOTE: Instead of setting Send To/Send To Lead, you can also set Email To and/or Email Name as the email address and name of the person to which you want to send the document. Just specify email address and a person’s full name as strings,
  • Email Template – Id of Salesforce email template used for email that will be sent. Find out how to configure an email template with proper merge fields in Configuring Email Templates section. If your template does not have the proper code to include the eSignature link, then this merge code will be automatically added to the email body. If template is selected then Email Subject and Email Body will be automatically set,
  • Created With Automation – flag used to specify that the eSign Doc record is created using configured automation, and not manually. Must be true if automating.

Apart from these fields, you can also set additional fields, according to your business needs and process:

  • Email CC – enter any other email addresses separated by a comma (no space in between email addresses) that you wish to CC,
  • Counter Sign Method
    • No Counter Sign Needed – default,
    • Counter Sign Required – select if you want this document to be counter signed by someone at the company after it is signed by the recipient,
    • Auto Counter Sign – automatically countersign the document after it’s signed by the recipient,
  • Counter Signed By – if you select Counter Sign Required or Auto Counter Sign, then you must select the user in your Salesforce org who needs to counter sign the document. You can select a user, specify user’s Id, or set a field reference,
  • Email Subject – if template was not selected, you can specify an email subject as a string,
  • Email Body – if template was not selected, you can type the email body manually (as plain text, or paste HTML code). If you choose to do this, make sure you have the eSignature link {!esign__Document__c.esign__eSign_Link__c} merged somewhere in the email body so the recipient can have the link to click to sign the document.  You can put this link in any way you want with link text like “Sign Here” or with an image button clicking to the link. See Configuring Email Templates section for examples.

You can set any related fields by specifying the Id or setting the field reference. For example, if you’re invoking the process from an Opportunity record and you want to relate eSign Doc to that Opportunity, you can set Opportunity field in Create a Record action.

You can also set any other writeable field from the eSign Doc object.