SignWell is an electronic signature tool for legally binding e-signatures and faster document signing.
SignWell is an electronic signature tool for legally binding e-signatures and faster document signing. On Nagent, Signwell is exposed as a fully-configurable signatures integration that any agent can call — 12 actions, and API key authentication. No code is required to wire Signwell into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Signwell 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 Signwell 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 Signwell, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SIGNWELL_CREATE_DOCUMENTTool to create and optionally send a new document for signing. Use when you have files and recipients defined and want to programmatically submit a signature request in one call.
Input parameters
If true, saves document as draft (no emails sent). If false, sends signature requests immediately.
List of files to include in the document. At least one file is required.
Email message for the signature request. Defaults to system or template message.
Email subject for the signature request. Defaults to system or template subject.
ISO 639-1 code for localization (e.g., en, fr, es). Defaults to en.
Optional key/value data associated with the document.
If true, sends reminders on day 3, 6, and 10.
Set to true to enable Test Mode (not legally binding & not billed). Defaults to false.
If true, you may place fields via special text tags in your document.
Number of days before the request expires (>=1). Defaults to account or template setting.
People who must complete and/or sign this document.
URL to redirect recipients to after successful signing.
If true, recipients may decline to sign (which cancels the request).
If true, signers may reassign their signing responsibility.
If true, enables embedded signing (iframe) and disables email auth.
UUID of API Application settings to use (optional).
If true, enforces signing in the order provided by recipients.
If true, appends a signature page to the end and requires signing there.
URL to redirect recipients to if they decline to sign.
Custom name used in all email communications and audit records.
Custom email used in communications instead of the API key owner.
If true, sends completion notifications when using embedded 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
SIGNWELL_CREATE_DOCUMENT_FROM_TEMPLATETool to create and optionally send a new document for signing from a template. Use when you need to generate a document using a pre-configured template with placeholders. If draft is set to true the document will not be sent.
Input parameters
Name of the document being created from the template.
If true, saves document as draft without sending. If false, sends for signing immediately. Defaults to false.
Additional files to append to the document. Will not replace existing template files.
Fields to add to appended files (not existing template files). 2D array - one array of fields per appended file.
Labels for organizing documents. Updating labels replaces any existing labels.
Email message for the signature request. Defaults to template or system message.
Email subject for the signature request. Defaults to template or system subject.
Optional key-value metadata associated with the document. Returned in all document queries.
If true, sends reminders on day 3, 6, and 10. Defaults to true.
Set to true to enable Test Mode (not legally binding and not billed). Defaults to false.
If true, enables special text tags for placing fields in documents. Defaults to false.
Number of days before the signature request expires (minimum 1). Defaults to account or template setting.
Document recipients assigned to template placeholders. Recipients inherit placeholder fields and settings.
UUID of a single template to use. Either template_id or template_ids must be provided, not both.
URL to redirect recipients to after successfully signing the document.
List of template UUIDs to use for creating a multi-template document. Either template_id or template_ids must be provided, not both.
If true, recipients may decline to sign (which cancels the entire document). Defaults to true.
If true, signers may reassign their signing responsibility to another person. Defaults to true.
Contacts who receive the final document once all recipients complete signing.
Template fields to prepopulate with values. Cannot prepopulate Signature or Initials fields.
If true, enables embedded signing (iframe) and disables email authentication. Defaults to false.
UUID of API Application settings to use for OAuth isolation or embedded API settings.
If true, enforces signing in the order provided by recipients array. Defaults to false.
Attachments that recipients must upload to complete signing. Shown after all document fields are completed.
If true, appends a signature page to the end and requires all signers to sign there. Defaults to false.
URL to redirect recipients to if they decline to sign.
Custom name used in all email communications, notifications, and audit file.
Custom email used for all communications and audit file instead of the API key owner's email.
If true, sends completion notifications when using embedded signing. Defaults to false.
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
SIGNWELL_CREATE_WEBHOOKTool to register a webhook callback URL. Use when you need to receive document event notifications.
Input parameters
URL where SignWell will post document event payloads.
UUID of the API Application to associate with this webhook.
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
SIGNWELL_DELETE_DOCUMENTTool to delete a document (and cancel signing if in progress). Use when you need to remove a document by ID after confirming it.
Input parameters
The unique identifier (UUID) of the document to delete. This ID is returned when creating a document via SIGNWELL_CREATE_DOCUMENT or can be retrieved using SIGNWELL_GET_DOCUMENT.
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
SIGNWELL_DELETE_WEBHOOKDeletes a registered webhook by its ID. Use this to remove webhooks that are no longer needed. Returns no content on success.
Input parameters
The UUID of the webhook to delete. Obtain this from the list webhooks 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
SIGNWELL_GET_CREDENTIALSRetrieve account information for the authenticated API key. Returns comprehensive details including user profile, account settings, workspace configuration, and contact information. Use this to validate API credentials, check account capabilities (like template creation limits), or get user/account IDs for other API calls.
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
SIGNWELL_GET_DOCUMENTTool to return a document and all associated document data. Use when you need to fetch document details by ID.
Input parameters
The unique identifier (UUID) for the document to retrieve. This ID is returned when creating a document via the API.
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
SIGNWELL_LIST_BULK_SENDSTool to list all Bulk Sends. Use after setting up API credentials to retrieve paginated records.
Input parameters
Page number for pagination. Defaults to 1.
Email address of the user that sent the Bulk Send. Requires admin or manager role to view other users' sends.
Number of results per page. Defaults to 10, maximum 50.
Unique identifier for API Application settings to scope the request.
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
SIGNWELL_LIST_WEBHOOKSTool to list all registered webhooks. Use when you need to retrieve the active webhooks for your SignWell account after setup.
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
SIGNWELL_SEND_REMINDERTool to send a reminder email to recipients that have not signed yet. Use when you need to prompt unsigned recipients to complete their signature.
Input parameters
The unique identifier (UUID) of the document for which to send reminders. This ID is returned when creating a document via SIGNWELL_CREATE_DOCUMENT or can be retrieved using SIGNWELL_GET_DOCUMENT.
Optional list of specific recipients within the document to send a reminder email to. If none are specified, all recipients that have not signed yet will receive a reminder email.
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
SIGNWELL_UPDATE_AND_SEND_DOCUMENTTool to update a draft document and send it to recipients for signing. Use when you need to modify document settings and initiate the signing process.
Input parameters
Unique identifier for the document to update and send.
The name of the document.
Labels to organize documents. Updating labels replaces any existing labels for this document.
Email message for the signature request that recipients will see. Defaults to system or template message.
Email subject for the signature request that recipients will see. Defaults to system or template subject.
Optional key-value data associated with the document. Available every time document data is returned.
Whether to send signing reminders to recipients. Reminders are sent on day 3, 6, and 10 if enabled.
Set to true to enable Test Mode. Test Mode documents do not count towards API billing and are not legally binding.
Number of days before the signature request expires. Defaults to the account or template expiration setting.
URL that recipients are redirected to after successfully signing the document.
Whether to allow recipients the option to decline signing. If multiple signers are involved, any recipient can cancel the entire process by declining.
Allows signers to reassign their signing responsibilities to another person if they are not the right person to sign.
When set to true, enables embedded signing in your website/web application via iFrame with email authentication disabled.
Unique identifier for API Application settings to use. Mainly used for isolating OAuth apps or for more control over embedded API settings.
When set to true, recipients will sign one at a time in the order specified.
URL that recipients are redirected to if the document is declined.
Custom requester name used for all email communications, signing notifications, and in the audit file.
Custom requester email used for all email communications, signing notifications, and in the audit file.
For embedded signing, setting this to true will send out final completion notification emails to document owners and CC'd contacts.
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
SIGNWELL_UPDATE_TEMPLATETool to update an existing template in SignWell. Use when you need to modify template properties such as name, subject, message, reminders, expiration, or other settings.
Input parameters
Unique identifier for the template to update.
The name of the template.
Whether the template can still be updated before it is ready for usage. If set to false the template is marked as Available and ready for use.
Labels can be used to organize templates in a way that makes them easy to find using template search in SignWell. A template can have multiple labels. Updating labels on a template will replace any existing labels.
Email message for the signature request that recipients will see. Defaults to the default system message or template message.
Email subject for the signature request that recipients will see. Defaults to the default system subject or template subject.
Optional key-value data that can be associated with the template. If set, will be available every time the template data is returned.
Whether to send signing reminders to recipients. Reminders are sent on day 3, day 6, and day 10 if set to true.
Number of days before the signature request expires. Defaults to the account expiration setting or template expiration.
A URL that recipients are redirected to after successfully signing a document.
Whether to allow recipients the option to decline signing a document. If multiple signers are involved, any single recipient can cancel the entire document signing process by declining to sign.
In some cases a signer is not the right person to sign and may need to reassign their signing responsibilities to another person. This feature allows them to reassign the document to someone else.
Unique identifier for API Application settings to use. API Applications are optional and mainly used when isolating OAuth apps or for more control over embedded API settings.
When set to true recipients will sign one at a time in the order of the recipients collection.
A URL that recipients are redirected to if the document is declined.
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 55 agents privately built on Nagent that already use Signwell.
Build on Nagent
Connect Signwell 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 Signwell, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Signwell is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Signwell is connected, you configure its 12 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Signwell 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 Signwell event fires, the agent kicks off automatically.
Every Signwell 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 Signwell ships with 12 pre-built signatures actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Signwell together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Signwell-based workflows tailored to your business.