Javascript required
Skip to content Skip to sidebar Skip to footer
Home / How to Upload Completed Documents to Docusign

How to Upload Completed Documents to Docusign

Employ this action to upload a PDF or Discussion document to catechumen to a DocuSign envelope, and request signatures from one or more signers

Use case

Similar to the DocuSign: Send an Envelope from a Template activeness, this activeness is used primarily for Hour and legal purposes. The difference being that DocuSign: Upload and Transport a Certificate for Signatures does non utilize an existing DocuSign template and is most often used for documents generated inside a Catalytic instance.

How to configure this action

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

In one case the certificate has been tagged and completed, DocuSign volition then transport the envelope to all recipients for signature.

Access to this action requires a preconfigured DocuSign integration, which tin can exist setup through our Integrations page. For more information on integrating Catalytic with other systems, delight refer to the Integrations section of our help documentation.

Fields for this action

  • Integration

    • Select from a listing of all DocuSign integrations already authorized through the Integrations folio.

  • Assign To

    • E-mail address of the private to tag necessary fields. Tin be text or a {{field-names}} reference
    annotation
    • Annotation: If the e-mail accost defined in Assign To is associated with a Catalytic account, the Catalytic task to tag the document will be a transmission i assigned to that name. Otherwise, the task will be a spider web grade and a link volition be sent to the electronic mail address.

  • File

    • PDF or Word document to create the DocuSign envelope from
      • To apply a pre-uploaded file, enter the alphanumeric ID (plant at the cease of the file URL after /files/)
      • To use a file uploaded or generated during an case, 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 proper noun for the file afterwards it is signed.
    • If left blank, the new file volition accept the same name as the original file, with "Signed" added to the terminate of the name.
    • 💡Tip: The file extension will exist added to this name and does not need to be included.

  • Signer i (2, 3) Proper name

    • Name of the starting time recipient to sign documents. Can be text, a {{field-names}} reference, multiple {{field-names}}references, or any combination of the above
    • Add upwards to three signer name and emails. Signers two and iii 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 two and iii are optional.

  • Carbon Copy 1 (2, 3) Name

    • Past default, a copy of the signed DocuSign envelope is emailed to all signers. To add additional recipients of the signed envelope, include upward to three carbon copy proper noun and emails.

  • Carbon Re-create 1 (ii, 3) Electronic mail

    • 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 re-create name and emails.

  • Output Field Prefix

    • To help go on output fields organized, cull an output field prefix to add to the outset of each output field proper noun as this action may output more than 1 field.
    • The step's name is used every bit the prefix by default.

What will this output?

The activeness volition not exist marked complete until all recipients have signed the documents.

This action may generate multiple fields. To help go along output fields organized, the prefix higher up will exist added to the offset of each of the output field names, separated by ii dashes. Each field will upshot every bit:{{output-field-prefix--output-field}}. Learn more than

Output fields for this action

  • Signed Document

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

  • EnvelopeID

    • The unique ID for this envelope, for case: 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 total list, encounter DocuSign's Envelope Condition article.

  • Condition

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

  • Signer ane (ii, 3) Status

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

  • Signed certificate name

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

Thanks for your feedback

We update the Help Centre daily, so await changes soon.

Link Copied

Paste this URL anywhere to link straight to the department.

kavelmesee1973.blogspot.com

Source: https://help.catalytic.com/docs/docusign-upload-and-send-a-document-for-signatures/