DocuSign: Upload and Send a Document for Signatures

Use this action to upload a PDF or Word document to convert to a DocuSign envelope, and request signatures from one or more signers

Use case

Similar to the DocuSign: Send an Envelope from a Template action, this action is used primarily for HR and legal purposes. The difference being that DocuSign: Upload and Send a Document for Signatures does not use an existing DocuSign template and is most often used for documents generated within a PagerDuty Workflow Automation instance.

How to configure this action

This action converts a PDF or Word document into a DocuSign envelope for recipients to sign. Prior to sending to recipients for signing, a PagerDuty Workflow Automation task is assigned to the individual defined in Assign To prompting them to tag the document.

Once the document has been tagged and completed, DocuSign will then send the envelope to all recipients for signature.

Access to this action requires a preconfigured DocuSign integration, which can be setup through our Integrations page. For more information on integrating PagerDuty Workflow Automation with other systems, please refer to the Integrations section of our help documentation.

Fields for this action

• Integration

  • Select from a list of all DocuSign integrations already authorized through the Integrations page.

• Assign To

  • Email address of the individual to tag necessary fields. Can be text or a {{field-names}} reference

  note

  • Note: If the email address defined in Assign To is associated with a PagerDuty Workflow Automation account, the PagerDuty Workflow Automation task to tag the document will be a manual one assigned to that name. Otherwise, the task will be a web form and a link will be sent to the email address.

• File

  • PDF or Word document to create the DocuSign envelope from
    • To use a pre-uploaded file, enter the alphanumeric ID (found at the end of the file URL after /files/)
    • To use a file uploaded or generated during an instance, enter the file’s field name reference in {{field-names}} format

• Subject

  • Subject line of the email containing the documents to sign

• Signed document name

  • Enter a name for the file after it is signed.
  • If left blank, the new file will have the same name as the original file, with “Signed” added to the end of the name.
  • 💡   Tip: The file extension will be added to this name and does not need to be included.

• Signer 1 (2, 3) Name

  • Name of the first recipient to sign documents. Can be text, a {{field-names}} reference, multiple {{field-names}}references, or any combination of the above
  • Add up to 3 signer name and emails. Signers 2 and 3 are optional.

• Signer 1 (2, 3) Email

  • Email address of the first recipient to sign documents, can be text or a {{field-names}} reference
  • Add up to 3 signer name and emails. Signers 2 and 3 are optional.

• Carbon Copy 1 (2, 3) Name

  • By default, a copy of the signed DocuSign envelope is emailed to all signers. To add additional recipients of the signed envelope, include up to 3 carbon copy name and emails.

• Carbon Copy 1 (2, 3) Email

  • By default, a copy of the signed DocuSign envelope is emailed to all signers. To add additional recipients of the signed envelope, include up to 3 carbon copy name and emails.

• Output Field Prefix

  • To help keep output fields organized, choose an output field prefix to add to the beginning of each output field name as this action may output more than one field.
  • The step’s name is used as the prefix by default.

What will this output?

The action will not be marked complete until all recipients have signed the documents.

This action may generate multiple fields. To help keep output fields organized, the prefix above will be added to the beginning of each of the output field names, separated by two dashes. Each field will result as:{{output-field-prefix--output-field}}. Learn more

Output fields for this action

• Signed Document

  • The final signed document. This field will not use the output field prefix. The name of the file will be whatever was set during configuration.

• EnvelopeID

  • The unique ID for this envelope, for example: 7e5bd754-357b-4f7b-b368-3ec2fc280b56

• EnvelopeStatus

  • The envelope status indicates a more specific state for the DocuSign envelope. For example, Sent, Delivered, Waiting for Others, Needs to Sign, or Needs to View.
  • For a full list, see DocuSign’s Envelope Status article.

• Status

  • The status of the request. For example, Running, or Completed.

• Signer 1 (2, 3) Status

  • The status of each requested signer. For example, Sent, Completed, or Declined.

• Signed document name

  • The signed document converted into a PDF. Signatures are added at the end of the PDF.