How to connect Process Street to Hermes Agent
Connect Process Street to Hermes with ClawLink: paste your Process Street key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine.
Process StreetAPI KEYMCPProcess Street supports creating and running checklists, SOPs, and workflows, helping teams automate recurring processes and track compliance.. Once connected, Hermes Agent can read and act on Process Street from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Process Street 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 Process Street setup: pair once in the browser and your always-on Hermes agent can act on Process Street 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 Process Street.
1Install 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 Process Street
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Process Street?"
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 testThen connect Process Street in the ClawLink dashboard — paste your Process Street API key once.
Verify the connection by asking Hermes:
Use Process Street to find data set rows 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 loginlogin opens the same browser approval and stores a credential locally. Once Process Street is connected in the dashboard, that agent calls the same 5 Process Street tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Process Street MCP for Hermes
Looking for a Process Street MCP server for Hermes Agent? ClawLink connects Process Street to Hermes Agent and exposes 5 Process Street tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Process Street integration works the same way.
What the Hermes Agent Process Street integration can do
5 Process Street tools are ready for Hermes Agent once the account is connected.
All 5 Process Street tools for Hermes
| Tool | What it does |
|---|---|
Find data set rows process_street_find_data_set_rows | Retrieves records from a Process Street data set with optional filtering by column values |
List workflows process_street_list_workflows | Retrieves a list of all workflows available in the Process Street account |
Complete workflow run process_street_complete_workflow_run | Marks an entire workflow run as completed in Process Street |
Create workflow run process_street_create_workflow_run | Creates a new workflow run from a specified workflow template |
Undelete workflow run process_street_undelete_workflow_run | Restores a previously deleted workflow run in Process Street |
Try it: find the Process Street tool you need
Browse the 5 Process Street tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Process Street to find data set rows and walk me through the result in plain English.
List the relevant items in Process Street, group them by priority, and recommend what Hermes should do next.
Use Process Street to complete workflow run and walk me through the result in plain English.
Create it in Process Street for me, then confirm the important fields before you finish.
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 Process Street working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Process Street API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Process Street 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 Process Street. | 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 Process Street actions to the runtime in a format your agent can reliably use. | 5 tools for Process Street are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Process Street 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 Process Street in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Process Street 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 Process Street
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 Process Street 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 Process Street tools
Process Street 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 Process Street 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.
Process Street 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 Process Street 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 Process Street integration?
Yes. ClawLink is the fastest way to connect Hermes to Process Street: link your Process Street account once in the browser and Hermes Agent can call the Process Street API through 5 ready-made tools — no custom code or token handling.
How do I connect Process Street 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 Process Street in the dashboard and Hermes can use it from the next message — no config files, and the Process Street key you paste is stored server-side instead of in your environment.
How long does it take to connect Process Street to Hermes Agent?
About two minutes. Sign in, click Connect next to Process Street in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Process Street 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 Process Street working from chat.
Hermes paired but still can't use Process Street
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.
