How to connect Wrike to Hermes Agent
Connect Wrike to Hermes with ClawLink in one click — 144 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
WrikeOAUTH2MCPManage projects, tasks, and team workflows at scale. Once connected, Hermes Agent can read and act on Wrike from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Wrike 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 Wrike setup: pair once in the browser and your always-on Hermes agent can act on Wrike for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
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. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
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.Setup
It takes three steps to connect Hermes to Wrike.
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 Wrike
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Wrike?"
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 Wrike in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Pull the relevant data from Wrike, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Wrike is connected in the dashboard, that agent calls the same 144 Wrike tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Wrike MCP for Hermes
Looking for a Wrike MCP server for Hermes Agent? ClawLink connects Wrike to Hermes Agent and exposes 144 Wrike tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Wrike integration works the same way.
What the Hermes Agent Wrike integration can do
144 Wrike tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 144.
30 of 144 Wrike tools for Hermes
| Tool | What it does |
|---|---|
Fetch all tasks wrike_fetch_all_tasks | Fetches tasks from a Wrike account, allowing filtering by status, due date, and subfolder |
Get account information wrike_get_account_information | Retrieves detailed Wrike account information, where the response content is influenced by |
Get all custom fields wrike_get_all_custom_fields | Retrieves all custom field definitions (including ID, name, type, and settings) from the Wrike |
Get all webhooks wrike_get_all_webhooks | Retrieve a list of all webhooks created using the same API token |
Get approvals wrike_get_approvals | Retrieve all approvals accessible to the authenticated user |
Get approvals by IDS wrike_get_approvals_by_ids | Retrieve specific Wrike approvals by their IDs (up to 100) |
Get async job wrike_get_async_job | Retrieve status and details for an asynchronous job in Wrike |
Get attachments wrike_get_attachments | Retrieve multiple Wrike attachments by their IDs (up to 100) |
Get attachments download wrike_get_attachments_download | Download a Wrike attachment file |
Get attachments preview wrike_get_attachments_preview | Download a preview version of a Wrike attachment |
Get attachments URL wrike_get_attachments_url | Get a public access URL for a Wrike attachment |
Get bookings wrike_get_bookings | Retrieves one or more Wrike bookings by their IDs |
Get colors wrike_get_colors | Query the list of available colors in Wrike |
Get comments wrike_get_comments | Retrieve all comments accessible to the authorized user |
Get comments by IDS wrike_get_comments_by_ids | Retrieve multiple Wrike comments by their IDs |
Get contact hourly rates wrike_get_contact_hourly_rates | Retrieve hourly budget rates for up to 100 Wrike contacts |
Get contact timelogs wrike_get_contact_timelogs | Retrieve all timelog records created by a specific contact in Wrike |
Get contacts wrike_get_contacts | Retrieves a list of Wrike contacts (e.g., team members, clients, collaborators); response |
Get contacts history wrike_get_contacts_history | Access field modification history for Wrike contacts |
Get custom item types wrike_get_custom_item_types | Retrieve all custom item types from Wrike |
Get dependencies wrike_get_dependencies | Retrieve one or more Wrike dependencies by their IDs (up to 100) |
Get folder bookings wrike_get_folder_bookings | Query bookings for a specific folder in Wrike |
Get folders wrike_get_folders | Retrieves folders and/or projects from Wrike, with filters; when using nextPageToken, all |
Get folders approvals wrike_get_folders_approvals | Retrieve all approvals from a specific Wrike folder |
Get folders attachments wrike_get_folders_attachments | Retrieve all attachments from a specific Wrike folder |
Get folders by IDS wrike_get_folders_by_ids | Retrieve multiple Wrike folders by their IDs |
Get folders comments wrike_get_folders_comments | Retrieve comments from a specific Wrike folder |
Get folders history wrike_get_folders_history | Access field modification history for Wrike folders |
Get folders hourly wrike_get_folders_hourly | Retrieve hourly budget rates for a specific Wrike folder |
Get folders rollups wrike_get_folders_rollups | Query rollup settings for items in a folder |
Try it: find the Wrike tool you need
Browse the 30 Wrike tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Wrike, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Wrike, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Wrike, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Wrike, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Wrike working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Wrike app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Wrike through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Wrike. | 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 Wrike actions to the runtime in a format your agent can reliably use. | 144 tools for Wrike are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Wrike 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 Wrike in the browser, and the 144 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Wrike
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 Wrike 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 Wrike tools
Wrike 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 Wrike 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.
Wrike 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Wrike and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a Hermes Agent Wrike integration?
Yes. ClawLink is the fastest way to connect Hermes to Wrike: link your Wrike account once in the browser and Hermes Agent can call the Wrike API through 144 ready-made tools — no custom code or token handling.
How do I connect Wrike 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 Wrike in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.
How long does it take to connect Wrike to Hermes Agent?
About two minutes. Sign in, click Connect next to Wrike in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Wrike up myself?
The alternative to ClawLink is usually manual OAuth app 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 Wrike working from chat.
Hermes paired but still can't use Wrike
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.
