ZapSign

Overview

This node integrates with the ZapSign API to manage digital document workflows, including creation, signing, updating, and validation of documents and their signatures. Specifically, for the Document - Validate Signatures operation, it allows users to upload a file (PDF or similar) and validate its embedded digital signatures.

Common scenarios where this node is beneficial include:

• Verifying the authenticity and integrity of signed PDF documents.
• Automating signature validation in document processing pipelines.
• Ensuring compliance by programmatically checking if documents have valid signatures before further processing.

Practical example:

• A company receives signed contracts as PDFs and wants to automatically verify that all required signatures are valid before archiving or triggering downstream workflows. This node can take the contract file as input and return validation results indicating whether the signatures are valid.

Properties

Output

The node outputs a JSON array where each item corresponds to the result of the signature validation request for an input file.

• The json output contains the response from the ZapSign API's signature validation endpoint.
• This typically includes details about the validity of the signatures found in the document, such as whether they are valid, invalid, or missing.
• The node does not output binary data for this operation; it only returns JSON metadata about the signature validation.

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_SANDBOX for sandbox environment (default: https://sandbox.api.zapsign.com.br)
  • ZAPSIGN_API_BASE_URL for production environment (default: https://api.zapsign.com.br)
• The node expects the input file to be provided as binary data in the specified binary property.

Troubleshooting

• Common issues:

  • The binary property specified does not exist or does not contain valid file data.
  • The file format is unsupported or corrupted, causing the API to fail validation.
  • API authentication errors due to missing or invalid API key credentials.
  • Network issues preventing access to the ZapSign API endpoint.

• Error messages and resolutions:

  • "Failed to download file from URL" — Occurs if the file URL is inaccessible or invalid. Ensure the URL is publicly accessible.
  • API errors related to bad requests — Check that the file is a valid PDF or supported format and that the binary data is correctly provided.
  • Authentication errors — Verify that the API key credential is configured properly in n8n.
  • If the node throws an error about missing binary data, confirm that the binary property name matches exactly and that the input data contains the file.

Links and References

• ZapSign API Documentation (general reference for API endpoints)
• ZapSign Signature Validation Endpoint (specific API docs for signature validation)

This summary focuses on the Document - Validate Signatures operation as requested, describing how the node processes a binary file input to validate its digital signatures via the ZapSign API.