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" or "Test" environment 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 | Collection of optional fields: - Include Full Submission Data (boolean): Whether to fetch full submission details when a submission event is received. |
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 an API call.
The output JSON structure includes at least the event data sent by DocuSeal, and optionally a submission_details field containing the full submission data.
If binary data were involved, it would be summarized here, but this node only handles JSON webhook payloads.
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 fetch submission details if requested. - 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 the selected event type matches the events you want to receive.
- No data received or empty payload: 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 occurs if the API key is invalid, missing, or lacks permissions, or if the submission ID is incorrect. Check the API credentials and ensure the environment setting matches the API key used.
- Security considerations: DocuSeal may provide a signing secret for webhook validation; users should implement verification outside this node if needed.
Links and References
- DocuSeal Webhooks Documentation (hypothetical link)
- n8n Webhook Trigger Nodes
- DocuSeal API documentation for fetching submission details (refer to your DocuSeal account resources)