ZapSign icon

ZapSign

Interact with ZapSign API for digital signatures

Actions15

Overview

This node integrates with the ZapSign API to manage digital signature workflows. Specifically, the Signer - Get Many operation retrieves a list of signers associated with a given document. This is useful when you want to programmatically access all individuals who are assigned to sign a particular document, for example, to display their status or to trigger follow-up actions.

Practical scenarios include:

  • Fetching all signers of a contract document to check who has signed and who hasn't.
  • Auditing signer information before sending reminders.
  • Integrating signer data into other systems like CRMs or databases.

Properties

Name Meaning
Document ID The unique identifier of the document whose signers you want to retrieve.

Output

The output is an array of JSON objects, each representing a signer associated with the specified document. Each signer object typically includes details such as email, name, authentication method, and any additional metadata provided by the ZapSign API.

Example structure (fields may vary):

[
  {
    "email": "signer1@example.com",
    "name": "John Doe",
    "auth_method": "email",
    "require_doc_auth": false,
    "require_facial_recognition": false,
    ...
  },
  {
    "email": "signer2@example.com",
    "name": "Jane Smith",
    "auth_method": "sms",
    "phone_number": "+1234567890",
    ...
  }
]

No binary data is returned in 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 required beyond the API credential setup.

Troubleshooting

  • Common issues:

    • Invalid or missing Document ID: The operation requires a valid document identifier; ensure it is correctly provided.
    • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
    • Network or API downtime: Check connectivity and ZapSign service status if requests fail.

  • Error messages:

    • "Document not found": The provided Document ID does not exist or is inaccessible. Confirm the ID is correct.
    • "Unauthorized" or "Authentication failed": The API key is invalid or expired. Update credentials accordingly.
    • "Rate limit exceeded": Too many requests sent in a short time. Implement retry logic or reduce request frequency.

Links and References

Discussion