# Ignisign AI integration on Definable

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

## What this connects

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

Vendor: https://console.ignisign.io/signup

## Tools available

**32** tools available. First 12:

- `IGNISIGN_API_AUTHENTICATION` — 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.
- `IGNISIGN_CANCEL_SIGNATURE_REQUEST` — 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.
- `IGNISIGN_CREATE_DOCUMENT` — 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.
- `IGNISIGN_CREATE_SIGNER` — Create Signer — Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
- `IGNISIGN_CREATE_WEBHOOK_ENDPOINT` — 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.
- `IGNISIGN_DELETE_DOCUMENT` — Delete Document — Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
- `IGNISIGN_DELETE_SIGNATURE_REQUEST` — 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.
- `IGNISIGN_DELETE_SIGNER` — 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.
- `IGNISIGN_DELETE_WEBHOOK_ENDPOINT` — 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.
- `IGNISIGN_GET_APPLICATION_CONTEXT` — 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_GET_DOCUMENT_INFORMATION` — Get Document Information — Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID.
- `IGNISIGN_GET_MISSING_SIGNER_INPUTS` — 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.

## Auth

Auth schemes: `API_KEY`.

## How agents use Ignisign

Inside a Definable workflow, Ignisign is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Ignisign** — the Researcher (GPT-5.5) pulls context from Ignisign (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Ignisign** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Ignisign (create record, post message, draft email).
- **Designer / Engineer → Distributor → Ignisign** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Ignisign (attach file, open PR comment, post status).

The Verifier checks every Ignisign call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- signatures — https://definable.ai/apps/category/signatures/
- documents — https://definable.ai/apps/category/documents/

## Related

- HTML page: https://definable.ai/apps/ignisign/
- Same category (signatures): https://definable.ai/apps/category/signatures/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt