# DocuSeal

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.

- **Category:** signatures
- **Auth:** API_KEY
- **Composio Managed App Available?** N/A
- **Tools:** 22
- **Triggers:** 0
- **Slug:** `DOCUSEAL`
- **Version:** 20260312_00

## Tools

### Archive Submission

**Slug:** `DOCUSEAL_ARCHIVE_SUBMISSION`

Tool to archive a submission by its unique identifier. Archived submissions are not permanently deleted and can be restored.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The unique identifier of the submission to be archived |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Archive Template

**Slug:** `DOCUSEAL_ARCHIVE_TEMPLATE`

Tool to archive a specific template by its unique identifier. Use after verifying the template ID.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier of the template to be archived |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Clone Template (v2)

**Slug:** `DOCUSEAL_CLONE_TEMPLATE2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The unique identifier of the documents template to clone. |
| `name` | string | No | Template name. Existing name with (Clone) suffix will be used if not specified. |
| `external_id` | string | No | Your application-specific unique string key to identify this template within your app. |
| `folder_name` | string | No | The folder's name to which the template should be cloned. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Submission

**Slug:** `DOCUSEAL_CREATE_SUBMISSION`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `order` | string ("preserved" | "random") | No | Order in which submitters should sign the document. |
| `message` | object | No | Custom email message for signature request. |
| `reply_to` | string | No | Reply-To email address for signature request notification emails. |
| `send_sms` | boolean | No | Set to true to send signature requests via SMS. Default is false. |
| `expire_at` | string | No | Expiration date and time after which the submission becomes unavailable for signing. Format: ISO 8601 or 'YYYY-MM-DD HH:MM:SS TZ'. |
| `send_email` | boolean | No | Set to false to disable signature request emails. Default is true. |
| `submitters` | array | Yes | List of submitters (signers) for the submission. At least one submitter is required. |
| `template_id` | integer | Yes | The unique identifier of the template to create a submission from. Templates must be created in advance via the Web UI or API. |
| `bcc_completed` | string | No | BCC email address to receive a copy of completed signed documents. |
| `completed_redirect_url` | string | No | URL to redirect submitters to after they complete signing. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Submission From DOCX

**Slug:** `DOCUSEAL_CREATE_SUBMISSION_FROM_DOCX`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `docx` | object | No | DOCX file to upload for the submission. Either 'docx' or 'docx_url' or 'documents' must be provided. |
| `name` | string | No | Name for the submission document. If not provided, the DOCX filename or 'document.docx' will be used. |
| `order` | string | No | Order in which submitters should sign: 'preserved' (in order) or 'random' (any order). Defaults to 'preserved'. |
| `message` | object | No | Custom email message content. |
| `docx_url` | string | No | 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` | string | No | Reply-to email address for notification emails |
| `send_sms` | boolean | No | Whether to send SMS notifications to submitters |
| `documents` | array | No | 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. |
| `expire_at` | string | No | ISO 8601 datetime when the submission expires (e.g., '2024-12-31T23:59:59Z') |
| `variables` | object | No | 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. |
| `send_email` | boolean | No | Whether to send email notifications to submitters. Defaults to true. |
| `submitters` | array | Yes | List of submitters (signers) for the document. At least one submitter with email or phone is required. |
| `remove_tags` | boolean | No | 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. |
| `template_ids` | array | No | 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. |
| `bcc_completed` | string | No | Email address to BCC when the submission is completed |
| `merge_documents` | boolean | No | Set true to merge the documents into a single PDF file. Defaults to false. |
| `completed_redirect_url` | string | No | URL to redirect the submitter to after signing is completed |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Submission From HTML

**Slug:** `DOCUSEAL_CREATE_SUBMISSION_FROM_HTML`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | Name for the submission |
| `order` | string ("preserved" | "random") | No | Order in which submitters should sign the document. |
| `message` | object | No | Custom email message for submission request. |
| `reply_to` | string | No | Reply-to email address for notification emails |
| `send_sms` | boolean | No | Whether to send SMS notifications to submitters. Defaults to false in API. |
| `documents` | array | Yes | List of HTML documents to include in the submission. Each document can have embedded field tags. At least one document required. |
| `expire_at` | string | No | Expiration date and time after which submission becomes unavailable. Format: 'YYYY-MM-DD HH:MM:SS UTC' |
| `send_email` | boolean | No | Whether to send email notifications to submitters. Defaults to true in API. |
| `submitters` | array | Yes | List of submitters (signers) who will fill and sign the document. At least one submitter required. |
| `template_ids` | array | No | Optional array of template IDs to include in the submission along with HTML documents for multi-document submissions |
| `bcc_completed` | string | No | Email address to BCC when the submission is completed by all parties |
| `merge_documents` | boolean | No | Set true to merge all documents into a single PDF file. Defaults to false. |
| `completed_redirect_url` | string | No | URL to redirect submitters to after they complete signing |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Submission From PDF

