DocuSeal is a platform that provides a powerful and easy-to-use API to implement eSignature workflows, allowing users to automate document and template management processes without relying on the web interface.
DocuSeal is a platform that provides a powerful and easy-to-use API to implement eSignature workflows, allowing users to automate document and template management processes without relying on the web interface. On Nagent, DocuSeal is exposed as a fully-configurable signatures integration that any agent can call — 22 actions, and API key authentication. No code is required to wire DocuSeal into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use DocuSeal to automate the kinds of tasks signatures teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire DocuSeal into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against DocuSeal, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCUSEAL_ARCHIVE_SUBMISSIONTool to archive a submission by its unique identifier. Archived submissions are not permanently deleted and can be restored.
Input parameters
The unique identifier of the submission to be archived
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_ARCHIVE_TEMPLATETool to archive a specific template by its unique identifier. Use after verifying the template ID.
Input parameters
The unique identifier of the template to be archived
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CLONE_TEMPLATE2Tool to clone an existing template into a new template with optional custom name, folder, and external_id. Use when you need to duplicate a template with specific customization options.
Input parameters
The unique identifier of the documents template to clone.
Template name. Existing name with (Clone) suffix will be used if not specified.
Your application-specific unique string key to identify this template within your app.
The folder's name to which the template should be cloned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CREATE_SUBMISSIONTool to create signature requests (submissions) from an existing document template and send them to submitters. Use this when you have a pre-configured template and want to send it for signing to one or more parties. Supports email and SMS notifications, custom messages, field pre-filling, and sequential or simultaneous signing workflows.
Input parameters
Order in which submitters should sign the document.
Custom email message for signature request.
Reply-To email address for signature request notification emails.
Set to true to send signature requests via SMS. Default is false.
Expiration date and time after which the submission becomes unavailable for signing. Format: ISO 8601 or 'YYYY-MM-DD HH:MM:SS TZ'.
Set to false to disable signature request emails. Default is true.
List of submitters (signers) for the submission. At least one submitter is required.
The unique identifier of the template to create a submission from. Templates must be created in advance via the Web UI or API.
BCC email address to receive a copy of completed signed documents.
URL to redirect submitters to after they complete signing.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CREATE_SUBMISSION_FROM_DOCXTool to create a one-off submission (signature request) from a DOCX document with dynamic content variables. Use \[\[variable_name\]\] text tags in the DOCX to define dynamic content variables and {{Field Name;role=Signer1;type=date}} text tags to define fillable fields. This allows you to generate personalized documents with pre-filled content and signature fields extracted from the DOCX file.
Input parameters
DOCX file to upload for the submission. Either 'docx' or 'docx_url' or 'documents' must be provided.
Name for the submission document. If not provided, the DOCX filename or 'document.docx' will be used.
Order in which submitters should sign: 'preserved' (in order) or 'random' (any order). Defaults to 'preserved'.
Custom email message content.
Public URL to a downloadable DOCX file. Either 'docx' or 'docx_url' or 'documents' must be provided. The URL must be publicly accessible.
Reply-to email address for notification emails
Whether to send SMS notifications to submitters
Array of documents with name and file (base64 or URL). Use this for multi-document submissions. Either 'docx' or 'docx_url' or 'documents' must be provided.
ISO 8601 datetime when the submission expires (e.g., '2024-12-31T23:59:59Z')
Dynamic content variables object. Use \[\[variable_name\]\] text tags in DOCX to define variables. Variable values can be strings, numbers, arrays, objects, or HTML content for styled text, paragraphs, and tables.
Whether to send email notifications to submitters. Defaults to true.
List of submitters (signers) for the document. At least one submitter with email or phone is required.
Pass false to disable the removal of {{text}} tags from the PDF. This can be used along with transparent text tags for faster and more robust PDF processing. Defaults to true.
Array of template IDs to use in the submission along with the provided documents. Use this to create multi-document submissions when some documents exist within templates.
Email address to BCC when the submission is completed
Set true to merge the documents into a single PDF file. Defaults to false.
URL to redirect the submitter to after signing is completed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CREATE_SUBMISSION_FROM_HTMLTool to create a one-off submission request from HTML content with embedded field tags rendered as a fillable and signable form. Use this when you want to create a signature request directly from HTML without first creating a reusable template. Field tags in HTML (like {{field_name}} or <signature-field>) will be automatically converted to fillable form fields.
Input parameters
Name for the submission
Order in which submitters should sign the document.
Custom email message for submission request.
Reply-to email address for notification emails
Whether to send SMS notifications to submitters. Defaults to false in API.
List of HTML documents to include in the submission. Each document can have embedded field tags. At least one document required.
Expiration date and time after which submission becomes unavailable. Format: 'YYYY-MM-DD HH:MM:SS UTC'
Whether to send email notifications to submitters. Defaults to true in API.
List of submitters (signers) who will fill and sign the document. At least one submitter required.
Optional array of template IDs to include in the submission along with HTML documents for multi-document submissions
Email address to BCC when the submission is completed by all parties
Set true to merge all documents into a single PDF file. Defaults to false.
URL to redirect submitters to after they complete signing
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CREATE_SUBMISSION_FROM_PDFTool to create a one-off submission (signature request) from a PDF file. Use this to upload a PDF document and send it for electronic signature without creating a reusable template first. You can define signature fields and other form fields either by using text tags in the PDF (e.g., {{Signature;role=First Party;type=signature}}) or by specifying field coordinates in the request.
Input parameters
PDF file to upload for the submission. Either 'pdf' or 'pdf_url' must be provided.
Name for the submission document. If not provided, the PDF filename or 'document.pdf' will be used.
Order in which submitters should sign: 'preserved' (in order) or 'random' (any order). Defaults to 'preserved'.
List of field definitions with coordinates. Use this to specify where signature, text, and other fields should appear. Alternatively, you can use text tags in the PDF like {{Field Name;role=First Party;type=signature}}
Custom email message with 'subject' and 'body' keys
Public URL to a downloadable PDF file. Either 'pdf' or 'pdf_url' must be provided. The URL must be publicly accessible.
Reply-to email address for notification emails
Whether to send SMS notifications to submitters
ISO 8601 datetime when the submission expires (e.g., '2024-12-31T23:59:59Z')
Whether to send email notifications to submitters. Defaults to true.
List of submitters (signers) for the document. At least one submitter with email or phone is required.
Email address to BCC when the submission is completed
URL to redirect the submitter to after signing is completed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CREATE_SUBMISSIONS_FROM_EMAILSTool to create submissions for a document template and send them to specified email addresses. Use this for simplified submission creation with Zapier or other automation tools. Each email address will receive a unique submission link.
Input parameters
A comma-separated list of email addresses to send the submission to.
Custom email message for signature request.
Set false to disable signature request emails sending. Defaults to true.
The unique identifier of the template to create submissions from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CREATE_TEMPLATE_FROM_DOCXTool to create a fillable document template from a Microsoft Word DOCX file. Use when you need to convert a DOCX document with field tags into a template.
Input parameters
Name for the created template. If not provided, a name will be auto-generated.
Array of DOCX documents to create the template from. Each document must have a name and file (base64 or URL). Use {{Field Name;role=Signer1;type=date}} text tags in the DOCX to define fillable fields.
Application-specific unique identifier. If a template with this external_id already exists, it will be updated with the new document.
Folder name to create the template in. If the folder doesn't exist, it will be created.
Set to true to make the template available via a shared link. This allows anyone with the link to create a submission from this template.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CREATE_TEMPLATE_FROM_HTML2Tool to create a fillable document template from HTML content with pre-defined fields. Use when you need to create a template directly from HTML with custom field tags for text, signatures, dates, and other fillable elements.
Input parameters
HTML template with field tags. Use custom HTML tags for fillable fields: <text-field>, <signature-field>, <date-field>, <initials-field>, <checkbox-field>, <image-field>, <file-field>, <select-field>, <radio-field>, <cells-field>, <stamp-field>, <payment-field>. Field attributes: name (field name), role (submitter role, e.g., 'First Party'), required (true/false), default (default value), readonly (true/false), style (CSS for sizing/positioning). Either html or documents parameter is required (not both).
Name of the template. A random UUID will be assigned if not specified.
Page size options for the document template.
Array of documents with HTML content. Use this to create a template with multiple documents. Leave empty when using the top-level html parameter for a single document template. Either html or documents parameter is required (not both).
Your application-specific unique string key to identify this template within your app. If provided and matches an existing template, that template will be updated with the new HTML.
Folder name to create the template in. Folder will be created if it doesn't exist.
HTML template of the footer to be displayed on every page.
HTML template of the header to be displayed on every page.
Set to true to make the template available via a shared link. This allows anyone with the link to create a submission from this template. Defaults to true.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_CREATE_TEMPLATE_FROM_PDFTool to create a fillable document template from a PDF file. Use when you need to create a reusable template from a PDF. Fields can be defined using {{Field Name;role=Signer1;type=date}} text tags in the PDF or by specifying pixel coordinates.
Input parameters
Name for the created template. If not provided, a default name is assigned.
Set to true to remove PDF form fields from the documents. This is useful for PDFs that have existing form fields that you want to replace with DocuSeal fields. Defaults to false.
Array of PDF documents to include in the template. Each document must have a name and either a 'file' (URL or base64) or 'pdf' property. Use text tags like {{Field Name;role=Signer1;type=date}} in the PDF or provide field coordinates.
Your application-specific unique string key to identify this template within your app. If a template with this external_id already exists, it will be updated with the new PDF instead of creating a duplicate.
Name of the folder to place the template in. The folder will be created if it doesn't exist.
Set to false to disable the removal of {{text}} tags from the PDF after processing. This can be used with transparent text tags for faster PDF processing. Defaults to true (tags are removed).
Set to true to make the template available via a shared link that allows anyone with the link to create a submission. Defaults to true.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_GET_SUBMISSIONTool to retrieve detailed information about a specific submission. Use when you need to fetch complete submission details including submitters, documents, status, template, events, and metadata.
Input parameters
The unique identifier of the submission.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_GET_SUBMISSION_DOCUMENTSTool to retrieve documents for a submission. Returns partially filled documents if the submission is in progress, or final signed documents if completed. Use when you need to download submission documents.
Input parameters
The unique identifier of the submission. You can get submission IDs from the List Submissions action.
When true, merges all documents into a single PDF. Returns individual documents when false or omitted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_GET_SUBMITTERTool to retrieve detailed information about a submitter by ID. Use when you need to fetch submitter details including documents, field values filled by the signer, submission events, and status.
Input parameters
The unique identifier of the submitter to retrieve. You can get submitter IDs from the List Submitters action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_GET_TEMPLATETool to retrieve details of a specific template by its unique identifier. Use when you need to fetch template metadata by ID.
Input parameters
The unique numeric identifier of the template to retrieve. You can get template IDs from the List Templates action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_LIST_SUBMISSIONSList document submissions with filtering and cursor-based pagination. Use to retrieve, search, and browse existing submissions by template, status, or submitter details. Supports searching by submitter name, email, or phone.
Input parameters
Search query to filter submissions by submitter name, email, or phone (partial match).
Filter submissions by unique submission slug.
Filter submissions with ID greater than this value (cursor-based pagination).
Maximum number of submissions to return (default: 10, max: 100).
Filter submissions with ID less than this value (cursor-based pagination).
Filter by submission status. Allowed values: 'pending', 'completed', 'declined', 'expired'.
If true, returns archived submissions. If false, returns active submissions only.
Filter submissions by a specific template ID.
Filter submissions by template folder name.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_LIST_SUBMITTERSRetrieve a paginated list of submitters with optional filtering. Use this tool to: - List all submitters across all submissions - Filter submitters by submission, status dates, or search query - Paginate through large result sets using 'after' and 'before' cursors Examples: - List all submitters: {} - Filter by submission: {"submission_id": 12345} - Search by email: {"q": "john@example.com"} - Get completed submitters in a date range: {"completed_after": "2024-01-01T00:00:00Z", "completed_before": "2024-12-31T23:59:59Z"} - Paginate results: {"limit": 50, "after": 3567000}
Input parameters
Search query to filter submitters by name, email, or phone (partial match supported)
Filter by unique submitter slug (e.g., 'zAyL9fH36Havvm')
Pagination cursor: return submitters with ID after this value. Use pagination.next from previous response.
Number of results per page (default: 10, max: 100)
Pagination cursor: return submitters with ID before this value
Filter by application-specific external identifier
Filter submitters by a specific submission ID
Filter submitters who completed after this date/time (ISO 8601 format, e.g., '2024-01-01T00:00:00Z')
Filter submitters who completed before this date/time (ISO 8601 format, e.g., '2024-12-31T23:59:59Z')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_LIST_TEMPLATES2Tool to retrieve a list of available document templates with pagination and filtering. Use when you need to search templates by name, slug, external_id, folder, or archived status.
Input parameters
Filter templates based on the name partial match. Search for templates whose names contain this string.
Filter templates by unique slug identifier.
Return templates with IDs greater than this value. Used for cursor-based pagination. Pass the ID from pagination.next to load the next batch.
Maximum number of templates to return. Default is 10; maximum is 100.
Return templates with IDs less than this value. Used for cursor-based pagination.
Filter templates by folder name.
If true, only archived templates are returned; if false or omitted, only active templates are returned.
The unique application-specific identifier provided for the template via API or Embedded template form builder. Filters templates with the specified external ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_MERGE_TEMPLATESMerge multiple DocuSeal templates into a single combined template. This action consolidates documents and fields from multiple source templates into one new template. Use this when you need to create a combined document package from existing templates. The merged template will contain all documents and fields from the source templates. Requires at least one template ID, but typically used with two or more.
Input parameters
Name for the merged template. If not provided, a default name will be generated.
Your application-specific identifier for the merged template.
Name of the folder where the merged template will be stored.
List of template IDs (integers) to merge into a single template. At least two template IDs are required.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_UPDATE_SUBMITTERTool to update submitter details, pre-fill or update field values, re-send signature request emails, or mark as auto-signed for automatic signing via API. Use when you need to modify submitter information, resend requests, or programmatically complete submissions.
Input parameters
The unique identifier of the submitter to update
The name of the submitter
The email address of the submitter
The phone number of the submitter, formatted according to E.164 standard
A list of configurations for template document form fields (required, readonly, default values, validation)
An object with pre-filled values for the submission. Use field names as keys. For more configurations see fields param.
Custom email message configuration for signature request.
Metadata object with additional submitter information
Specify Reply-To address to use in the notification emails
Set true to re-send signature request via phone number SMS
Pass true to mark submitter as completed and auto-signed via API
Set true to re-send signature request emails
Your application-specific unique string key to identify this submitter within your app
Set to true to require phone 2FA verification via one-time code sent to phone number to access documents
Submitter specific URL to redirect to after the submission completion
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_UPDATE_TEMPLATE2Tool to update a document template by moving it to a different folder, changing its name, updating submitter roles, or unarchiving it. Use when you need to modify template properties.
Input parameters
The unique identifier of the document template.
The name of the template
An array of submitter role names to update the template with.
Set `false` to unarchive template.
The folder's name to which the template should be moved.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCUSEAL_UPDATE_TEMPLATE_DOCUMENTSTool to add, remove, or replace documents in a template with provided PDF/DOCX file or HTML content. Use when you need to modify the document structure of an existing template.
Input parameters
The unique identifier of the template to update.
Set to true to merge all existing and new documents into a single PDF document in the template.
List of document updates to apply. Each item can add a new document, replace an existing one, or mark one for removal.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 74 agents privately built on Nagent that already use DocuSeal.
Build on Nagent
Connect DocuSeal to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find DocuSeal, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, DocuSeal is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once DocuSeal is connected, you configure its 22 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop DocuSeal steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a DocuSeal event fires, the agent kicks off automatically.
Every DocuSeal action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While DocuSeal ships with 22 pre-built signatures actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching DocuSeal together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build DocuSeal-based workflows tailored to your business.