How to connect Trigger.dev to Hermes Agent (paste one key, 10 tools)

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

1
Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2
Connect Trigger.dev
Paste your API key in the dashboard.
3
Use it from chat
Ask Hermes Agent: "What can you do with Trigger.dev?"

Install by command

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

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 Trigger.dev in the ClawLink dashboard — paste your Trigger.dev API key once.

Verify the connection by asking Hermes:

Use Trigger.dev to execute trql query and walk me through the result in plain English.

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:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Trigger.dev is connected in the dashboard, that agent calls the same 10 Trigger.dev tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Trigger.dev MCP for Hermes

Looking for a Trigger.dev MCP server for Hermes Agent? ClawLink connects Trigger.dev to Hermes Agent and exposes 10 Trigger.dev tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Trigger.dev integration works the same way.

What the Hermes Agent Trigger.dev integration can do

10 Trigger.dev tools are ready for Hermes Agent once the account is connected.

All 10 Trigger.dev tools for Hermes

Tool	What it does
Execute trql query `trigger_dev_execute_trql_query`	Run one read-only Trigger.dev Query Language SELECT statement for custom run analytics and
Get batch `trigger_dev_get_batch`	Retrieve a task batch's status, run IDs, completion counts, and item errors
Get batch results `trigger_dev_get_batch_results`	Retrieve the success or failure outcome and encoded output for every run in a completed task
Get error `trigger_dev_get_error`	Retrieve one Trigger.dev error group's message, occurrence history, affected versions, and
Get run `trigger_dev_get_run`	Retrieve one run's status, timing, payload, output, attempts, metadata, relationships
Get run result `trigger_dev_get_run_result`	Retrieve one run's compact success or failure result, including its encoded output or error and
List errors `trigger_dev_list_errors`	Return one forward page of Trigger.dev error groups, optionally filtered by task, version
List runs `trigger_dev_list_runs`	Return one forward page of runs in the connected environment, optionally filtered by time
Batch trigger task `trigger_dev_batch_trigger_task`	Start multiple runs of one deployed Trigger.dev task in one provider-side batch and return the
Trigger task `trigger_dev_trigger_task`	Start one run of a deployed Trigger.dev task and return the new run ID

Try it: find the Trigger.dev tool you need

Browse the 10 Trigger.dev tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Use Trigger.dev to execute trql query and walk me through the result in plain English.

Pull the relevant data from Trigger.dev, 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 Trigger.dev working from chat.

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

ClawLink vs. Composio

Composio also exposes Trigger.dev 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 Trigger.dev in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Trigger.dev key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

Hermes paired but still can't use Trigger.dev

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 Trigger.dev 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 Trigger.dev tools

Trigger.dev 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 Trigger.dev 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.

Trigger.dev 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 Trigger.dev has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a Hermes Agent Trigger.dev integration?

Yes. ClawLink is the fastest way to connect Hermes to Trigger.dev: link your Trigger.dev account once in the browser and Hermes Agent can call the Trigger.dev API through 10 ready-made tools — no custom code or token handling.

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

How long does it take to connect Trigger.dev to Hermes Agent?

About two minutes. Sign in, click Connect next to Trigger.dev in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring Trigger.dev up myself?

Hermes paired but still can't use Trigger.dev

How to connect Trigger.dev to Hermes Agent

Setup

Install and pair

Connect Trigger.dev

Use it from chat