01
Trigger on event
- Listen for a new event
- Parse and validate the payload
- Take an action with the linked tool
Ignisign
32 tools available
IgniSign is a comprehensive electronic signature platform that enables users to sign, send, and manage documents securely online.
Connect Ignisign to Definable to automate repetitive tasks, sync data with the rest of your stack, trigger on real-world events. Personas call Ignisign's 32 tools directly from chat or scheduled flows. You can wire it into any persona to read, write, and react when an event fires.
Common workflows with Ignisign
02
Daily summary
- Pull yesterday's activity
- Summarise with the model of your choice
- Send the digest via email or Slack
03
Cross-tool sync
- Read records from one app
- Transform with a persona
- Write the result back via this integration
Ignisign actions 32
Every Ignisign action below is a callable tool any Definable persona can invoke.
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.
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.
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.
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 application context
Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app.
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 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 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 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.
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 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.
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`.
Boldsign
BoldSign delivers eSignature solutions, letting organizations create, send, and manage legally binding documents through streamlined digital signing workflows
Boloforms
BoloForms is an eSignature platform designed for small businesses, offering unlimited signatures, templates, forms, and team members at a fixed price.
Docnify
Docnify is a digital signing platform that simplifies the document signing process, offering integrations with tools like Figma, Jira, Trello, and Google Docs to create a unified workspace.
Documenso
Documenso is an open-source electronic signature platform that allows users to create, send, and sign documents digitally.
DocuSeal
DocuSeal is a platform that provides a powerful and easy-to-use API to implement eSignature workflows, allowing users to automate document and template management processes without relying on the web interface.
DocuSign
DocuSign provides eSignature and digital agreement solutions, enabling businesses to send, sign, track, and manage documents electronically
Frequently asked questions
What can I automate with Ignisign on Definable?
Anything Ignisign exposes through its API. Common signatures workflows on Definable include automate repetitive tasks, sync data with the rest of your stack, trigger on real-world events. Personas can call any of the 32 Ignisign tools directly, then chain the result into another integration without you writing code.
How does Ignisign authentication work?
Ignisign uses API_KEY on Definable. You connect once from the integrations page, scoped to the permissions you choose, and from then on any persona that has the integration enabled can act on your behalf. Tokens are encrypted at rest and rotated automatically.
Is the Ignisign integration included in my Definable plan?
Yes — every Definable plan, including Starter, includes access to all 32 Ignisign tools. You only need a separate Ignisign subscription if Ignisign itself charges per seat or per API call.
Is using Ignisign through Definable secure?
Every call from a persona to Ignisign is logged with the user, persona, prompt, and response. Tokens never leave Definable's secrets vault, scopes are configurable per persona, and you can revoke access at any time from the integration page.
How do I get started with Ignisign on Definable?
Sign up for Definable, open the integrations page, find Ignisign, and connect via OAuth or API key. You can immediately attach Ignisign to any persona and start running workflows. The free Starter plan includes 5,000 credits/month.
What Ignisign actions does Definable expose?
Definable exposes all 32 Ignisign actions as callable tools — including `Ignisign API Authentication`, `Cancel Signature Request`, `Initialize Document`, plus 29 more. Each tool gets a typed parameter schema so personas know exactly how to call it.
Ready to automate with Ignisign?
Wire it up in minutes. No coding required.