Actions15
Overview
This node integrates with the ZapSign API to manage digital signature workflows for documents. Specifically, the Cancel Document operation allows users to cancel a document that has been previously created or sent for signature. This is useful in scenarios where a document needs to be invalidated or withdrawn before completion, such as when an error is found in the document or the signing process is no longer required.
Practical examples include:
- Canceling a contract that was mistakenly sent out.
- Stopping the signing process of a document due to changes in terms.
- Revoking a document before it is signed by all parties.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document to cancel. This is required to specify which document should be canceled. |
Output
The output JSON contains the response from the ZapSign API after attempting to cancel the document. Typically, this will include confirmation details about the cancellation status of the specified document.
Example structure (simplified):
{
"id": "string",
"status": "cancelled",
"updated_at": "timestamp",
...
}
No binary data is output for this 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 the 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 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:
"Document not found": The specified Document ID does not exist; verify the ID."Unauthorized"or"Authentication failed": The API key is invalid or expired; update credentials."Cannot cancel document": The document may already be completed or canceled; check document status before canceling.
Resolving these typically involves verifying input parameters, checking credentials, and ensuring the document is in a cancellable state.
Links and References
- ZapSign API Documentation (official API docs for detailed endpoint info)
- n8n Documentation (for general usage of custom nodes and credentials)