Skip to main content

Connect Clay to Glean

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

Set up

Add Clay to Glean in four steps

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

  1. 1

    Approve Clay in Runlayer

    Add Clay from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Glean to Runlayer

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

    Glean setup guide
  3. 3

    Sign in to Clay

    Sign in the way Clay requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Clay from Glean

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

Tools

21 Clay tools in Glean

Runlayer policy decides which of these Glean users can call. 12 read data only and 3 can change or delete data.

  • Add company data points

    Add data points to companies in an existing search.

  • Add contact data points

    Add data points to contacts in an existing search.

  • Ask question about accounts

    Ask a natural language question about one or more accounts available in Clay Audiences.

  • Find and enrich company

    Find and enrich a single company by domain or LinkedIn URL.

  • Find and enrich contacts at company

    Search for contacts at a company by role, title, name, or department.

  • Find and enrich list of contacts

    Find and enrich specific named contacts at their companies.

  • Get credits available

    Check if credits are available for the workspace.

  • Get current workspace

    Report which Clay workspace this connection is pinned to.

See all 21 Clay 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 Clay 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