Actions15
Overview
This node integrates with the ZapSign API to manage digital signature workflows. It allows users to perform various operations on documents, signers, templates, and webhooks related to electronic signatures.
For the Document - Get operation specifically, the node retrieves detailed information about a single document by its ID. This is useful when you want to check the status, metadata, or other details of a specific document in your ZapSign account.
Common scenarios:
- Fetching the current status of a document to verify if it has been signed or completed.
- Retrieving document metadata for record-keeping or auditing purposes.
- Integrating document data retrieval into automated workflows that depend on document state.
Practical example:
You have sent a contract for signature and want to periodically check its status. Using this node's "Get Document" operation, you can fetch the latest document details and trigger subsequent actions based on whether the document is signed or still pending.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document to retrieve. This is required to specify which document's details to fetch. |
Output
The output JSON contains the full details of the requested document as returned by the ZapSign API. This typically includes fields such as:
- Document metadata (name, creation date, etc.)
- Current status (e.g., draft, sent, signed, cancelled)
- Signer information
- Other relevant document properties managed by ZapSign
If the operation succeeds, the output will be a JSON object representing the document.
No binary data is output for the "Get Document" operation.
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 ZapSign endpoints.
- No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Document ID: Ensure the Document ID provided exists and is correctly formatted.
- 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:
"Document not found": The specified Document ID does not exist. Double-check the ID."Unauthorized"or"Authentication failed": The API key may be invalid or expired. Reconfigure credentials.- Timeout or network errors: Retry after verifying network access.
To resolve errors, confirm input parameters, validate credentials, and consult ZapSign API documentation for error codes.
Links and References
- ZapSign API Documentation (official API docs for detailed endpoint info)
- n8n Documentation (for general usage of custom nodes and credentials)