DocuSeal

Overview

The node integrates with the DocuSeal API to manage document submissions. Specifically, the Archive Submission operation deletes (archives) a submission by its ID. This is useful for workflows that need to clean up or logically remove submissions from active use after processing or when they are no longer needed.

Practical examples:

• Automatically archive a submission after it has been fully processed and signed.
• Clean up old or test submissions in bulk as part of maintenance workflows.
• Archive submissions based on external triggers or conditions in your automation.

Properties

Output

The output JSON contains the response from the DocuSeal API after attempting to archive the submission. Typically, this will be an empty object or confirmation of deletion. No binary data is returned by this operation.

Example output JSON:

{}

Dependencies

• Requires an API key credential for authenticating with the DocuSeal API.
• The node uses HTTP DELETE requests to the /submissions/{submissionId} endpoint.
• No additional environment variables are required beyond the API authentication setup.

Troubleshooting

• Invalid Submission ID: If the provided Submission ID does not exist or is invalid, the API may return an error. Ensure the ID is correct and corresponds to an existing submission.
• Authentication Errors: If the API key is missing or invalid, requests will fail. Verify the API credentials configured in n8n.
• Network Issues: Connectivity problems can cause request failures. Check network access to the DocuSeal API endpoint.
• API Rate Limits: Excessive requests might be throttled by the API. Implement retry logic or reduce request frequency if needed.

Common error message example:

• Failed to archive submission: <error message> — indicates the API call to delete the submission failed; check the error details for specifics.

Links and References

• DocuSeal API Documentation (generic link, replace with actual if available)
• n8n documentation on creating custom nodes