# How to connect Ignav Flights to Hermes Agent (paste one key, 5 tools)

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

Web version: https://claw-link.dev/hermes/ignav-flights

Most guides for giving Hermes Agent Ignav Flights 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 Ignav Flights setup: pair once in the browser and your always-on Hermes agent can act on Ignav Flights 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 Ignav Flights.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Ignav Flights** — 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 ignav-flights  # connect Ignav Flights (browser OAuth)
npx -y @useclawlink/cli actions ignav-flights  # list available actions
npx -y @useclawlink/cli run ignav-flights <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 Ignav Flights in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ignav Flights API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from Ignav Flights, 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 Ignav Flights is connected in the dashboard, that agent calls the same 5 Ignav Flights 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).

## Ignav Flights MCP for Hermes

Looking for a Ignav Flights MCP server for Hermes Agent? ClawLink connects Ignav Flights to Hermes Agent and exposes 5 Ignav Flights 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 Ignav Flights integration](https://claw-link.dev/openclaw/ignav-flights) works the same way.

## What the Hermes Agent Ignav Flights integration can do

5 Ignav Flights tools are ready for Hermes Agent once the account is connected.

### All 5 Ignav Flights tools for Hermes

| Tool | What it does |
|---|---|
| **Get booking links** `ignav_flights_get_booking_links` | Get current direct airline or OTA booking links for a recent Ignav fare result or a manually |
| **Search airports** `ignav_flights_search_airports` | Find supported airport-level IATA codes by code, airport name, city, country, or metro-style |
| **Search flexible fares** `ignav_flights_search_flexible_fares` | Search one or two ordered flight legs for multi-city, open-jaw, or other flexible trips |
| **Search one way fares** `ignav_flights_search_one_way_fares` | Search complete one-way flight itineraries between two airport-level IATA codes on a future date |
| **Search round trip fares** `ignav_flights_search_round_trip_fares` | Search complete round-trip itineraries between two airport-level IATA codes with outbound and |

## Example prompts

**Get Booking Links**

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

**Search Airports**

> Search Ignav Flights for what I need, summarize the results, and tell me the next best action.

**Search Flexible Fares**

> Search Ignav Flights for what I need, summarize the results, and tell me the next best action.

**Search One Way Fares**

> Search Ignav Flights for what I need, summarize the results, and tell me the next best action.

## 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 Ignav Flights working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Ignav Flights API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ignav Flights 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 Ignav Flights. | 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 Ignav Flights actions to the runtime in a format your agent can reliably use. | 5 tools for Ignav Flights are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Ignav Flights 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 Ignav Flights in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Ignav Flights 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 Ignav Flights
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 Ignav Flights 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 Ignav Flights tools
Ignav Flights 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 Ignav Flights 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.

### Ignav Flights 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 Ignav Flights 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 Ignav Flights integration?
Yes. ClawLink is the fastest way to connect Hermes to Ignav Flights: link your Ignav Flights account once in the browser and Hermes Agent can call the Ignav Flights API through 5 ready-made tools — no custom code or token handling.

### How do I connect Ignav Flights 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 Ignav Flights in the dashboard and Hermes can use it from the next message — no config files, and the Ignav Flights key you paste is stored server-side instead of in your environment.

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

### Why use ClawLink instead of wiring Ignav Flights 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 Ignav Flights working from chat.

### Hermes paired but still can't use Ignav Flights
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

- [Cal.com](https://claw-link.dev/hermes/cal) — Schedule and manage bookings through Cal.com
- [Connect Bookingmood](https://claw-link.dev/hermes/bookingmood) — Bookingmood provides flexible, commission-free booking software for rental businesses of all sizes, enabling seamless integration with your website.
- [Hermes Eventbrite integration](https://claw-link.dev/hermes/eventbrite) — Create and manage events, tickets, and attendees