Connect Webflow to ECA
Give ECA governed access to Webflow’s 34 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Webflow to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Webflow in Runlayer
Add Webflow from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Webflow’s 34 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to Webflow
Sign in the way Webflow requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Webflow from ECA
Webflow’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
34 Webflow tools in ECA
Runlayer policy decides which of these ECA users can call. 4 read data only.
Ask Webflow AI
Ask Webflow AI about anything related to Webflow API.
Designer asset tool
Designer Tool - Upload an image from a publicly accessible URL as a Webflow asset.
Data agent instructions tool
Data tool - Manage and generate agent instructions (rules and skills) for a site.
Data analyze tool
Read Webflow Analyze report data for a site, including traffic timeseries, ranked pages, ranked dimensions, ranked engagement events, and aggregate or bucketed time on page.
Data apps tool
Inspect and manage Webflow Cloud apps, GitHub sources, environments, variable metadata, deployments, domains, and logs, including destructive lifecycle changes and deployment triggers.
Data assets tool
Data tool - Manage Webflow site assets and asset folders via the Data API.
Data campaigns tool
Campaign Hub sites, campaigns, page-variation personalization, and campaign analytics.
Data cms tool
Data tool - CMS tool to manage collections, collection fields (static/option/reference), collection field groups, and collection items (list, create, update, publish, unpublish, delete)
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Webflow call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more
