Connect Nimble to Zed
Give Zed governed access to Nimble’s 27 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Nimble to Zed in four steps
Admins approve the server once. Everyone in Zed then gets it through the same governed connection.
- 1
Approve Nimble in Runlayer
Add Nimble from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Zed to Runlayer
Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches Nimble’s 27 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Zed setup guide - 3
Sign in to Nimble
Sign in the way Nimble requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Nimble from Zed
Nimble’s approved tools appear in Zed. Every call is checked against policy and recorded.
Tools
27 Nimble tools in Zed
Runlayer policy decides which of these Zed users can call. 16 read data only and 5 can change or delete data.
Nimble crawl run
Nimble Crawl: one-time bulk fetch of a known doc tree or URL list.
Nimble crawl status
Check the status and progress of a running or completed crawl job.
Nimble crawl list
List crawl jobs, optionally filtered by status.
Nimble crawl terminate
Cancel a running or queued crawl job.
List extraction templates
Browse Extraction Templates — reusable, site-specific structured scrapers.
Get extraction template
Get an Extraction Template's input/output schema before running it.
Run extraction template
Run an Extraction Template against 1–few known items (URL or site ID).
Generate extraction template
Generate a new Extraction Template — only when the user explicitly asks to.
Control
What Runlayer can see and stop in Zed
Some controls apply to every client at the gateway. Others depend on what Zed exposes to Runlayer.
Gateway policy (available)
Every Nimble call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.
Frequently asked questions
Connect more