Sanaf AI
Start free
Signatures

Ignisign, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Ignisign account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Signatures
  • Connects with a key
  • 36 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Ignisign is

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

You paste in a key from your own Ignisign account. It is kept encrypted, and you can withdraw it from inside Ignisign whenever you like.

How a run works

One message in, the work done in Ignisign.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Ignisign. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Ignisign account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

36 tools it already has

What it can do in Ignisign

These are the ready-made tools your AI employee already has in Ignisign. It is not limited to them, but it never has to be taught these.

  • Cancel Signature RequestTool to cancel a signature request. Use after identifying the signature request to abort.
  • Close Ignisign Signature RequestTool to close an active signature request. Use when you need to end or abort a signature process.
  • Create SignerTool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
  • Create Webhook EndpointTool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications.
  • Delete DocumentTool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
  • Delete Ignisign Signature RequestTool to delete a signature request. Use when you need to permanently remove a signature request by its ID.
  • Delete SignerTool to delete a signer. Use when you need to remove a signer from a specific application environment after confirming signer ID.
  • Delete Webhook EndpointTool to delete a specific webhook endpoint. Use when you want to remove an existing webhook by its ID.
  • Get application contextTool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app.
  • Get Document InformationTool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID.
  • Get Missing Signer InputsTool 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 DetailsTool to retrieve detailed information for a specific signature request. Use after creating or listing a signature request to inspect its details.
  • Get Signature Request DocumentTool 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 o
  • Get Signature Request StatusTool 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 RequestsTool to retrieve a paginated list of signature requests for an application. Use after confirming the application ID and environment.
  • Get Signed DocumentTool 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
  • Get Signer Creation ConstraintsTool 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 ConstraintsTool to get signer input constraints. Use when you need to know which fields are required from signers for a given signer profile.
  • Get Signer InputsTool to retrieve inputs provided by a signer for a signature request. Use after a signer has completed their input steps to fetch submitted values.
  • Get Signer ProfileTool to retrieve a signer profile. Use after obtaining the signer profile ID.
  • Get Signer ProfilesTool to retrieve signer profiles. Use when listing all profiles for a given app environment after confirming app ID and environment.
  • Get Webhook DetailsTool to retrieve details of a specific webhook endpoint. Use after you have the webhook ID to inspect its URL, description, and creation timestamp.
  • Get WebhooksTool to list all webhook endpoints configured for an application environment. Use after confirming the application ID and environment.
  • Ignisign API AuthenticationTool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls.
  • Initialize DocumentTool 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 RequestTool to initialize a new signature request. Use when starting a signature flow in a specific application environment.
  • List DocumentsTool 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 docu
  • Provide Document Content Data JSONTool to provide JSON content for a document. Use when you need to attach or update the JSON data of a document.
  • Provide Document Content FileTool to provide file content for a document. Use after creating a document to attach its file content.
  • Provide Document Content Private FileTool to provide private content for a document via its SHA-256 hash. Use after creating a document placeholder and needing to submit the private content hash for signing.
  • Publish Signature RequestTool to publish a draft signature request. Use after adding all documents and signer details to the draft.
  • Search SignersTool to search for signers within an application. Use after obtaining application ID and environment. Allows optional filtering by name, email, or external ID.
  • Update Document InformationTool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation.
  • Update Signature RequestTool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending.
  • Update SignerTool to update details of an existing signer. Use after fetching a signer when you need to change its profile.
  • Update Webhook EndpointTool 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 wbh123 to http
Access, and who is in charge of it

You stay the boss of your Ignisign account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Ignisign account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Ignisign is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Ignisign and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Ignisign

Can an AI employee really work inside Ignisign?
Yes. It signs in to your own Ignisign account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Ignisign?
No. Nothing moves and nothing is replaced. Your records stay in Ignisign, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Ignisign account?
You paste in a key from your own Ignisign account. It is kept encrypted, and you can withdraw it from inside Ignisign whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Ignisign?
It has 36 ready-made tools in Ignisign today, among them Cancel Signature Request, Close Ignisign Signature Request and Create Signer. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Ignisign and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Ignisign and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Ignisign?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Ignisign is written down with what it did and when.