Connect Workato to Hermes
Give Hermes governed access to Workato’s 108 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Workato to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Add Workato to Runlayer
Workato isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Hermes to Runlayer
Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Workato’s 108 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Workato
Sign in the way Workato requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Workato from Hermes
Workato’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
108 Workato tools in Hermes
Runlayer policy decides which of these Hermes users can call.
Get asset URL
Generate Workato UI URLs for one or more assets (recipe, genie, knowledge_base, skill, blueprint, job, folder, connection, mcp_server, project, data_table, api_endpoint, and ~30 more types).
Blueprint apply
Edit the blueprint working copy held by this chat session: 1 to 100 ops, each {op: 'set', path, value} or {op: 'delete', path}, applied atomically in the order given.
Blueprint identify
Report which blueprint this chat session's working copy holds, by handle, without reading Workato or changing anything.
Blueprint init
Start a new blueprint in this chat session: creates an empty local working copy and nothing on Workato.
Blueprint link asset
Bind a built asset (recipe, skill, genie, or MCP server) to a blueprint's asset map placeholder.
Blueprint pull
Load an existing blueprint from Workato into this chat session's working copy, replacing whatever the session held.
Blueprint push
Save this chat session's blueprint working copy to Workato - the only blueprint tool that writes to the platform.
Read blueprint
Read the blueprint working copy held by this chat session.
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 Workato 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
