DocuSeal icon

DocuSeal

Create documents, manage templates, and handle submissions with DocuSeal

Actions23

Overview

The "Create From PDF" operation in the Submission resource allows users to create a new document submission based on a PDF file. This node is useful when you want to send a PDF document for signing or filling by multiple submitters, automating workflows that involve document approvals, contracts, or form completions.

Typical use cases include:

  • Sending contracts or agreements as PDFs to multiple signers.
  • Automating document workflows where a PDF template is pre-filled and sent out.
  • Collecting signatures or data from clients or partners on a PDF document.

You can provide the PDF either as a binary file from a previous node or via a URL. The node supports specifying submitters with roles and contact details, pre-filling fields, and setting additional options like notifications and expiration.

Properties

Name Meaning
Submitters List of people who will sign or fill the document. Each submitter requires an email and role (e.g., Signer, Client). Additional optional fields include name, phone, metadata, external ID, completion status, notification preferences, and pre-filled fields.
Field Values Input Mode How to define field values to pre-fill in the document: either individually (one by one) or as a JSON object containing all field names and their values.
Field Values When using individual mode, specify each field's name and the value to pre-fill.
Field Values JSON When using JSON mode, provide a JSON object with field names as keys and their corresponding values.
Input Source Source of the PDF file: either a binary file from a previous node or a URL pointing to the PDF.
Binary Property (Required if Input Source is binary) The name of the binary property containing the PDF file.
File URL (Required if Input Source is URL) The URL of the PDF file to use.
Additional Options Various optional settings including:
• BCC Completed: Email address to BCC when submission completes.
• Completed Redirect URL: URL to redirect submitters after completion.
• Expire At: Expiration date/time.
• External ID: Custom identifier.
• Message: Custom email subject and body with variables.
• Metadata: Additional metadata.
• Order: Signing order (random/all at once or sequential).
• Reply To: Reply-to email for notifications.
• Send Email: Global email notification toggle.
• Send SMS: Global SMS notification toggle.

Output

The node outputs a JSON object representing the created submission. This typically includes details such as submission ID, status, submitters, and links related to the submission process.

If the node handles binary data (the PDF), it uses the binary property specified but the output mainly focuses on the submission metadata and status.

Dependencies

  • Requires an API key credential for authenticating with the DocuSeal service.
  • Needs access to the PDF file either as binary data from a previous node or a valid URL.
  • The node depends on helper functions to prepare binary data, validate URLs, build submitters array, and format dates.
  • No other external dependencies are required beyond the configured API credentials and network access to URLs if used.

Troubleshooting

  • At least one submitter is required: If no submitters are provided, the node throws an error. Ensure you add at least one submitter with a valid email and role.
  • Invalid file URL: If the URL provided for the PDF is invalid or unreachable, the node will throw an error indicating the URL problem. Verify the URL correctness and accessibility.
  • Failed to build field values: Errors in formatting or providing field values (either individually or JSON) can cause failures. Check the field names and JSON syntax carefully.
  • Missing binary property: When using binary input source, ensure the binary property name matches the actual binary data property from the previous node.
  • API errors: Network issues or authentication problems with the DocuSeal API will result in errors. Confirm your API key is valid and has necessary permissions.

Links and References

Discussion