Connect Webflow to Hermes
Give Hermes governed access to Webflow’s 34 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Webflow to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Approve Webflow in Runlayer
Add Webflow from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Hermes to Runlayer
Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Webflow’s 34 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Webflow
Sign in the way Webflow requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Webflow from Hermes
Webflow’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
34 Webflow tools in Hermes
Runlayer policy decides which of these Hermes users can call. 4 read data only.
Ask Webflow AI
Ask Webflow AI about anything related to Webflow API.
Designer asset tool
Designer Tool - Upload an image from a publicly accessible URL as a Webflow asset.
Data agent instructions tool
Data tool - Manage and generate agent instructions (rules and skills) for a site.
Data analyze tool
Read Webflow Analyze report data for a site, including traffic timeseries, ranked pages, ranked dimensions, ranked engagement events, and aggregate or bucketed time on page.
Data apps tool
Inspect and manage Webflow Cloud apps, GitHub sources, environments, variable metadata, deployments, domains, and logs, including destructive lifecycle changes and deployment triggers.
Data assets tool
Data tool - Manage Webflow site assets and asset folders via the Data API.
Data campaigns tool
Campaign Hub sites, campaigns, page-variation personalization, and campaign analytics.
Data cms tool
Data tool - CMS tool to manage collections, collection fields (static/option/reference), collection field groups, and collection items (list, create, update, publish, unpublish, delete)
Control
What Runlayer can see and stop in Hermes
Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.
Gateway policy (available)
Every Webflow call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Hermes as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Hermes runs it.
Block output after it runs (available)
Runlayer can block a tool’s output in Hermes and show a message in its place.
Redact output in place (not available)
Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Hermes
- Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.
Frequently asked questions
Connect more
