Connect Ignisign to Definable AI

IgniSign is a comprehensive electronic signature platform that enables users to sign, send, and manage documents securely online.

About Ignisign

Ignisign is a productivity tool. Connect it to Definable AI with one-click OAuth2 — no API keys or custom code required.

What you can automate with Ignisign

Use Definable AI's agent platform to trigger workflows from Ignisign, process results with 50+ AI models, and sync data across 900+ connected apps.

Tools & Actions (36 available)

  • Cancel Signature Request: Cancel (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.
  • Close Ignisign Signature Request: Tool to close an active signature request. Use when you need to end a signature process after all signers have completed or to abort a request in progress.
  • Create Signer: Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
  • Create Webhook Endpoint: Tool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications.
  • Delete Document: Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
  • Delete Ignisign Signature Request: Permanently 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.
  • Delete Signer: Tool 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.
  • Delete Webhook Endpoint: Delete 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.
  • Get Document Information: Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID.
  • Get Missing Signer Inputs: Tool 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.
  • Get Signature Request Details: Tool to retrieve detailed information for a specific signature request. Use after creating or listing a signature request to inspect its details.
  • Get Signature Request Document: Tool 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.
  • Get Signature Request Status: Tool to retrieve the current status of a specific signature request. Use when you need to check the state of a single request by its ID.
  • Get Signature Requests: Retrieves 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.
  • Get Signed Document: Tool 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)
  • Get Signer Creation Constraints: Tool to retrieve input constraints required to create a signer for a specific signature profile. Use after selecting a signature profile to determine required signer inputs.
  • Get Signer Input Constraints: Tool to get signer input constraints. Use when you need to know which fields are required from signers for a given signer profile.
  • Get Signer Inputs: Retrieves 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.
  • Get Signer Profile: Retrieve 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.
  • Get Signer Profiles: Retrieve 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.
  • Get Webhook Details: Tool to retrieve details of a specific webhook endpoint. Use after you have the webhook ID to inspect its URL, description, and creation timestamp.
  • Get Webhooks: Retrieves 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.
  • Get application context: Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app.
  • Ignisign API Authentication: Tool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls.
  • Initialize Document: Tool to initialize a document for a signature request. Use when linking a new document to an existing signature request after creating that request.
  • Initialize Ignisign Signature Request: Initialize 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.
  • List Documents: Tool 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.
  • Provide Document Content Data JSON: Provides 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.
  • Provide Document Content File: Tool to provide file content for a document. Use after creating a document to attach its file content.
  • Provide Document Content Private File: Provides 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.
  • Publish Signature Request: Tool to publish a draft signature request. Use after adding all documents and signer details to the draft.
  • Search Signers: Tool to search for signers within an application environment. 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.
  • Update Document Information: Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation.
  • Update Signature Request: Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending.
  • Update Signer: Updates 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).
  • Update Webhook Endpoint: Tool 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`.

How to connect Ignisign

  1. Sign in to Definable AI and go to Apps
  2. Search for Ignisign and click Connect
  3. Authorize via OAuth2 — takes under 30 seconds
  4. Use Ignisign actions in your AI agents and workflows