Xodo Sign is a cloud-based digital signature solution that allows users to sign, send, and manage documents online.
Xodo Sign is a cloud-based digital signature solution that allows users to sign, send, and manage documents online. On Nagent, Eversign is exposed as a fully-configurable signatures integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Eversign into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Eversign 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 Eversign 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 Eversign, with input parameters and output schema. Drop these into any step of an agent built in Helix.
EVERSIGN_AUDIT_LOGRetrieves the complete audit trail for a document, showing all events from creation through completion. Use this after obtaining a document_hash from list_documents or create_document to track document lifecycle events, signer actions, and status changes.
Input parameters
The unique identifier (hash) of the document to retrieve history 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
EVERSIGN_CREATE_DOCUMENTCreates a new Eversign document for electronic signature collection from one or more signers. You can create documents either: 1. From a template (use EVERSIGN_LIST_TEMPLATES to find available templates, then specify template_id) 2. From uploaded files (provide file URLs, base64 content, or file IDs in the files array) Documents can be sent immediately to signers or saved as drafts. Use sandbox mode for testing. Returns the document_hash which can be used to track and manage the document.
Input parameters
Custom metadata key-value pairs to attach to the document
PDF or document files to include (via URL, Base64, or file_id)
Custom document title/name (requires premium plan - omit to use template's default title)
Form fields to place on the document for signers to fill
Custom message sent to all signers in invitation email (requires premium plan - omit to use default)
Set to true to create document in sandbox/test mode for testing (documents are marked as non-binding)
List of signers who must sign the document (at least one required)
Set to true to save as draft without sending to signers (can be sent later)
URL to redirect signers to after completing the signature
Enable automatic reminder emails to signers
CC recipients who receive the completed document but don't sign
Template document hash to use as base for this document (use EVERSIGN_LIST_TEMPLATES to find available templates)
Enable sequential signing (signers must sign in order)
Require all signers to sign for completion (vs. any one signer)
Enable embedded signing (displays signing in iframe)
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
EVERSIGN_CREATE_TEMPLATETool to create a new template. Use when you need to programmatically set up reusable document templates after confirming your business settings.
Input parameters
List of file objects to attach to the template.
2-dimensional array of form fields - one array per file. Each file's array contains its field specifications. Provide an empty array \[\] for files without fields.
Unix timestamp (seconds since epoch) when the document should expire. Must be a future date.
If true, the template is created in the sandbox environment.
List of signer roles for the template. Each role represents a type of signer (e.g., 'Client', 'Manager') rather than a specific person.
Reminder settings for the template.
Optional internal notes for the template.
Title of the template to be created.
Optional message body to associate with the template.
If true, all signers must complete before finalization.
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
EVERSIGN_DELETE_DOCUMENT_OR_TEMPLATETool to delete, cancel, or trash a document or template by its hash. Usage: - To cancel a pending/in-process document: Set cancel=True - To trash a document (safer, reversible): Set trash=True - To permanently delete a draft or cancelled document: Use without cancel or trash flags Note: Draft and completed documents must be trashed before permanent deletion. Pending documents must be cancelled before deletion.
Input parameters
Set to True to move a document to trash instead of permanently deleting it. Draft and completed documents must be trashed before they can be permanently deleted. This is a safer option than permanent deletion.
Set to True to cancel a pending/in-process document. Cancelled documents can then be permanently deleted. Use this for documents that are awaiting signatures.
The unique identifier (hash) of the document or 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
EVERSIGN_GET_BULK_JOBS_LISTTool to retrieve a list of bulk jobs for a business. Use when you need to view or paginate existing bulk jobs.
Input parameters
Maximum number of bulk jobs to return (default 100, range 1-1000)
Number of bulk jobs to skip (default 0)
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
EVERSIGN_GET_BULK_JOB_STATUSTool to retrieve the status of a bulk job. Use when you need to check the progress of a bulk sending job, including counts of completed, cancelled, and in-progress documents.
Input parameters
ID of the bulk job to retrieve status 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
EVERSIGN_LIST_BUSINESSESRetrieves all businesses associated with your Eversign account, or filters to a specific business if business_id is provided. This is a read-only operation that returns business details including ID, name, status, and whether it's the primary business. Use this action when you need to discover available businesses before performing operations that require a business context, or to verify business access permissions.
Input parameters
Optional business ID to filter results to a specific business. When provided, only returns the business with this ID if you have access to it. If not provided, returns all businesses associated with your account.
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
EVERSIGN_LIST_DOCUMENTSRetrieves a paginated list of documents from your Eversign business account. This tool returns comprehensive document details including signers, status, timestamps, and metadata. Use filters to narrow results by status type, date range, search terms, or signer email. Perfect for monitoring document workflows, tracking signing progress, and building document dashboards.
Input parameters
Page number for paginated results (starts at 1). Use with per_page to navigate through large document lists.
Filter documents by status type. Options: 'all' (default - all documents), 'my_action_required' (documents requiring your action), 'waiting_for_others' (documents waiting for other signers), 'completed' (signed documents), 'drafts' (draft documents), 'cancelled' (cancelled documents).
Search documents by text contained in document title, message, or other fields. Case-insensitive partial match.
Filter documents created on or before this date. Format: YYYY-MM-DD (e.g., '2024-12-31'). Combine with from_date for date range filtering.
Number of documents to return per page (default: 50). Use lower values for faster responses or higher values (up to API limit) to reduce pagination.
Filter documents created on or after this date. Format: YYYY-MM-DD (e.g., '2024-01-15'). Useful for retrieving documents from a specific time period.
Filter documents where the specified email address is a signer. Use to find all documents involving a particular person.
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
EVERSIGN_LIST_TEMPLATESTool to list templates for a business with optional pagination. Use when you need to retrieve a paginated list of templates.
Input parameters
Page number for paginated results; must be at least 1
Type of templates to retrieve: 'templates' (active templates), 'templates_archived' (archived templates), or 'template_drafts' (draft templates)
Number of results per page; must be between 1 and 500
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
EVERSIGN_REASSIGN_SIGNERTool to reassign a signer to a new person. Use when you need to replace an existing signer on a document before signing is complete. Example: "Reassign the signer alice@example.com on document abc123 to bob@example.com".
Input parameters
Optional explanation for the reassignment
The ID of the signer which should be reassigned/replaced (found in document signer details)
The unique hash (ID) of the document for which the signer should be changed
The name of the new signer
The email address of the new 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
No publicly available marketplace agent is found using this tool yet. There are 85 agents privately built on Nagent that already use Eversign.
Build on Nagent
Connect Eversign 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 Eversign, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Eversign is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Eversign is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Eversign 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 Eversign event fires, the agent kicks off automatically.
Every Eversign 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 Eversign ships with 10 pre-built signatures actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Eversign together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Eversign-based workflows tailored to your business.