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 digital document templates and related operations. Specifically, for the Template resource and the Create Template (DOCX) operation, it allows users to create a new document template by uploading a DOCX file either via a public URL or as a Base64-encoded string. The created template can then be used to generate documents with dynamic fields for signing workflows.
Common scenarios where this node is beneficial include:
- Automating the creation of reusable document templates for contracts, agreements, or forms.
- Centralizing template management in automated workflows.
- Preparing templates with branding and configuration options before sending documents for signature.
Practical example:
- A company wants to automate contract generation. They upload a branded DOCX template once using this node, then use other operations to create personalized documents from that template for each client.
Properties
| Name | Meaning |
|---|---|
Document Name (name) |
Optional name for the template document. Helps identify the template in the system. |
Template Additional Fields (templateAdditionalFields) |
Collection of optional settings for the template, including: - Language for the document interface ( lang): Portuguese (Brazil), English, Spanish - Disable automatic signer emails - Brand logo URL - Brand primary color (RGB/hex) - Brand name for emails (max 100 chars) - External ID for your application - Folder path in ZapSign (auto-creates missing folders) - Signature deadline date - Enable signature order - Reminder interval in days - Allow signer refusal - Creator email - Flags controlling signer permissions and notifications - Folder token (overrides folder path if provided) |
DOCX Source (docxSource) |
How to provide the DOCX content: - Public URL ( url) - Base64 string ( base64) |
DOCX URL (docxUrl) |
When docxSource is url, the public URL to the DOCX file (max 10MB). Must be accessible publicly. |
DOCX Base64 (docxBase64) |
When docxSource is base64, the Base64-encoded content of the DOCX file (without data prefix). |
Output
The node outputs an array of JSON objects representing the response from the ZapSign API after creating the template. This typically includes details such as the template ID, name, creation timestamps, and any metadata or status information returned by the API.
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 API base URL, supporting sandbox and production environments.
- The DOCX file must be accessible either via a public URL or provided as Base64 content.
- Network access to ZapSign API endpoints is required.
Troubleshooting
- Invalid or missing DOCX content: Ensure the DOCX file is correctly provided either as a valid public URL or a proper Base64 string without prefixes.
- File size limits: The DOCX file must not exceed 10MB.
- Authentication errors: Verify that the API key credential is valid and has appropriate permissions.
- Invalid additional fields: Check that optional fields like colors are in correct format (e.g., hex color codes), and dates follow the YYYY-MM-DD format.
- API errors: If the API returns a 400 Bad Request, review the request parameters for missing or invalid values.
- Folder path issues: If specifying a folder path, ensure it does not exceed length limits and uses valid characters; missing folders will be auto-created but deep nesting may cause issues.
- Network issues: Confirm network connectivity to the ZapSign API endpoints.
Links and References
- ZapSign API Documentation (official API docs for templates and document management)
- ZapSign Node on n8n Community
If you need further details about other operations or resources, feel free to ask!