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, the Place Signatures operation for the Document resource allows users to programmatically place signature or initial ("rubrica") fields on an existing document at specified positions and pages.
This operation is useful when you have a document already uploaded or created in ZapSign and want to define exactly where each signer should sign or initial within the document. It supports multiple placements per document, each linked to a specific signer by their token.
Practical examples:
- Automatically placing signature fields on contracts before sending them out for signing.
- Adding initials ("visto") fields on specific pages of legal documents.
- Defining multiple signature spots for different signers on a multi-page agreement.
Properties
| Name | Meaning |
|---|---|
| Document Token | The unique token identifying the document on which signatures/initials will be placed. |
| Rubrics | A list of signature or initial placements, each specifying: |
| - Page (0-based index) where the signature/initial should appear. | |
| - Relative Position Bottom: vertical position relative to page bottom (percentage or unit). | |
| - Relative Position Left: horizontal position relative to page left (percentage or unit). | |
| - Relative Size X: width of the signature/initial field. | |
| - Relative Size Y: height of the signature/initial field. | |
| - Signer Token: token identifying the signer who must sign/initial at this placement. | |
| - Type: either "signature" or "visto" (initial). |
Output
The output JSON contains the response from the ZapSign API after placing the signatures. This typically includes confirmation details about the updated document and the signature placements.
No binary data output is produced 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). - Relies on internal helper functions for making HTTP requests and mapping signer entries.
Troubleshooting
- Missing Document Token: The operation requires a valid document token; ensure it is provided and correctly formatted.
- Invalid or Missing Signer Tokens in Rubrics: Each rubric must specify a signer token; missing tokens will cause the request to fail.
- API Errors: If the API returns errors, check that the document is in a state that allows placing signatures (e.g., not finalized or canceled).
- Positioning Issues: Incorrect relative positioning values may cause signatures to appear off-page or overlapping; verify coordinates carefully.
- Authentication Failures: Ensure the API key credential is valid and has permissions to modify the document.
Common error messages are generally passed through from the ZapSign API and should be interpreted according to their HTTP status codes and messages.
Links and References
- ZapSign API Documentation (official API docs for detailed parameters and responses)
- ZapSign Signature Placement Guide (if available, for understanding coordinate system and types)
If you need further details on other operations or resources, feel free to ask!