Actions33
- Template Actions
- Document Actions
- Signer Actions
- Background Check Actions
- Partnership Actions
- Timestamp Actions
- Webhook Actions
Overview
This node integrates with the ZapSign API to manage electronic document signing workflows. Specifically, for the Signer resource and the Detail operation, it retrieves detailed information about a signer using their unique token.
Typical use cases include:
- Fetching signer details to verify their status or attributes in a signing process.
- Auditing or reporting on individual signers within a document workflow.
- Integrating signer data into other systems or workflows after retrieval.
For example, you might use this node to get the current status, authentication method, or contact information of a signer identified by their token, enabling conditional logic or notifications based on that data.
Properties
| Name | Meaning |
|---|---|
| Signer Token | The unique token identifier of the signer whose details you want to retrieve. |
Output
The output is a JSON object containing detailed information about the specified signer. This typically includes fields such as the signer's name, email, authentication method, phone number, validation status, and any other metadata provided by the ZapSign API for that signer.
No binary data output is produced for 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_SANDBOXfor sandbox orZAPSIGN_API_BASE_URLfor production). - Relies on internal helper functions for making HTTP requests and processing responses.
Troubleshooting
- Missing or invalid Signer Token: The operation requires a valid signer token. If the token is missing or malformed, the API call will fail.
- API Authentication Errors: Ensure the API key credential is correctly configured and has permissions to access signer details.
- Network Issues: Failures to reach the ZapSign API endpoint may occur due to network problems or incorrect base URLs.
- Error Handling: If the signer token does not exist or is invalid, the API may return errors which the node surfaces. Check the error message for details.
Links and References
- ZapSign API Documentation (general reference for API endpoints and signer details)
- n8n documentation on creating custom nodes
Note: Internal credential names and implementation-specific identifiers have been omitted per guidelines.