# How to connect Ignisign to Grok Bot

```json
{
  "title": "How to connect Ignisign to Grok Bot",
  "toolkit": "Ignisign",
  "toolkit_slug": "ignisign",
  "framework": "Grok Bot",
  "framework_slug": "grok-bot",
  "url": "https://composio.dev/toolkits/ignisign/framework/grok-bot",
  "markdown_url": "https://composio.dev/toolkits/ignisign/framework/grok-bot.md",
  "updated_at": "2026-11-06T09:25:30.843Z"
}
```

## Introduction

Grok is xAI's assistant, and its bot builder lets you create a personal agent that holds context, runs skills, and connects to the apps you already use through plugins.
This guide explains how to connect Ignisign to a Grok bot using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a plugin, authenticate once, then ask your bot to work with Ignisign in plain language.
For exact tool slugs and parameter tables, see the [tool catalog in the Composio docs](https://docs.composio.dev/toolkits/ignisign).

## Also integrate Ignisign with

- [Claude Code](https://composio.dev/toolkits/ignisign/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/ignisign/framework/claude-cowork)
- [OpenAI Agents SDK](https://composio.dev/toolkits/ignisign/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/ignisign/framework/claude-agents-sdk)
- [Codex](https://composio.dev/toolkits/ignisign/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/ignisign/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/ignisign/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/ignisign/framework/atomic-agent)
- [Google ADK](https://composio.dev/toolkits/ignisign/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/ignisign/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/ignisign/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/ignisign/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/ignisign/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/ignisign/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/ignisign/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/ignisign/framework/autogen)

## TL;DR

Composio exposes 1,700+ apps to your Grok bot through a single connection, so you get:
- Connect to 1,700+ apps with on-demand tool loading, so you do not fill your context window with unnecessary tool definitions.
- Use programmatic tool calling through a remote workbench, letting the model write its own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
- Handle large tool responses outside the model context to keep conversations lean.

## Connect Ignisign to Grok Bot

### Connecting Ignisign to Grok Bot
Once Grok Bot is set up, you connect Ignisign entirely from its interface, and the whole flow takes under a minute.
### Set up Grok Bot
Get access. Grok Bot is included with Cursor Ultra, Cursor Premium Teams, and SuperGrok Heavy. Get the desktop app for macOS or Windows from [x.ai/bot](https://x.ai/bot) and sign in. An iPhone companion app is also available, and your bots sync across devices.
Create a bot. Pick a suggested role or define your own, then give it a short name, one primary job, and a short description of how it should work. Focused bots work best, because a clear role gives the bot more useful context over time.
### Connect Ignisign
### 1. Add the Composio plugin
Click the button. The Composio listing on x.ai opens and launches Grok Bot for you. If the app does not open on its own, click Add to Grok Bot.
[Add to Grok Bot](https://x.ai/bot/plugin/32661537)
Grok Bot opens the Composio plugin, showing its connector and skills. Click Add.
### 2. Authenticate
Go to the Installed section and click the Composio entry. You'll see its connector and skills listed.
Click Authenticate. You'll be taken to the Composio consent screen. Review the access it requests and click Authorize. Composio handles the OAuth handshake for you, so you never touch API keys or tokens.
### 3. Connect your Ignisign account
Back in the chat, ask your bot to connect to Ignisign or give it any Ignisign task.
For example, ask it to:
- "Start a new signature request for a contract"
- "Add a new signer to this application"
- "Delete a completed document by its ID"
It will prompt you to authenticate and authorize access.
That's it. Composio's tools are now available in your Grok bot, and your Ignisign account is ready to use.

## What is Grok Bot?

Grok is xAI's assistant, available as a chat interface and a bot builder for creating personal agents that run skills and connect to external apps.
With Composio Connect, your Grok bot can securely access apps like Ignisign through MCP without you sharing account credentials directly with the agent.

## What is the Ignisign MCP server, and what's possible with it?

The Ignisign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ignisign account. It provides structured and secure access to your electronic signature workflows, so your agent can perform actions like sending signature requests, managing documents, onboarding signers, and handling signature operations on your behalf.
- Automated signature request management: Let your agent create, cancel, or delete signature requests, streamlining the entire e-signature process from start to finish.
- Document initialization and deletion: Have the agent initialize new documents for signing or permanently delete documents when they're no longer needed.
- Signer onboarding and removal: Effortlessly add new signers to your application environment or remove existing ones as your workflows change.
- Webhook endpoint management: Allow your agent to create or delete webhook endpoints, enabling real-time notifications and integrations for signature events.
- Application context retrieval: Fetch global application settings and environment configurations so your agent always works with up-to-date information.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `IGNISIGN_API_AUTHENTICATION` | 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. |
| `IGNISIGN_CANCEL_SIGNATURE_REQUEST` | 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. |
| `IGNISIGN_CREATE_DOCUMENT` | 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. |
| `IGNISIGN_CREATE_SIGNER` | Create Signer | Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile. |
| `IGNISIGN_CREATE_WEBHOOK_ENDPOINT` | 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. |
| `IGNISIGN_DELETE_DOCUMENT` | Delete Document | Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete. |
| `IGNISIGN_DELETE_SIGNATURE_REQUEST` | 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. |
| `IGNISIGN_DELETE_SIGNER` | 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. |
| `IGNISIGN_DELETE_WEBHOOK_ENDPOINT` | Delete Webhook Endpoint | Deletes a webhook endpoint by ID. When the response contains a list, returns the remaining webhook endpoints; a successful empty response returns no list. |
| `IGNISIGN_GET_APPLICATION_CONTEXT` | Get application context | Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app. |
| `IGNISIGN_GET_DOCUMENT_INFORMATION` | Get Document Information | Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID. |
| `IGNISIGN_GET_MISSING_SIGNER_INPUTS` | Get Missing Signer Inputs | Retrieve missing inputs for a signer and profile. If the direct lookup fails, the tool estimates missing fields from profile constraints and available signer search results; a failed or unmatched search can cause provided fields to be reported as missing. |
| `IGNISIGN_GET_SIGNATURE_REQUEST_DETAILS` | 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. |
| `IGNISIGN_GET_SIGNATURE_REQUEST_DOCUMENT` | Get Signature Request Document | Downloads a document's original file. Provide a document ID to download it directly, or omit it to resolve the first document ID from the specified signature request; a supplied document ID is not checked against that request. |
| `IGNISIGN_GET_SIGNATURE_REQUESTS` | 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. |
| `IGNISIGN_GET_SIGNED_DOCUMENT` | 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) |
| `IGNISIGN_GET_SIGNER_INPUT_CONSTRAINTS` | 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. |
| `IGNISIGN_GET_SIGNER_INPUTS` | Get Signer Inputs | Retrieve available signer input values from a signature request's context. The tool matches the signer in the context and derives inputs from listed provided-input names or a limited set of common fields; values may be missing. |
| `IGNISIGN_GET_SIGNER_PROFILE` | 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. |
| `IGNISIGN_GET_SIGNER_PROFILES` | 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. |
| `IGNISIGN_GET_WEBHOOKS` | 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. |
| `IGNISIGN_INIT_SIGNATURE_REQUEST` | 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. |
| `IGNISIGN_LIST_DOCUMENTS` | 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. |
| `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_DATA_JSON` | 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. |
| `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_FILE` | Provide Document Content File | Tool to provide file content for a document. Use after creating a document to attach its file content. |
| `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_PRIVATE_FILE` | 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. |
| `IGNISIGN_PUBLISH_SIGNATURE_REQUEST` | Publish Signature Request | Tool to publish a draft signature request. Use after adding all documents and signer details to the draft. |
| `IGNISIGN_SEARCH_SIGNERS` | 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. |
| `IGNISIGN_UPDATE_DOCUMENT_INFORMATION` | Update Document Information | Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation. |
| `IGNISIGN_UPDATE_SIGNATURE_REQUEST` | Update Signature Request | Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending. |
| `IGNISIGN_UPDATE_SIGNER` | 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). |
| `IGNISIGN_UPDATE_WEBHOOK_ENDPOINT` | Update Webhook Endpoint | Updates an existing webhook endpoint's destination URL and optionally its description. The destination URL is required even when changing the description. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, your Grok bot can access the Ignisign MCP server through Composio to run the actions you authorize, using plain language in the chat.

## Complete Code

None listed.

## Conclusion

### Way Forward
Now that Ignisign is connected, extend your setup by connecting the other apps you already use every day, so your Grok bot can run true cross-app workflows end to end.
- Connect Calendar to turn threads into scheduled meetings automatically.
- Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
- Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
- Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, your bot can coordinate multiple tools safely and reliably in one conversation.

## How to build Ignisign MCP Agent with another framework

- [Claude Code](https://composio.dev/toolkits/ignisign/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/ignisign/framework/claude-cowork)
- [OpenAI Agents SDK](https://composio.dev/toolkits/ignisign/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/ignisign/framework/claude-agents-sdk)
- [Codex](https://composio.dev/toolkits/ignisign/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/ignisign/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/ignisign/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/ignisign/framework/atomic-agent)
- [Google ADK](https://composio.dev/toolkits/ignisign/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/ignisign/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/ignisign/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/ignisign/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/ignisign/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/ignisign/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/ignisign/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/ignisign/framework/autogen)

## Related Toolkits

- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [ActiveMerge](https://composio.dev/toolkits/active_merge) - ActiveMerge is a document automation platform for generating documents, images, merged files, and e-signature workflows. It helps teams turn templates and stored files into finished, shareable documents faster.
- [Affinda](https://composio.dev/toolkits/affinda) - Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.
- [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease.
- [Airparser](https://composio.dev/toolkits/airparser) - Airparser is an AI-powered parser for extracting structured data from emails, documents, PDFs, and files. It turns messy inbound content into clean fields your apps and workflows can use.
- [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training.
- [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses.
- [Apitemplate](https://composio.dev/toolkits/apitemplate_io) - Apitemplate is an API service for generating PDFs and images from reusable templates. It turns JSON data into branded documents and visuals without custom rendering code.
- [Archive.org](https://composio.dev/toolkits/archive_org) - Archive.org is the Internet Archive's digital library of websites, books, audio, video, and images. Use it to preserve, explore, and access historical web captures and public-domain media.
- [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files.
- [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently.
- [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price.
- [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere.
- [Box MCP](https://composio.dev/toolkits/box_mcp) - Box MCP is Box's hosted MCP server that exposes enterprise files, folders, and metadata. It provides secure, centralized access to corporate content for search and management.
- [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code.
- [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more.
- [CertSeal](https://composio.dev/toolkits/cert_seal) - CertSeal is an API platform for issuing and managing verifiable digital certificates. Use it to automate trusted certificate workflows for recipients, batches, designs, and webhooks.
- [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Ignisign MCP?

With a standalone Ignisign MCP server, the agents and LLMs can only access a fixed set of Ignisign tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ignisign and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Grok Bot?

Yes, you can. Grok Bot fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Ignisign tools.

### Can I manage the permissions and scopes for Ignisign while using Tool Router?

Yes, absolutely. You can configure which Ignisign scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Ignisign data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
