Actions23
- Template Actions
- AI Tool Actions
- Form Actions
- Submission Actions
- Submitter Actions
Overview
This node integration with DocuSeal allows users to create and manage document submissions, specifically enabling the creation of a submission from raw HTML content. It is useful in scenarios where you want to generate a document dynamically from HTML markup and send it out for signing or filling by designated submitters.
Typical use cases include:
- Automating contract generation from HTML templates.
- Creating custom forms or agreements on the fly using HTML content.
- Sending documents to multiple parties for electronic signatures or data entry.
For example, you can provide an HTML string representing a contract, specify the people who need to sign or fill it, pre-fill some fields, and then send it out for completion.
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 details include name, phone, external ID, metadata, notification preferences (send email/SMS), completion status, and pre-filled fields specific to that submitter. |
| Field Values Input Mode | How to define field values to pre-fill in the document: either as individual fields (name-value pairs) or as a single JSON object mapping field names to values. |
| Field Values | When using "Individual Fields" mode, this is a collection of field name and value pairs to pre-fill in the document template. |
| Field Values JSON | When using "JSON Object" mode, this is a JSON object defining all field values with keys as field names and values as their corresponding pre-fill values. |
| HTML Content | The actual HTML content string used to create the submission document. This is required for the "Create From HTML" operation. |
| Additional Options | Various optional settings for the submission, including: • BCC Completed: Email address to BCC when submission completes. • Completed Redirect URL: URL to redirect submitters after completion. • Expire At: Date/time when the submission expires. • External ID: Custom identifier for the submission. • Message: Custom email subject and body with variables. • Metadata: Additional JSON metadata. • Order: Signing order ("Random" or "Sequential"). • Reply To: Reply-to email for notifications. • Send Email: Global toggle for sending email notifications. • Send SMS: Global toggle for sending SMS notifications. |
Output
The node outputs a JSON object representing the created submission returned by the DocuSeal API. This typically includes details such as submission ID, status, submitters info, and other metadata about the created submission.
No binary output is produced by this operation.
Dependencies
- Requires an active connection to the DocuSeal API via an API key credential configured in n8n.
- The node uses internal helper functions to prepare submitter arrays and field values, and to format dates.
- Network access to DocuSeal endpoints is necessary.
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 HTML content: The HTML content must be a valid string; otherwise, the API may reject the request.
- Field values building errors: Errors can occur if the field values input is malformed JSON or incorrectly structured. Validate your JSON or individual field entries.
- API request failures: Network issues or invalid credentials will cause request failures. Check your API key and network connectivity.
- Invalid date formats: For expiration dates, ensure the date/time is correctly formatted as expected by the API.
Links and References
- DocuSeal API Documentation (general reference for API endpoints)
- n8n Documentation - Creating Custom Nodes
- HTML Forms and Document Generation Concepts
This summary focuses on the "Submission" resource and the "Create From HTML" operation, describing how to configure the node inputs and what output to expect.