Actions15
Overview
This node integrates with the ZapSign API to manage digital signature workflows. Specifically, the Document - Download operation allows users to download a signed document by its ID. This is useful in scenarios where you need to retrieve the final signed PDF file after all parties have signed it.
Practical examples include:
- Automatically downloading signed contracts or agreements for storage or further processing.
- Fetching completed documents to attach them to customer records or send via email.
- Archiving signed documents in cloud storage or document management systems.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document to download. |
Output
The output contains two main parts:
json: An object with the following fields:documentId: The ID of the downloaded document.downloaded: A boolean flag indicating that the document was successfully downloaded (true).
binary: Contains the actual PDF file data of the signed document under the propertydata. This binary data represents the downloaded signed document in PDF format.
Dependencies
- Requires an active connection to the ZapSign API using an API key credential configured in n8n.
- The node uses authenticated HTTP requests to interact with the ZapSign API endpoints.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Document ID: Ensure the Document ID provided exists and is correct.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity and ZapSign service status.
Error messages:
- If the document is not found, the API may return a 404 error. Confirm the Document ID.
- Permission denied or unauthorized errors indicate issues with the API key.
- Binary data preparation errors could occur if the response is not a valid PDF; ensure the document is signed and available for download.
Links and References
- ZapSign API Documentation (official API docs for detailed endpoint info)
- n8n Documentation on Binary Data Handling