Skip to main content
Book a demo

Connect Workato to Glean

Give Glean governed access to Workato’s 108 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Glean setup guide

Set up

Add Workato to Glean in four steps

Admins approve the server once. Everyone in Glean then gets it through the same governed connection.

  1. 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. 2

    Connect Glean to Runlayer

    Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Workato’s 108 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Glean setup guide
  3. 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. 4

    Use Workato from Glean

    Workato’s approved tools appear in Glean. Every call is checked against policy and recorded.

Tools

108 Workato tools in Glean

Runlayer policy decides which of these Glean 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.

See all 108 Workato tools

Control

What Runlayer can see and stop in Glean

Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.

  • Gateway policy (available)

    Every Workato call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.

  • OTLP telemetry (available)

    Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.

In Glean

  • Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.

Frequently asked questions

Connect more

Find another combination