Actions33
- Template Actions
- Document Actions
- Signer Actions
- Background Check Actions
- Partnership Actions
- Timestamp Actions
- Webhook Actions
Overview
The node integrates with the ZapSign API to manage electronic document signing workflows. Specifically, for the Signer resource and the Remove operation, it allows users to remove a signer from a document by providing the signer's unique token.
This operation is useful in scenarios where a signer was added by mistake, needs to be replaced, or should no longer participate in the signing process. For example, if a document was sent out for signature but one of the recipients is no longer authorized or available, this operation can remove that signer to prevent further actions from them.
Properties
| Name | Meaning |
|---|---|
| Signer Token | The unique token identifying the signer to be removed from the document. This is required. |
Output
- The output JSON contains the response from the ZapSign API after attempting to remove the signer.
- Typically, this will include confirmation of removal or details about the signer status.
- No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the ZapSign API.
- Uses environment variables to determine the base URL for the API (
ZAPSIGN_API_BASE_URL_SANDBOXorZAPSIGN_API_BASE_URL). - The node depends on internal helper functions for making HTTP requests and handling responses.
Troubleshooting
Common issues:
- Providing an invalid or expired signer token will cause the removal to fail.
- Network or authentication errors may occur if the API key is missing or incorrect.
- Attempting to remove a signer who has already completed signing or whose status disallows removal might result in errors.
Error messages:
- If the signer token is missing or empty, the node throws an error indicating the requirement.
- HTTP errors from the API (e.g., 404 Not Found) indicate the signer does not exist or cannot be found.
- Other API errors are logged and rethrown as node operation errors with descriptive messages.
Resolution tips:
- Verify the signer token is correct and corresponds to an active signer.
- Ensure the API key credential is valid and has necessary permissions.
- Check network connectivity and API endpoint configuration.
Links and References
- ZapSign API Documentation (general reference for API endpoints and signer management)
- n8n documentation on creating custom nodes for further customization guidance