DocuSeal icon

DocuSeal

Create documents, manage templates, and handle submissions with DocuSeal

Overview

The node interacts with the DocuSeal API to manage document templates, including cloning existing templates. Specifically, the "Template - Clone" operation creates a copy of an existing template by specifying its ID and providing a new name for the cloned template. This is useful when you want to create a similar template without starting from scratch, preserving the original while making modifications on the clone.

Practical scenarios include:

  • Quickly duplicating a contract or form template to customize it for a different client or use case.
  • Creating backup copies of templates before making significant changes.
  • Generating multiple versions of a template with slight variations.

Properties

Name Meaning
Template ID The numeric ID of the existing template to be cloned.
Template Name The new name to assign to the cloned template.
Additional Fields Optional extra settings for the cloned template:
- External ID: A custom identifier for the template.
- Folder Name or ID: Specifies the folder where the cloned template should be placed.
- Fields Configuration: Allows defining form fields for the template, each with:
- Field Name: Name of the field.
- Field Type: Type of the field (Checkbox, Date, Image, Initials, Number, Radio, Select, Signature, Text).
- Required: Whether the field is mandatory.
- Role: Role responsible for filling this field.

Output

The output JSON contains the response from the DocuSeal API after cloning the template. Typically, this includes details of the newly created template such as its ID, name, external ID, folder information, and configured fields.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the DocuSeal API via an API key credential configured in n8n.
  • The node uses internal helper functions to prepare requests and handle binary data if needed (not applicable for clone).
  • Network access to DocuSeal's API endpoints is necessary.

Troubleshooting

  • Invalid Template ID: If the provided Template ID does not exist or is incorrect, the API will return an error. Verify the ID is correct.
  • Missing Required Fields: Both Template ID and Template Name are required. Omitting either will cause the node to throw an error.
  • API Request Failures: Network issues or invalid API credentials can cause request failures. Ensure the API key is valid and network connectivity is stable.
  • Invalid Additional Fields: Providing malformed or unsupported additional fields may result in errors. Double-check the structure and values of these fields.
  • Error Message Example: Failed to clone template: <error message> indicates the cloning process failed; check the error details for specifics.

Links and References

Discussion