Skip to main content
Book a demo

Connect Webflow to Claude

Give Claude governed access to Webflow’s 34 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Webflow to Claude in four steps

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

  1. 1

    Approve Webflow in Runlayer

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

  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Webflow’s 34 tools show up in Claude’s own tool list.

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

    Use Webflow from Claude

    Webflow’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

34 Webflow tools in Claude

Runlayer policy decides which of these Claude 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)

See all 34 Webflow tools

Control

What Runlayer can see and stop in Claude

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination