Ignisign logo
ConnectorIgnisign

Ignisign integration for Claude and Codex

Create a Ignisign connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Ignisign from Claude

Add the Ignisign connection to a Space that runs Claude, then use it from every channel in that Space.

Use Ignisign from Codex

Add the Ignisign connection to a Space that runs Codex, then use it from every channel in that Space.

Use Ignisign from Sidekick

Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.

Documents & Forms

What the Ignisign connector can do

IgniSign is an electronic signature platform covering signers, documents, and signature requests through a token-based API. A type.com Space connected to IgniSign can ask Claude to authenticate the connection, initialize a document on a request, create a new signer, register a webhook, or cancel a request that no longer needs to go out.

One connection, many Spaces

Connect Ignisign once, then decide which Spaces can use it in threads, skills, automations, and coding work.

What teams do with Ignisign in type.com

Attach a document to a new signature request

Initialize a document on an existing signature request once the request itself has been created.

Try asking
Initialize this contract PDF as the document on our latest IgniSign signature request.

Onboard a new signer

Create a signer under an existing signer profile so they can be added to upcoming signature requests.

Try asking
Create an IgniSign signer for Alex Kim using our standard employee signer profile.

Cancel a request sent to the wrong recipient

Cancel a signature request that was sent by mistake, stopping the workflow before anyone signs it.

Try asking
Cancel the IgniSign signature request we sent to the wrong email this morning.

Representative actions

  • Ignisign API Authentication

    Authenticates the application and returns a bearer token for further API calls.

  • Cancel Signature Request

    Closes out a signature request before anyone finishes signing it, ending the workflow for good.

  • Initialize Document

    Attaches a file to a signature request that has already been started.

  • Create Signer

    Onboards a new signer under a selected signer profile.

  • Create Webhook Endpoint

    Registers a webhook endpoint for an application to receive event notifications.

Connection

API and auth details

IgniSign documents an electronic-signature API with bearer API keys and signature-process tokens. Integrations can create signature requests, manage documents, signers, signer profiles, proofs, seals, bare signatures, log capsules, user invitations, webhooks, and embedded signing workflows.

FAQ

Questions people ask before connecting Ignisign

Can Claude manage IgniSign signature requests?

Yes. With IgniSign connected to a Space, Claude can initialize documents, create signers, register webhooks, and cancel requests from a type.com thread.

How does type.com authenticate with IgniSign?

IgniSign uses an API key, added once by an admin when the connection is created, who then controls which Spaces can use it.

Can IgniSign signature requests run on a schedule?

Yes. A recurring task, such as checking for unsigned requests each day, can be set up as a type.com automation that posts reminders to a channel.

Is this the same as a Ignisign MCP server?

Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More documents & forms connectors

All Documents & Forms integrations