IgniSign is a comprehensive electronic signature platform that enables users to sign, send, and manage documents securely online.
IgniSign is a comprehensive electronic signature platform that enables users to sign, send, and manage documents securely online. On Nagent, Ignisign is exposed as a fully-configurable signatures integration that any agent can call — 32 actions, and API key authentication. No code is required to wire Ignisign into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Ignisign 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 Ignisign 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 Ignisign, with input parameters and output schema. Drop these into any step of an agent built in Helix.
IGNISIGN_API_AUTHENTICATIONTool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls.
Input parameters
The application identifier (e.g., appId_d9cf31d7-6f48-4b11-8168-ded211c1296d).
Execution environment. Allowed values: DEVELOPMENT, STAGING, PRODUCTION.
Secret tied to the application and environment; obtainable from Ignisign Console.
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
IGNISIGN_CANCEL_SIGNATURE_REQUESTCancel (close) a signature request to terminate it. This uses the Ignisign /close endpoint which permanently cancels the signature workflow. Use this when you need to abort a signature request that is in DRAFT or IN_PROGRESS status. This operation is idempotent - calling it on an already cancelled request returns success without error.
Input parameters
Unique identifier (24-character hex string) of the signature request to cancel. Obtain this from IGNISIGN_GET_SIGNATURE_REQUESTS or IGNISIGN_INIT_SIGNATURE_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
IGNISIGN_CREATE_DOCUMENTTool to initialize a document for a signature request. Use when linking a new document to an existing signature request after creating that request.
Input parameters
Application identifier
Human-friendly label for the document
Target application environment
Free-text external reference; not interpreted by IgniSign
Human-readable description of the document
ID of the signature request to associate the document with
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
IGNISIGN_CREATE_SIGNERTool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
Input parameters
The application identifier.
Signer’s email address; required if demanded by the signer profile.
The application environment.
Signer’s last name; required if demanded by the signer profile.
Birth date as YYYY-MM-DD; required if demanded by the signer profile.
Signer’s first name; required if demanded by the signer profile.
Place of birth; required if demanded by the signer profile.
External reference; not used by Ignisign for identification.
Nationality as ISO 3166-1 alpha-2 code; required if demanded by the signer profile.
Phone number in E.164 format; required if demanded by the signer profile.
Birth country as ISO 3166-1 alpha-2 code; required if demanded by the signer profile.
Signer profile ID to which the signer must conform.
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
IGNISIGN_CREATE_WEBHOOK_ENDPOINTTool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications.
Input parameters
The webhook endpoint URL to receive Ignisign events.
The application identifier.
The application environment.
Human-readable description of the webhook endpoint.
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
IGNISIGN_DELETE_DOCUMENTTool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
Input parameters
The unique identifier (MongoDB ObjectId) of the document to delete. Obtain this from a previous document creation or listing operation.
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
IGNISIGN_DELETE_SIGNATURE_REQUESTPermanently deletes a signature request from Ignisign by its ID. This action is irreversible and removes the signature request along with all associated data. The signature request ID can be obtained from the IGNISIGN_INIT_SIGNATURE_REQUEST action or IGNISIGN_GET_SIGNATURE_REQUESTS action.
Input parameters
Unique MongoDB ObjectId identifier of the signature request to delete. This ID is returned when initializing a signature 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
IGNISIGN_DELETE_SIGNERTool to revoke/delete a signer from an Ignisign application environment. This action permanently revokes the signer's access and is idempotent (can be called multiple times on the same signer). Use when you need to remove a signer after confirming their signer ID.
Input parameters
The application identifier (e.g., appId_d9cf31d7-6f48-4b11-8168-ded211c1296d).
The application environment.
Unique identifier of the signer to revoke (24-character MongoDB ObjectId format, e.g., '688f26dd3b3a41c435b74a40').
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
IGNISIGN_DELETE_WEBHOOK_ENDPOINTDelete a webhook endpoint by its ID. After deletion, returns the list of remaining webhook endpoints configured for the application environment. Use this tool when you need to remove a webhook that is no longer needed or to clean up unused webhooks. The webhook ID can be obtained from the create webhook or list webhooks endpoints.
Input parameters
The unique identifier of the webhook endpoint to delete. This ID is returned when creating a webhook or can be obtained from the list webhooks endpoint.
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
IGNISIGN_GET_APPLICATION_CONTEXTTool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app.
Input parameters
Unique identifier of the Ignisign application. Must match the app_id associated with the authentication token. Format: 'appId_<uuid>'
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
IGNISIGN_GET_DOCUMENT_INFORMATIONTool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID.
Input parameters
The unique identifier of the 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
IGNISIGN_GET_MISSING_SIGNER_INPUTSTool to determine missing inputs needed for a signer in a specific signature profile. Use after selecting a signature profile and signer to identify required fields.
Input parameters
The application identifier used to identify the application.
The execution environment where requests are executed.
The unique identifier of the signer. Obtain this from the Search Signers or Create Signer actions.
The unique identifier of the signature profile. Obtain this from the Get Signer Profiles 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
IGNISIGN_GET_SIGNATURE_REQUEST_DETAILSTool to retrieve detailed information for a specific signature request. Use after creating or listing a signature request to inspect its details.
Input parameters
The unique identifier (MongoDB ObjectId) of the signature request 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
IGNISIGN_GET_SIGNATURE_REQUEST_DOCUMENTTool to retrieve the document associated with a specific signature request. The action downloads the original file of a document. Provide `documentId` to select a specific document or omit to use the first available document of the request.
Input parameters
Unique identifier of the signature request.
Optional: specify a concrete documentId to download. If omitted, the first documentId found on the signature request will be used.
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
IGNISIGN_GET_SIGNATURE_REQUESTSRetrieves a paginated list of signature requests for a specific Ignisign application and environment. Use this to list all signature requests (drafts, in-progress, completed, cancelled) in an application. Each signature request can have associated documents and signers. Returns pagination metadata to iterate through large result sets. Note: The app_env parameter must match your API key's environment scope.
Input parameters
Page number for pagination (1-indexed). Defaults to 1 if not specified.
The Ignisign application identifier. Obtain this from 'Get application context' or the Ignisign console.
The application environment. Must match the environment scope of your API key (e.g., a DEVELOPMENT API key can only access DEVELOPMENT environment).
Number of items to return per page. Defaults to 25 if not specified.
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
IGNISIGN_GET_SIGNED_DOCUMENTTool to download the signed document (signature proof) for a signature request. The action will: 1) Resolve the first documentId from the signature request details. 2) Try v4: GET /documents/{documentId}/signatures/PDF_WITH_SIGNATURES 3) Fallback v3: GET /v3/documents/{documentId}/signature-proof 4) Final fallback: GET /documents/{documentId}/file (original file)
Input parameters
Unique identifier of the signature request to download the signed document 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
IGNISIGN_GET_SIGNER_INPUT_CONSTRAINTSTool to get signer input constraints. Use when you need to know which fields are required from signers for a given signer profile.
Input parameters
The application identifier used to identify the application.
The execution environment where requests are executed.
The unique identifier of the signer profile.
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
IGNISIGN_GET_SIGNER_INPUTSRetrieves the inputs provided by a specific signer for a signature request. Returns field values the signer has submitted (e.g., firstName, lastName, email). Use this after a signer has been added to a signature request to fetch their profile information. The signer must be associated with the specified signature request.
Input parameters
The MongoDB ObjectId of the signer whose inputs to retrieve. Obtain this from the Search Signers action or from the signerIds array in a signature request's details.
The MongoDB ObjectId of the signature request. Obtain this from the Get Signature Requests action or from the response when initializing a signature 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
IGNISIGN_GET_SIGNER_PROFILERetrieve detailed information about a specific signer profile by its ID. Use this to get profile settings including integration mode, authentication methods, and associated signers. First use 'Get Signer Profiles' to list available profile IDs.
Input parameters
The Ignisign application identifier. Starts with 'appId_'.
The application environment (DEVELOPMENT, STAGING, or PRODUCTION).
The unique identifier of the signer profile to retrieve. Obtain this from the Get Signer Profiles 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
IGNISIGN_GET_SIGNER_PROFILESRetrieve all signer profiles for a specific Ignisign application environment. Use this tool to list all configured signer profiles that define how signers interact with signature requests. Each profile specifies integration mode (BY_SIDE, EMBEDDED, or MACHINE_TO_MACHINE), authentication methods, and other settings. Returns profile IDs which can be used when creating signers or signature requests.
Input parameters
The unique identifier for the Ignisign application (e.g., 'appId_d9cf31d7-6f48-4b11-8168-ded211c1296d')
The application environment to retrieve signer profiles from. Use 'DEVELOPMENT' for testing, 'STAGING' for pre-production, or 'PRODUCTION' for live environment
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
IGNISIGN_GET_WEBHOOKSRetrieves all webhook endpoints configured for a specific Ignisign application environment. Returns the list of webhooks including their URLs, descriptions, and creation timestamps. Use this to audit existing webhook integrations or verify webhook configurations.
Input parameters
The Ignisign application identifier in format 'appId_<UUID>' (e.g., 'appId_d9cf31d7-6f48-4b11-8168-ded211c1296d').
The target environment for the application: DEVELOPMENT (sandbox testing), STAGING (pre-production), or PRODUCTION (live).
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
IGNISIGN_INIT_SIGNATURE_REQUESTInitialize a new signature request in Ignisign. This is the first step in creating a signature workflow. After initialization, you can add documents (IGNISIGN_CREATE_DOCUMENT), assign signers (IGNISIGN_CREATE_SIGNER), and publish the request (IGNISIGN_PUBLISH_SIGNATURE_REQUEST) to start the signing process.
Input parameters
The unique application identifier. Obtain this from IGNISIGN_GET_APPLICATION_CONTEXT or use the appId associated with your Ignisign account.
The target environment for the signature request. Use DEVELOPMENT for testing, STAGING for pre-production, or PRODUCTION for live signatures.
The signer profile ID (_id field) that defines signature settings and authentication methods. Retrieve available profiles using IGNISIGN_GET_SIGNER_PROFILES.
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
IGNISIGN_LIST_DOCUMENTSTool to retrieve documents linked to a signature request. The action works by calling the signature request context endpoint and extracting its documentIds, then fetching each document detail.
Input parameters
The IgniSign application identifier. Obtain this from the application context or your IgniSign dashboard.
The application environment. Use DEVELOPMENT for testing, STAGING for pre-production, or PRODUCTION for live operations.
The unique identifier (MongoDB ObjectId format) of the signature request whose documents should be listed. Obtain this from creating or listing signature requests.
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
IGNISIGN_PROVIDE_DOCUMENT_CONTENT_DATA_JSONProvides JSON content to an existing document in Ignisign. Use this action after creating a document with IGNISIGN_CREATE_DOCUMENT to attach structured JSON data that will be associated with a signature request. The JSON content is stored and can be used for document generation or data binding in signature workflows.
Input parameters
The unique identifier of the document (MongoDB ObjectId format). Obtain this from IGNISIGN_CREATE_DOCUMENT response.
The JSON object to attach to the document. Can contain nested objects, arrays, strings, numbers, booleans, and null values.
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
IGNISIGN_PROVIDE_DOCUMENT_CONTENT_FILETool to provide file content for a document. Use after creating a document to attach its file content.
Input parameters
File for the document content (e.g., PDF). The 'name' field should be the desired filename (e.g., 'contract.pdf').
Override filename for the upload. If not provided, uses the filename from the file field.
Override MIME type (e.g., 'application/pdf'). If not provided, auto-detected from filename extension.
The unique identifier (MongoDB ObjectId) of the document to attach the file to. Obtained from the IGNISIGN_CREATE_DOCUMENT 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
IGNISIGN_PROVIDE_DOCUMENT_CONTENT_PRIVATE_FILEProvides private document content by submitting its SHA-256 hash to IgniSign. Use this after creating a document with IGNISIGN_CREATE_DOCUMENT when the document content should remain private (not uploaded). The hash proves document integrity without exposing its contents. The document status will change to 'PROVIDED' upon success.
Input parameters
MongoDB ObjectId identifier of the document. Obtain this from the IGNISIGN_CREATE_DOCUMENT action.
Hex-encoded SHA-256 hash (64 lowercase hex characters) of the private document content to be signed. This hash represents the document without uploading the actual file.
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
IGNISIGN_PUBLISH_SIGNATURE_REQUESTTool to publish a draft signature request. Use after adding all documents and signer details to the draft.
Input parameters
The unique identifier of the draft signature request to publish.
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
IGNISIGN_SEARCH_SIGNERSTool to search for signers within an application environment with pagination support. Use after obtaining application ID and environment. Requires a non-empty filter string to search by name, email, or external ID. Use '*' to match all signers. Supports page and pageSize parameters to paginate through large result sets.
Input parameters
Page number for pagination (1-indexed). Defaults to 1 if not specified.
The application identifier (e.g., appId_XXXX-XXXX-XXXX-XXXX-XXXX)
The application execution environment.
Required filter string (non-empty) to search signers by name, email, or external ID. Use '*' to match all signers.
Number of signers to return per page. Defaults to server default if not specified.
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
IGNISIGN_UPDATE_DOCUMENT_INFORMATIONTool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation.
Input parameters
A user-friendly label to identify the document.
The unique identifier of the document to update (MongoDB ObjectId format, 24 hex characters).
Optional external identifier used by external systems (free text; not interpreted by Ignisign).
A detailed, human-readable description of the 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
IGNISIGN_UPDATE_SIGNATURE_REQUESTTool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending.
Input parameters
New title of the signature request.
Language code of the signature request.
List of signer IDs to include in the request.
External reference ID for your system.
List of statement objects to attach to the request.
New description for the signature request.
List of document IDs to associate with the request.
Scheduled send date (required if diffusionMode = SCHEDULED).
When to send the signature request.
Expiration date in ISO 8601 format.
Unique identifier of the signature request to update.
Whether the expiration date is active.
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
IGNISIGN_UPDATE_SIGNERUpdates an existing signer's profile assignment. Use this to change which signer profile a signer is associated with. The signer must already exist in the application environment. Requires: app_id (from Get Application Context), signer_id (from Create Signer or Search Signers), and signer_profile_id (from Get Signer Profiles).
Input parameters
The Ignisign application identifier (e.g., 'appId_d9cf31d7-6f48-4b11-8168-ded211c1296d'). Obtain from Get Application Context.
The application environment where the signer exists.
The unique identifier of the signer to update (e.g., '688f26dd3b3a41c435b74a40'). Obtain from Create Signer or Search Signers.
The signer profile ID to assign to this signer (e.g., '688f26dd3b3a41c435b749f6'). Obtain from Get Signer Profiles.
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
IGNISIGN_UPDATE_WEBHOOK_ENDPOINTTool to update an existing webhook endpoint. Use when you have a webhook ID and want to modify its destination URL or description. Example: Update the URL of webhook `68e7adc882353ea4e072bdbe` to `https://example.com/webhook`.
Input parameters
New destination URL that the webhook will call. Must be a valid HTTPS URL.
Unique identifier of the webhook to update (e.g., '68e7adc882353ea4e072bdbe').
Human-readable description of the webhook endpoint. Set to empty string to clear.
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 54 agents privately built on Nagent that already use Ignisign.
Build on Nagent
Connect Ignisign 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 Ignisign, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Ignisign is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Ignisign is connected, you configure its 32 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Ignisign 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 Ignisign event fires, the agent kicks off automatically.
Every Ignisign 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 Ignisign ships with 32 pre-built signatures actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Ignisign together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Ignisign-based workflows tailored to your business.