eSignatures.io provides a platform for sending and signing mobile-friendly contracts over the web.
eSignatures.io provides a platform for sending and signing mobile-friendly contracts over the web. On Nagent, eSignatures.io is exposed as a fully-configurable signatures integration that any agent can call — 17 actions, and API key authentication. No code is required to wire eSignatures.io into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use eSignatures.io 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 eSignatures.io 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 eSignatures.io, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ESIGNATURES_IO_ADD_TEMPLATE_COLLABORATORTool to grant editing access to a template with optional email invitation. Use when you need to add a collaborator who can edit the template.
Input parameters
Name of the collaborator who will be granted editing access to the template
Email address to send invitation to. The collaborator will receive an email with access link if provided.
Unique identifier of the template to add collaborator to
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
ESIGNATURES_IO_COPY_TEMPLATETool to duplicate an existing template with optional customization. Use when you need to create a new template based on an existing one.
Input parameters
Title for the new template copy
Unique identifier of the template to copy
Optional placeholder field values for customization. List of maps with 'api_key' and 'value' fields.
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
ESIGNATURES_IO_CREATE_CONTRACTTool to create a new contract using a specified template and signer details. Use after selecting a template when you need to send a contract for signature.
Input parameters
Set to 'yes' for test/demo contracts (no fees), 'no' or omit for production contracts
Title of the contract; defaults to template title if not provided
Labels/tags for organizing contracts in dashboard
Language setting for the contract (e.g., 'en', 'de', 'fr', 'es', 'ja')
List of signer details; at least one required
Custom metadata to attach to the contract
ID of the template to use for the contract
Set to 'yes' to save contract without sending notifications
Number of hours until the contract expires
Custom webhook URL for notifications (overrides default)
Dynamic fields to populate in the template
Email of team member to assign the contract to
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
ESIGNATURES_IO_CREATE_SIGNERAdd a signer to an existing contract/signature request. This action queues the addition of a new signer to a contract that has already been created. The signer will be added asynchronously and will receive their signing invitation via email. Use this when you need to add additional signers to a contract after it has been created, or when you want to add signers incrementally rather than all at once during contract creation. Note: The API returns a queued status, indicating the operation has been accepted for processing. Adding a new signer does not automatically send an email notification unless the contract settings are configured to do so.
Input parameters
ISO 639-1 two-letter language code for localizing the signer's interface and emails (e.g., 'en', 'es', 'fr', 'de')
Full legal name of the signer who will sign the contract
Email address where the signer will receive signing notifications and access to the contract
Company or organization name associated with the signer
Phone number in international E.164 format (e.g., +1234567890) for SMS notifications or verification
URL to redirect the signer to after they complete signing. Useful for returning users to your application.
Custom metadata key-value pairs to attach to the signer for tracking or integration purposes
The contract ID to which this signer will be added. This is the 'id' field returned when creating a contract.
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
ESIGNATURES_IO_CREATE_TEMPLATETool to create a new template. Use when you want to register a reusable contract template after defining document elements.
Input parameters
Title of the new template.
Optional list of labels to organize templates and contracts.
Ordered list of document elements comprising the 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
ESIGNATURES_IO_DELETE_SIGNERTool to remove a signer from a contract. Use when you need to revoke a signer's access to sign a contract.
Input parameters
Unique identifier of the signer to remove from the contract
Unique identifier of the contract containing the signer
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
ESIGNATURES_IO_DELETE_TEMPLATETool to delete a specific template by its ID. Use when you need to remove an unused or outdated template after confirming its ID.
Input parameters
Unique identifier of the template to delete
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
ESIGNATURES_IO_GENERATE_CONTRACT_PDF_PREVIEWTool to generate a PDF preview of a contract and receive a webhook notification with a download URL. Use when you need to preview the contract document before or after signing.
Input parameters
Unique identifier of the contract to generate PDF preview for
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
ESIGNATURES_IO_GET_CONTRACTTool to retrieve details of a specific contract by its ID. Returns contract status, signer information, and values entered by signers. Use when you need to check contract status or download signed PDF.
Input parameters
Unique identifier of the contract to retrieve
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
ESIGNATURES_IO_GET_TEMPLATETool to retrieve details of a specific template by its ID. Use when you need to fetch a template’s metadata after selecting its ID.
Input parameters
Unique identifier of the template to retrieve
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
ESIGNATURES_IO_LIST_TEMPLATE_COLLABORATORSTool to retrieve all collaborators with editing access to a template. Returns collaborator IDs, names, emails, and editor URLs.
Input parameters
Unique identifier of the template to list collaborators for
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
ESIGNATURES_IO_LIST_TEMPLATESTool to retrieve a list of all templates. Use when you need to browse available templates before selecting one.
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
ESIGNATURES_IO_REMOVE_TEMPLATE_COLLABORATORTool to revoke a collaborator's template editing permissions. Use when you need to remove access for a specific collaborator from a template.
Input parameters
Unique identifier of the template to revoke collaborator access from
Unique identifier of the collaborator to remove from the 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
ESIGNATURES_IO_SEND_CONTRACT_TO_SIGNERTool to send or resend a contract signature request to a specific signer via their configured communication channel. Use when you need to deliver a contract to a signer for their signature.
Input parameters
Unique identifier of the signer to send the contract to
Unique identifier of the contract to send
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
ESIGNATURES_IO_UPDATE_SIGNERTool to update contact details of an existing signer on a contract. Use when you need to change a signer's name, email, or mobile number. Note: The contract is not automatically emailed when the signer's information is updated.
Input parameters
Updated full name of the signer
Updated email address of the signer
Updated mobile number of the signer in international format with country code (e.g., +14155559999)
The ID of the signer whose information should be updated
The ID of the contract containing the signer to update
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
ESIGNATURES_IO_UPDATE_TEMPLATETool to update an existing template's content, title, or labels. Use when you need to modify a template's configuration without creating a new one.
Input parameters
Updated title of the template
Array of labels for organizing templates
Unique identifier of the template to update
Array of document element objects defining the template content. Replaces existing elements.
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
ESIGNATURES_IO_WITHDRAW_CONTRACTTool to withdraw a contract by its ID. Use when you need to prevent further signing of a contract that hasn't been fully signed.
Input parameters
Unique identifier of the contract to withdraw
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 49 agents privately built on Nagent that already use eSignatures.io.
Build on Nagent
Connect eSignatures.io 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 eSignatures.io, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, eSignatures.io is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once eSignatures.io is connected, you configure its 17 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop eSignatures.io 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 eSignatures.io event fires, the agent kicks off automatically.
Every eSignatures.io 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 eSignatures.io ships with 17 pre-built signatures actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching eSignatures.io together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build eSignatures.io-based workflows tailored to your business.