Connect Skyvern to Glean
Give Glean governed access to Skyvern’s 77 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Skyvern to Glean in four steps
Admins approve the server once. Everyone in Glean then gets it through the same governed connection.
- 1
Approve Skyvern in Runlayer
Add Skyvern from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Glean to Runlayer
Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Skyvern’s 77 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Glean setup guide - 3
Sign in to Skyvern
Sign in the way Skyvern requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Skyvern from Glean
Skyvern’s approved tools appear in Glean. Every call is checked against policy and recorded.
Tools
77 Skyvern tools in Glean
Runlayer policy decides which of these Glean users can call. 34 read data only and 11 can change or delete data.
Create browser session
Create a new browser session to start interacting with websites.
Close browser session
Close a browser session when you're done.
List browser sessions
List all active browser sessions.
Get browser session
Get details about a specific browser session -- status, timeout, availability.
Connect to browser session
Connect to an existing browser -- a cloud session by ID or any browser via CDP URL.
Perform browser action (ai)
Perform actions on a page by describing what to do in plain English.
Extract data from page (ai)
Extract structured data from the current page using AI with screenshots and a dedicated extraction LLM.
Validate page condition (ai)
Check if a condition is true on the current page — cheapest AI option for yes/no questions.
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 Skyvern 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