Actions23
- Template Actions
- AI Tool Actions
- Form Actions
- Submission Actions
- Submitter Actions
Overview
The node integrates with the DocuSeal API to create document templates from PDF files. Specifically, the "Create From PDF" operation under the "Template" resource allows users to generate a new document template by uploading a PDF either as binary data from a previous node or by providing a URL to the PDF file.
This operation is useful in scenarios where you want to automate the creation of reusable document templates based on existing PDFs, for example:
- Automatically generating contract templates from signed PDF documents.
- Creating form templates from PDF brochures or flyers.
- Importing standardized PDF forms into DocuSeal for further processing and distribution.
Properties
| Name | Meaning |
|---|---|
| Input Source | Selects the source of the PDF file: - Binary File: Use a binary file from a previous node in the workflow. - URL: Use a PDF file accessible via a public URL. |
| Binary Property | (Shown if Input Source is "Binary File") The name of the binary property that contains the PDF file data from the input item. Default is "data". |
| File URL | (Shown if Input Source is "URL") The URL of the PDF file to use for creating the template. Must be a valid URL pointing to a PDF document. |
| Template Name | The name to assign to the newly created template. |
| Additional Fields | Optional additional settings for the template: - External ID: A custom identifier for the template. - Folder Name or ID: Folder location where the template should be stored. - Fields Configuration: Define form fields for the template, including field name, type (e.g., checkbox, date, image, initials, number, radio, select, signature, text), whether the field is required, and the role responsible for filling it. |
Output
The node outputs JSON data representing the created template object returned by the DocuSeal API. This typically includes details such as the template's unique ID, name, external ID, folder information, and configured fields.
No binary output is produced by this operation.
Dependencies
- Requires an active connection to the DocuSeal API using an API key or token credential configured in n8n.
- The node uses helper functions to prepare binary data and validate URLs.
- Network access is needed to upload binary files or fetch PDF files from URLs.
Troubleshooting
- Invalid file URL error: If the provided URL is not valid or inaccessible, the node will throw an error indicating the URL is invalid. Ensure the URL is correct, publicly accessible, and points directly to a PDF file.
- Missing binary data: When using the binary file option, ensure the specified binary property exists in the input data and contains valid PDF content.
- API request failures: Errors from the DocuSeal API (e.g., authentication issues, malformed requests) will be surfaced. Verify API credentials and input parameters.
- Empty or missing required fields: The template name is mandatory; omitting it will cause an error.
- Field configuration errors: If fields are provided, ensure they follow the expected structure with valid types and names.
Links and References
- DocuSeal API Documentation (for detailed API endpoints and payload formats)
- n8n Documentation on Binary Data Handling
- URL Validation Concepts