**Slug:** `DOCUSEAL_CREATE_SUBMISSION_FROM_PDF`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `pdf` | object | No | PDF file to upload for the submission. Either 'pdf' or 'pdf_url' must be provided. |
| `name` | string | No | Name for the submission document. If not provided, the PDF filename or 'document.pdf' will be used. |
| `order` | string | No | Order in which submitters should sign: 'preserved' (in order) or 'random' (any order). Defaults to 'preserved'. |
| `fields` | array | No | 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}} |
| `message` | object | No | Custom email message with 'subject' and 'body' keys |
| `pdf_url` | string | No | Public URL to a downloadable PDF file. Either 'pdf' or 'pdf_url' must be provided. The URL must be publicly accessible. |
| `reply_to` | string | No | Reply-to email address for notification emails |
| `send_sms` | boolean | No | Whether to send SMS notifications to submitters |
| `expire_at` | string | No | ISO 8601 datetime when the submission expires (e.g., '2024-12-31T23:59:59Z') |
| `send_email` | boolean | No | Whether to send email notifications to submitters. Defaults to true. |
| `submitters` | array | Yes | List of submitters (signers) for the document. At least one submitter with email or phone is required. |
| `bcc_completed` | string | No | Email address to BCC when the submission is completed |
| `completed_redirect_url` | string | No | URL to redirect the submitter to after signing is completed |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Submissions From Emails

**Slug:** `DOCUSEAL_CREATE_SUBMISSIONS_FROM_EMAILS`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `emails` | string | Yes | A comma-separated list of email addresses to send the submission to. |
| `message` | object | No | Custom email message for signature request. |
| `send_email` | boolean | No | Set false to disable signature request emails sending. Defaults to true. |
| `template_id` | integer | Yes | The unique identifier of the template to create submissions from. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Template from DOCX

**Slug:** `DOCUSEAL_CREATE_TEMPLATE_FROM_DOCX`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | Name for the created template. If not provided, a name will be auto-generated. |
| `documents` | array | Yes | 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. |
| `external_id` | string | No | Application-specific unique identifier. If a template with this external_id already exists, it will be updated with the new document. |
| `folder_name` | string | No | Folder name to create the template in. If the folder doesn't exist, it will be created. |
| `shared_link` | boolean | No | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Template from HTML

