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

Create a Ignisign connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Ignisign connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Ignisign connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
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.
Connect Ignisign once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Initialize a document on an existing signature request once the request itself has been created.
Initialize this contract PDF as the document on our latest IgniSign signature request.
Create a signer under an existing signer profile so they can be added to upcoming signature requests.
Create an IgniSign signer for Alex Kim using our standard employee signer profile.
Cancel a signature request that was sent by mistake, stopping the workflow before anyone signs it.
Cancel the IgniSign signature request we sent to the wrong email this morning.
Authenticates the application and returns a bearer token for further API calls.
Closes out a signature request before anyone finishes signing it, ending the workflow for good.
Attaches a file to a signature request that has already been started.
Onboards a new signer under a selected signer profile.
Registers a webhook endpoint for an application to receive event notifications.
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.
Yes. With IgniSign connected to a Space, Claude can initialize documents, create signers, register webhooks, and cancel requests from a type.com thread.
IgniSign uses an API key, added once by an admin when the connection is created, who then controls which Spaces can use it.
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.
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.
Connect Algodocs to Claude in type.com to confirm your account, list document extractors, and browse folders before processing a document batch.
Connect API2PDF to Claude in type.com to turn HTML into branded PDFs, extract specific pages, or convert PDFs to HTML from a shared thread.
Connect Aryn to Claude in type.com to organize DocSets, pull parsed documents, and plan queries from a shared thread.
Connect Basin to Claude in type.com to create forms, add webhooks, and organize projects for form data in a thread.