How to connect Webflow to Hermes Agent
Connect Webflow to Hermes Agent with ClawLink: paste a Webflow site token once and 51 tools work from chat. No OAuth app to register, no MCP server to run, no config file.
WebflowAPI KEYMCPBuild and manage websites, CMS collections, and assets. Once connected, Hermes Agent can read and act on Webflow from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Webflow 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 Webflow setup: pair once in the browser and your always-on Hermes agent can act on Webflow 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 Webflow.
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 Webflow
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Webflow?"
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 Webflow in the ClawLink dashboard — paste your Webflow API key once.
Verify the connection by asking Hermes:
Call webflow_list_webflow_sites and show me the sites the connection can see, then call webflow_get_site_info for each site_id and tell me which site each displayName corresponds to.
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 Webflow is connected in the dashboard, that agent calls the same 51 Webflow tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Webflow MCP for Hermes
Looking for a Webflow MCP server for Hermes Agent? ClawLink connects Webflow to Hermes Agent and exposes 51 Webflow tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Webflow integration works the same way.
Every route to Webflow's API starts with a credential, so let's be exact about this one: you paste a Webflow site token, created in Site settings > Apps & integrations > API access by a site administrator. What the hosted flow removes is everything a token normally drags in: the OAuth app registration, the MCP server you would keep running, and the config block in ~/.hermes/config.yaml. Webflow's own MCP server is the current answer the engines teach, and it is a remote OAuth server that needs Node.js 22.3.0 or higher plus a Designer companion app for canvas work. With ClawLink you paste the token once in the dashboard and the 51 tools below work from Hermes chat. Your site's plan determines the rate limits and the token's scopes bound what the agent can do.
Webflow MCP for Hermes: the routes, and what each requires
The answer engines now lead with Webflow's official MCP server, which is OAuth-based and carries MCP 2.0 governance controls. The three routes in this space are genuinely different tradeoffs:
- Webflow's official MCP server is Webflow's first-party answer: a remote server exposing Data and Designer APIs as MCP tools, with governance controls and Postman Agent Mode support. The requirements are real: Node.js 22.3.0 or higher, an OAuth authorization where only site owners and admins can approve the app, and a Designer companion app that must stay open in the Webflow Designer for canvas tools to work. Its Designer API tools edit the live canvas (elements, styles, variables); its Data tools cover CMS and assets.
- ClawLink connects with a pasted site token and exposes 51 Data API tools in Hermes chat: CMS collections and items, assets and folders, pages and site metadata, orders, form submissions, and webhooks. What we do not serve: Webflow's Designer API canvas-editing tools, which is exactly what the official MCP's companion app governs. The connection here also cannot reach Webflow's custom code endpoints, because site tokens never can.
- A self-built integration using a site token directly (the API access section of Site settings) or a registered Webflow App gives you full control, at the cost of owning scopes, rate-limit handling, and any server plumbing yourself. It is the route the config-file guides teach, and it is the one this page's hosted setup replaces.
All three routes call the same Webflow API family with the same per-plan rate limits. The differences are the credential (site token versus OAuth app), the runtime (nothing to run versus Node plus a companion app), and which API surface is reachable (Data API versus Designer canvas tools).
What the Hermes Agent Webflow integration can do
51 Webflow 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 51.
30 of 51 Webflow tools for Hermes
| Tool | What it does |
|---|---|
Create asset folder webflow_create_asset_folder | Create a new asset folder in a site |
Create collection webflow_create_collection | Create a new Webflow CMS collection |
Create collection item webflow_create_collection_item | Create a new item in a Webflow collection |
Create live collection item webflow_create_live_collection_item | Create a collection item and publish live |
Get asset webflow_get_asset | Retrieves detailed information about a specific asset by its ID from a Webflow site |
Get asset folder webflow_get_asset_folder | Retrieve details about a specific Asset Folder in Webflow |
Get collection webflow_get_collection | Retrieves a specific collection by its ID from a Webflow site |
Get collection item webflow_get_collection_item | Retrieves a specific item from a Webflow collection |
Get component properties webflow_get_component_properties | Get the default property values of a component definition |
Get custom domains webflow_get_custom_domains | Retrieve all custom domains associated with a specific Webflow site |
Get item inventory webflow_get_item_inventory | Retrieves the current inventory levels for a specific SKU item in a Webflow e-commerce site |
Get live collection item webflow_get_live_collection_item | Retrieves details of a selected Collection live Item from Webflow |
Get order webflow_get_order | Retrieves detailed information about a specific order in Webflow |
Get page webflow_get_page | Retrieve metadata for a single Webflow page by page_id |
Get page dom webflow_get_page_dom | Retrieve the DOM/content node structure for a Webflow static page |
Get site info webflow_get_site_info | Retrieves detailed information about a specific Webflow site |
Get token authorized by webflow_get_token_authorized_by | Retrieve information about the user who authorized the access token |
List asset folders webflow_list_asset_folders | List all asset folders within a given Webflow site |
List assets webflow_list_assets | Retrieve all assets (images, files) uploaded to a Webflow site |
List collection items webflow_list_collection_items | Retrieves a list of items from a specified collection in Webflow |
List collections webflow_list_collections | Retrieves a list of all collections for a given Webflow site |
List comment threads webflow_list_comment_threads | List all comment threads for a Webflow site |
List form submissions webflow_list_form_submissions | Retrieves a list of form submissions for a specific Webflow site |
List orders webflow_list_orders | Retrieves a list of all orders for a specified Webflow site using the GET |
List pages webflow_list_pages | Retrieves a list of all pages for a specified Webflow site |
List webflow sites webflow_list_webflow_sites | Retrieves a list of all Webflow sites accessible to the authenticated user |
List webhooks webflow_list_webhooks | List all App-created Webhooks registered for a given site |
Create bulk collection items webflow_create_bulk_collection_items | Create one or multiple items in a Webflow CMS Collection across multiple locales |
Create collection field webflow_create_collection_field | Create a custom field in a Webflow collection |
Fulfill order webflow_fulfill_order | Allows you to mark an order as fulfilled in Webflow's e-commerce system |
Try it: find the Webflow tool you need
Browse the 30 Webflow tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Call webflow_list_webflow_sites and show me the sites the connection can see, then call webflow_get_site_info for each site_id and tell me which site each displayName corresponds to.
List my collections with webflow_list_collections (site_id from the sites list), pick the Blog collection, then create an item with webflow_create_collection_item: field_data with name and slug for the attached article, is_draft true. Show me the draft before publishing.
Create the attached job posting in the Jobs collection with webflow_create_live_collection_item so it publishes immediately, and confirm the published URL.
Call webflow_list_assets with the site_id and list the 20 largest assets, their types, and their folders.
Webflow tool names and arguments that trip agents up
Verified 2026-08-02 against the live Composio schemas (backend.composio.dev/api/v3.1/tools/<SLUG>) and Webflow's Data API docs. No prod call history exists for this integration yet, so these are schema and doc facts, not observed failures:
- The real site-listing tool is
webflow_list_webflow_sitesand the site-info tool iswebflow_get_site_info(requiressite_id). Agents that guesswebflow_list_sitesorwebflow_get_siteget a tool-not-found error; both names do not exist in the catalog. webflow_create_collection_itemrequirescollection_idandfield_data, andfield_datamust includenameandslug;is_draftdefaults to false, so a call without it creates a live-pending item rather than a draft.webflow_create_live_collection_itemis the publish-now variant: it bypasses the staged workflow and puts the item on the live site directly.skip_invalid_filesdefaults to true, so invalid file references are dropped silently.webflow_publish_siterequiressite_idand publishes all staged changes. Publishing is capped at one successful publish per minute per Webflow's docs, so repeated publish calls in a loop hit the 429 limit.webflow_create_collectionrequiressite_id,display_name, andsingular_name; theslugis generated from the display name if omitted. Collection names must be distinct within a site.- All Data API calls carry the rate limit of the token's site plan: 60 requests/minute on Starter and Basic, 120 on CMS, eCommerce, and Business. Agents polling a site repeatedly burn this window quickly.
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 Webflow working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Webflow API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Webflow 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 Webflow. | 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 Webflow actions to the runtime in a format your agent can reliably use. | 51 tools for Webflow are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Webflow 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 Webflow in the browser, and the 51 tools above work from chat. There is no SDK and no config file, and the Webflow 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 Webflow
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 Webflow 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 Webflow tools
Webflow 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 Webflow 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.
Webflow 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.
Too Many Requests
Webflow's literal 429 error body is {"message": "Too Many Requests", "code": "too_many_requests"}. The Data API allows 60 requests per minute on Starter and Basic plans and 120 on CMS, eCommerce, and Business plans, per token, and publishing is capped at one successful publish per minute. The Retry-After header tells the agent how long to wait (typically 60 seconds); retrying faster does not help. Have the agent batch collection-item reads and spread writes out. Not yet seen in prod for this integration (zero executions recorded), but this is the limit every Webflow plan carries.
Ask the agent to diagnose it:
Stop and wait for the Retry-After window. Then continue the remaining calls one at a time, and tell me how many requests remain in this minute window.Webflow 401 invalid access token while the account is connected
No prod instances recorded for this integration yet, so this card is grounded in Webflow's docs rather than real calls. With a pasted token, a 401 means the token itself is dead: revoked in Site settings, or expired after 365 consecutive days of inactivity (any successful API call resets the inactivity clock). The hosted flow cannot refresh a dead token, so the fix is a new one: regenerate it in Site settings > Apps & integrations > API access and reconnect Webflow from the dashboard. Site tokens also cannot reach authorization, custom code, or workspace activity log endpoints at all, so calls against those fail regardless of token validity.
Ask the agent to diagnose it:
Reconnect Webflow from the dashboard with a freshly generated site token, then retry the same call in a fresh chat.Webflow 403 insufficient permissions on one collection while others work
A 403 with other calls working means the token lacks the scope or the role for that operation. Webflow fixes the scope at token creation, and its own guidance is to mint a new token when you need new scopes rather than reusing one. The practical hosted-flow version: generate a token with the scopes the workflow needs (CMS scopes for collection writes, asset scopes for uploads) and reconnect. Also check roles: only site administrators can create site tokens, and a non-admin Webflow user cannot mint one at all. Not yet seen in prod for this integration.
Ask the agent to diagnose it:
List which Webflow tools fail and which succeed. If the failing ones need broader scopes, I will mint a new token with those scopes and you reconnect with it.API key setup works but results look incomplete
Double-check that the API key for Webflow 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 Webflow integration?
Yes. ClawLink is the fastest way to connect Hermes to Webflow: link your Webflow account once in the browser and Hermes Agent can call the Webflow API through 51 ready-made tools — no custom code or token handling.
How do I connect Webflow 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 Webflow in the dashboard and Hermes can use it from the next message — no config files, and the Webflow key you paste is stored server-side instead of in your environment.
How long does it take to connect Webflow to Hermes Agent?
About two minutes. Sign in, click Connect next to Webflow in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Webflow 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 Webflow working from chat.
Do I need a Webflow OAuth app for this?
No. The OAuth route (Webflow's own MCP server and Webflow Apps) registers an app and runs an authorization flow. ClawLink uses a site token instead: you paste it once in the dashboard, and the connection calls the Data API on your site's behalf. The tradeoff is the token's scopes: they are fixed at creation, so if the agent needs broader access later, you mint a new token with the needed scopes and reconnect. Creating a site token requires site administrator rights in Webflow.
Which Webflow sites can the agent access?
Site tokens are created per site, so a connection with a site token sees the site the token was created for. For access across multiple sites you need a workspace-level token or a Webflow App with OAuth, which is the manual route this page's setup replaces. If the agent reports no sites or the wrong site, the token is scoped to a different site than the one you meant.
What are Webflow's rate limits?
Webflow limits the Data API per token: 60 requests per minute on Starter and Basic site plans, 120 per minute on CMS, eCommerce, and Business plans, and custom limits on Enterprise. Going over returns HTTP 429 with a Retry-After header (typically 60 seconds). Publishing a site is additionally capped at one successful publish per minute. These limits apply to the hosted connection exactly as they would to your own script, because the token is yours.
Is it safe to connect Webflow to an AI agent?
The token is a credential for the site it was created on, so treat it like one: it can be revoked from the same Site settings page at any time, and it expires after 365 consecutive days of inactivity. Webflow's own guidance is to give tokens minimal scopes and to revoke tokens you are not using. Because scopes are fixed at creation, an agent that needs to edit CMS content needs a token with the CMS scopes from the start; a read-only token will 403 on write tools, which is the safety mechanism working as intended.
Hermes paired but still can't use Webflow
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 tools
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
Hermes SafetyCulture integration
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.