**Slug:** `DOCUSEAL_CREATE_TEMPLATE_FROM_HTML2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `html` | string | No | 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` | string | No | Name of the template. A random UUID will be assigned if not specified. |
| `size` | string ("Letter" | "Legal" | "Tabloid" | "Ledger" | "A0" | "A1" | "A2" | "A3" | "A4" | "A5" | "A6") | No | Page size options for the document template. |
| `documents` | array | No | 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). |
| `external_id` | string | No | 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` | string | No | Folder name to create the template in. Folder will be created if it doesn't exist. |
| `html_footer` | string | No | HTML template of the footer to be displayed on every page. |
| `html_header` | string | No | HTML template of the header to be displayed on every page. |
| `shared_link` | boolean | No | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Template From PDF

**Slug:** `DOCUSEAL_CREATE_TEMPLATE_FROM_PDF`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | Name for the created template. If not provided, a default name is assigned. |
| `flatten` | boolean | No | 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. |
| `documents` | array | Yes | 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. |
| `external_id` | string | No | 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. |
| `folder_name` | string | No | Name of the folder to place the template in. The folder will be created if it doesn't exist. |
| `remove_tags` | boolean | No | 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). |
| `shared_link` | boolean | No | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Submission

**Slug:** `DOCUSEAL_GET_SUBMISSION`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The unique identifier of the submission. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Submission Documents

**Slug:** `DOCUSEAL_GET_SUBMISSION_DOCUMENTS`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The unique identifier of the submission. You can get submission IDs from the List Submissions action. |
| `merge` | boolean | No | When true, merges all documents into a single PDF. Returns individual documents when false or omitted. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Submitter

**Slug:** `DOCUSEAL_GET_SUBMITTER`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The unique identifier of the submitter to retrieve. You can get submitter IDs from the List Submitters action. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Template

**Slug:** `DOCUSEAL_GET_TEMPLATE`

Tool to retrieve details of a specific template by its unique identifier. Use when you need to fetch template metadata by ID.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `template_id` | integer | Yes | The unique numeric identifier of the template to retrieve. You can get template IDs from the List Templates action. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Submissions

**Slug:** `DOCUSEAL_LIST_SUBMISSIONS`

List 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Search query to filter submissions by submitter name, email, or phone (partial match). |
| `slug` | string | No | Filter submissions by unique submission slug. |
| `after` | integer | No | Filter submissions with ID greater than this value (cursor-based pagination). |
| `limit` | integer | No | Maximum number of submissions to return (default: 10, max: 100). |
| `before` | integer | No | Filter submissions with ID less than this value (cursor-based pagination). |
| `status` | string | No | Filter by submission status. Allowed values: 'pending', 'completed', 'declined', 'expired'. |
| `archived` | boolean | No | If true, returns archived submissions. If false, returns active submissions only. |
| `template_id` | integer | No | Filter submissions by a specific template ID. |
| `template_folder` | string | No | Filter submissions by template folder name. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Submitters

**Slug:** `DOCUSEAL_LIST_SUBMITTERS`

Retrieve 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Search query to filter submitters by name, email, or phone (partial match supported) |
| `slug` | string | No | Filter by unique submitter slug (e.g., 'zAyL9fH36Havvm') |
| `after` | integer | No | Pagination cursor: return submitters with ID after this value. Use pagination.next from previous response. |
| `limit` | integer | No | Number of results per page (default: 10, max: 100) |
| `before` | integer | No | Pagination cursor: return submitters with ID before this value |
| `external_id` | string | No | Filter by application-specific external identifier |
| `submission_id` | integer | No | Filter submitters by a specific submission ID |
| `completed_after` | string | No | Filter submitters who completed after this date/time (ISO 8601 format, e.g., '2024-01-01T00:00:00Z') |
| `completed_before` | string | No | Filter submitters who completed before this date/time (ISO 8601 format, e.g., '2024-12-31T23:59:59Z') |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Templates (Enhanced)

**Slug:** `DOCUSEAL_LIST_TEMPLATES2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `q` | string | No | Filter templates based on the name partial match. Search for templates whose names contain this string. |
| `slug` | string | No | Filter templates by unique slug identifier. |
| `after` | integer | No | Return templates with IDs greater than this value. Used for cursor-based pagination. Pass the ID from pagination.next to load the next batch. |
| `limit` | integer | No | Maximum number of templates to return. Default is 10; maximum is 100. |
| `before` | integer | No | Return templates with IDs less than this value. Used for cursor-based pagination. |
| `folder` | string | No | Filter templates by folder name. |
| `archived` | boolean | No | If true, only archived templates are returned; if false or omitted, only active templates are returned. |
| `external_id` | string | No | The unique application-specific identifier provided for the template via API or Embedded template form builder. Filters templates with the specified external ID. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Merge Templates

**Slug:** `DOCUSEAL_MERGE_TEMPLATES`

Merge 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | Name for the merged template. If not provided, a default name will be generated. |
| `external_id` | string | No | Your application-specific identifier for the merged template. |
| `folder_name` | string | No | Name of the folder where the merged template will be stored. |
| `template_ids` | array | Yes | List of template IDs (integers) to merge into a single template. At least two template IDs are required. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Submitter

**Slug:** `DOCUSEAL_UPDATE_SUBMITTER`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The unique identifier of the submitter to update |
| `name` | string | No | The name of the submitter |
| `email` | string | No | The email address of the submitter |
| `phone` | string | No | The phone number of the submitter, formatted according to E.164 standard |
| `fields` | array | No | A list of configurations for template document form fields (required, readonly, default values, validation) |
| `values` | object | No | An object with pre-filled values for the submission. Use field names as keys. For more configurations see fields param. |
| `message` | object | No | Custom email message configuration for signature request. |
| `metadata` | object | No | Metadata object with additional submitter information |
| `reply_to` | string | No | Specify Reply-To address to use in the notification emails |
| `send_sms` | boolean | No | Set true to re-send signature request via phone number SMS |
| `completed` | boolean | No | Pass true to mark submitter as completed and auto-signed via API |
| `send_email` | boolean | No | Set true to re-send signature request emails |
| `external_id` | string | No | Your application-specific unique string key to identify this submitter within your app |
| `require_phone_2fa` | boolean | No | Set to true to require phone 2FA verification via one-time code sent to phone number to access documents |
| `completed_redirect_url` | string | No | Submitter specific URL to redirect to after the submission completion |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Template

**Slug:** `DOCUSEAL_UPDATE_TEMPLATE2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The unique identifier of the document template. |
| `name` | string | No | The name of the template |
| `roles` | array | No | An array of submitter role names to update the template with. |
| `archived` | boolean | No | Set `false` to unarchive template. |
| `folder_name` | string | No | The folder's name to which the template should be moved. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Template Documents

**Slug:** `DOCUSEAL_UPDATE_TEMPLATE_DOCUMENTS`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | integer | Yes | The unique identifier of the template to update. |
| `merge` | boolean | No | Set to true to merge all existing and new documents into a single PDF document in the template. |
| `documents` | array | Yes | List of document updates to apply. Each item can add a new document, replace an existing one, or mark one for removal. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |