# How to connect Ignisign to Hermes Agent (paste one key, 32 tools)

> Connect Ignisign to Hermes with ClawLink: paste your Ignisign key once and 32 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/ignisign

Most guides for giving Hermes Agent Ignisign access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Ignisign setup: pair once in the browser and your always-on Hermes agent can act on Ignisign for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to Ignisign.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Ignisign** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect ignisign  # connect Ignisign (browser OAuth)
npx -y @useclawlink/cli actions ignisign  # list available actions
npx -y @useclawlink/cli run ignisign <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then connect Ignisign in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ignisign API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from Ignisign, summarize it in plain English, and point out anything that needs attention.

### Using a different agent?

The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Ignisign is connected in the dashboard, that agent calls the same 32 Ignisign tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Ignisign MCP for Hermes

Looking for a Ignisign MCP server for Hermes Agent? ClawLink connects Ignisign to Hermes Agent and exposes 32 Ignisign tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Ignisign integration](https://claw-link.dev/openclaw/ignisign) works the same way.

## What the Hermes Agent Ignisign integration can do

32 Ignisign tools are ready for Hermes Agent once the account is connected. The 28 below are the ones people reach for most; your agent can call all 32.

### 28 of 32 Ignisign tools for Hermes

| Tool | What it does |
|---|---|
| **Get application context** `ignisign_get_application_context` | Retrieve the global context of an application |
| **Get document information** `ignisign_get_document_information` | Retrieve document metadata by ID |
| **Get missing signer inputs** `ignisign_get_missing_signer_inputs` | Determine missing inputs needed for a signer in a specific signature profile |
| **Get signature request details** `ignisign_get_signature_request_details` | Retrieve detailed information for a specific signature request |
| **Get signature request document** `ignisign_get_signature_request_document` | Retrieve the document associated with a specific signature request |
| **Get signature requests** `ignisign_get_signature_requests` | Retrieves a paginated list of signature requests for a specific Ignisign application and |
| **Get signed document** `ignisign_get_signed_document` | Download the signed document (signature proof) for a signature request |
| **Get signer input constraints** `ignisign_get_signer_input_constraints` | Get signer input constraints |
| **Get signer inputs** `ignisign_get_signer_inputs` | Retrieves the inputs provided by a specific signer for a signature request |
| **Get signer profile** `ignisign_get_signer_profile` | Retrieve detailed information about a specific signer profile by its ID |
| **Get signer profiles** `ignisign_get_signer_profiles` | Retrieve all signer profiles for a specific Ignisign application environment |
| **Get webhooks** `ignisign_get_webhooks` | Retrieves all webhook endpoints configured for a specific Ignisign application environment |
| **List documents** `ignisign_list_documents` | Retrieve documents linked to a signature request |
| **Search signers** `ignisign_search_signers` | Search for signers within an application environment with pagination support |
| **API authentication** `ignisign_api_authentication` | Authenticate an application over Ignisign API and retrieve a JWT |
| **Create document** `ignisign_create_document` | Initialize a document for a signature request |
| **Create signer** `ignisign_create_signer` | Create a new signer |
| **Create webhook endpoint** `ignisign_create_webhook_endpoint` | Create a new webhook endpoint for an application |
| **Init signature request** `ignisign_init_signature_request` | Initialize a new signature request in Ignisign |
| **Provide document content data json** `ignisign_provide_document_content_data_json` | Provides JSON content to an existing document in Ignisign |
| **Provide document content file** `ignisign_provide_document_content_file` | Provide file content for a document |
| **Provide document content private file** `ignisign_provide_document_content_private_file` | Provides private document content by submitting its SHA-256 hash to IgniSign |
| **Publish signature request** `ignisign_publish_signature_request` | Publish a draft signature request |
| **Update document information** `ignisign_update_document_information` | Update document metadata |
| **Update signature request** `ignisign_update_signature_request` | Partially update a signature request in DRAFT state |
| **Update signer** `ignisign_update_signer` | Updates an existing signer's profile assignment |
| **Update webhook endpoint** `ignisign_update_webhook_endpoint` | Update an existing webhook endpoint |
| **Cancel signature request** `ignisign_cancel_signature_request` | Cancel (close) a signature request to terminate it |

## Example prompts

**Get Application Context**

> Pull the relevant data from Ignisign, summarize it in plain English, and point out anything that needs attention.

**Get Document Information**

> Pull the relevant data from Ignisign, summarize it in plain English, and point out anything that needs attention.

**Get Missing Signer Inputs**

> Pull the relevant data from Ignisign, summarize it in plain English, and point out anything that needs attention.

**Get Signature Request Details**

> Pull the relevant data from Ignisign, summarize it in plain English, and point out anything that needs attention.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Ignisign working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Ignisign API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ignisign account becomes available to the agent without you building credential management. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Ignisign. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right Ignisign actions to the runtime in a format your agent can reliably use. | 32 tools for Ignisign are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Ignisign to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Ignisign in the browser, and the 32 tools above work from chat. There is no SDK and no config file, and the Ignisign key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### Hermes paired but still can't use Ignisign
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

### Connection succeeds but no tools appear
Reconnect Ignisign from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling Ignisign tools
Ignisign tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Ignisign call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### Ignisign returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### API key setup works but results look incomplete
Double-check that the API key for Ignisign has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a Hermes Agent Ignisign integration?
Yes. ClawLink is the fastest way to connect Hermes to Ignisign: link your Ignisign account once in the browser and Hermes Agent can call the Ignisign API through 32 ready-made tools — no custom code or token handling.

### How do I connect Ignisign to Hermes with ClawLink?
Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Ignisign in the dashboard and Hermes can use it from the next message — no config files, and the Ignisign key you paste is stored server-side instead of in your environment.

### How long does it take to connect Ignisign to Hermes Agent?
About two minutes. Sign in, click Connect next to Ignisign in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Ignisign up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Ignisign working from chat.

### Hermes paired but still can't use Ignisign
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

## Related

- [GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows
- [Hermes PagerDuty integration](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services
- [Connect SafetyCulture](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.