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 workflows, including templates, documents, signers, background checks, partnerships, timestamps, and webhooks. Specifically for the Template resource with the Get Many operation, it retrieves a list of document templates from the ZapSign platform.
This operation is useful when you want to fetch multiple templates available in your ZapSign account, for example, to display them, select one for document creation, or synchronize template data with another system.
Practical example:
- Fetching up to 50 templates to present options for creating new documents based on existing templates.
- Automating workflows that need to process or analyze all available templates.
Properties
| Name | Meaning |
|---|---|
| Limit | Maximum number of template results to return. This controls how many templates are fetched in one call. Default is 50. |
Output
The output is a JSON array containing the retrieved templates. Each item in the array represents a template object as returned by the ZapSign API's /api/v1/templates endpoint. The structure typically includes template metadata such as ID, name, creation date, and other relevant details defined 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 base URL for the API:
ZAPSIGN_API_BASE_URL_SANDBOX(optional sandbox URL)ZAPSIGN_API_BASE_URL(production URL fallback)
- The node makes HTTP GET requests to the ZapSign API endpoint
/api/v1/templateswith query parameters.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Network connectivity problems can prevent reaching the ZapSign API.
- Exceeding rate limits or quota restrictions imposed by ZapSign may result in errors.
- Providing an invalid limit value (e.g., less than 1) might cause request errors.
Error messages:
- If the API returns an error, it will be propagated as a node operation error.
- Typical HTTP errors like 400 (Bad Request) or 401 (Unauthorized) indicate configuration or credential issues.
- Ensure the API key has permissions to access templates.
Resolution tips:
- Verify the API key credential is correctly configured and active.
- Check network access and proxy settings if applicable.
- Confirm the limit parameter is a positive integer.
- Review ZapSign API documentation for any changes or additional requirements.
Links and References
- ZapSign API Documentation (official API docs, for detailed template endpoints and data structures)
- n8n Documentation on Creating Custom Nodes
- Environment Variables usage in n8n: Environment Variables
Note: This summary focuses exclusively on the Template resource's Get Many operation as requested, based on static analysis of the provided source code and property definitions.