Overview
This node acts as a webhook trigger for DocuSeal events, allowing workflows in n8n to respond automatically when specific events occur within the DocuSeal platform. It listens for webhook calls from DocuSeal and can optionally fetch detailed submission data related to those events.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a document submission is completed.
- Tracking when a new submission is created to update internal systems.
- Responding to submitter interactions such as opening or completing forms.
- Integrating DocuSeal events into broader business processes without manual intervention.
For example, you could use this node to start a workflow that sends a notification email whenever a submission is completed or to log submission details into a CRM system.
Properties
| Name | Meaning |
|---|---|
| Environment | Choose between "Production" and "Test" environments to specify which DocuSeal environment to listen to. |
| Event Type | The specific DocuSeal event to listen for. Options: - All Events - Submission Completed - Submission Created - Submitter Completed - Submitter Opened |
| Additional Fields | Optional extra settings: - Include Full Submission Data (boolean): Whether to fetch full submission details when a submission event occurs. |
Output
The node outputs JSON data representing the webhook payload received from DocuSeal. If the option to include full submission data is enabled and a submission ID is present, it enriches the output with detailed submission information fetched via DocuSeal's API.
The output JSON structure includes at least the event data sent by DocuSeal, and optionally a submission_details field containing the full submission data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for DocuSeal with access to either the production or test environment.
- Needs network access to DocuSeal's API endpoint (
https://api.docuseal.com) to optionally fetch submission details. - The user must configure a webhook URL in their DocuSeal dashboard pointing to the URL provided by this node.
Troubleshooting
- Webhook not triggering: Ensure the webhook URL from the node is correctly set up in the DocuSeal dashboard under the Webhooks tab, and that the selected event type matches the events you want to receive.
- No data received or empty output: Verify that DocuSeal is sending events and that the event type filter in the node matches the incoming event.
- Failed to fetch submission details: This error may occur if the API key is invalid, lacks permissions, or network issues prevent reaching DocuSeal's API. Check credentials and network connectivity.
- Security considerations: If DocuSeal provides a signing secret for webhook validation, ensure it is configured properly outside this node to verify webhook authenticity.
Links and References
- DocuSeal API Documentation (for details on submission data and webhook setup)
- DocuSeal Dashboard — Webhook configuration section (accessible via your DocuSeal account)
This summary is based solely on static analysis of the provided source code and property definitions.