---
title: "Ignisign integration for LuumenAI"
url: "https://www.luumen.ai/integrations/ignisign/"
entity: SoftwareIntegration
category: "Knowledge & documentation"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Ignisign integration for LuumenAI

Track signature requests and cancel stale ones, with the write held for approval

## What LuumenAI can do with Ignisign

LuumenAI connects to Ignisign with an API token and exposes 32 tools (14 read-only · 13 write · 5 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 32 tools (14 read-only · 13 write · 5 destructive)
- Plan: available on all plans
- Category: Knowledge & documentation

## About Ignisign with LuumenAI

Connect Ignisign and Luumen can see the state of your signing workflows: which requests are open, which signers still owe inputs, what documents are attached, and where the signed proof lives. Reads answer on the spot. Changes like initializing a request, adding document content, or canceling a request are previewed and sent for approval first. Authentication is by API key.

## Example tools

Read-only (14 in total):

- `IGNISIGN_GET_APPLICATION_CONTEXT` — Retrieve the global context of an application.
- `IGNISIGN_GET_DOCUMENT_INFORMATION` — Retrieve document metadata by ID.
- `IGNISIGN_GET_MISSING_SIGNER_INPUTS` — Determine missing inputs needed for a signer in a specific signature profile.
- `IGNISIGN_GET_SIGNATURE_REQUEST_DETAILS` — Retrieve detailed information for a specific signature request.
- `IGNISIGN_GET_SIGNATURE_REQUEST_DOCUMENT` — Retrieve the document associated with a specific signature request.
- `IGNISIGN_GET_SIGNATURE_REQUESTS` — Retrieves a paginated list of signature requests for a specific Ignisign application and environment.
- `IGNISIGN_GET_SIGNED_DOCUMENT` — Download the signed document (signature proof) for a signature request.
- `IGNISIGN_GET_SIGNER_INPUT_CONSTRAINTS` — Get signer input constraints.

Write and destructive (18 in total, approval required by default):

- `IGNISIGN_API_AUTHENTICATION` — Authenticate an application over Ignisign API and retrieve a JWT.
- `IGNISIGN_CANCEL_SIGNATURE_REQUEST` — Cancel (close) a signature request to terminate it.
- `IGNISIGN_CREATE_DOCUMENT` — Initialize a document for a signature request.
- `IGNISIGN_CREATE_SIGNER` — Create a new signer.
- `IGNISIGN_CREATE_WEBHOOK_ENDPOINT` — Create a new webhook endpoint for an application.
- `IGNISIGN_DELETE_DOCUMENT` — Delete a specific document by its ID.
- `IGNISIGN_DELETE_SIGNATURE_REQUEST` — Permanently deletes a signature request from Ignisign by its ID.
- `IGNISIGN_DELETE_SIGNER` — Revoke/delete a signer from an Ignisign application environment.

## Frequently asked questions

### How does LuumenAI connect to Ignisign?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Ignisign on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to Ignisign — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/ignisign/