Team
Shared credential for production and unattended runs.
IgniSign is a comprehensive electronic signature platform that enables users to sign, send, and manage documents securely online.
Tools and triggers
Available tools and events after Ignisign is connected.
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…
Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
Tool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications.
Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
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…
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…
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…
Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app.
Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID.
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.
Tool to retrieve detailed information for a specific signature request. Use after creating or listing a signature request to inspect its details.
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…
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…
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…
Tool to get signer input constraints. Use when you need to know which fields are required from signers for a given signer profile.
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…
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…
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…
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…
Tool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls.
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 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)…
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.
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…
Tool to provide file content for a document. Use after creating a document to attach its file content.
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…
Tool to publish a draft signature request. Use after adding all documents and signer details to the draft.
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…
Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation.
Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending.
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…
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…
Setup
Pick a scope, then confirm what can start a Protege and what it can do.
What can start a Protege from this app.
What a Protege can do after it starts.
Prefer team for production.
Shared credential for production and unattended runs.
Tied to one user—only when the workflow needs their account.
Team-scoped for supported chat surfaces.
Build with us
Request early access or book a live walkthrough with the team.