Content & Documents · Integration
Webflow
Add Webflow to your product for your customers, and give your AI agents governed access to it.
Webflow is a visual site builder with a CMS behind it, so a site is made of pages a designer laid out and collections whose items fill them. That split decides what an integration can do. Collection items are structured records your product creates, updates and deletes against a schema the customer defined in the designer, assets can be uploaded into the site's own library, and a publish call is what makes any of it visible on the live domain, which is the step people forget. Form submissions and item changes arrive as webhooks, so your product reacts instead of polling. What the API will not do is design: the layout belongs in Webflow, and everything here works with the content inside it. Credentials for each site stay with fastn, scoped to the customer who authorised them, and API revisions land here rather than in your sprint.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Webflow site so content your product produces reaches their live pages with no copy and paste.
Create and update collection items against the schema that customer defined, then publish so the change is actually visible.
Upload assets from your product into the site's own asset library rather than hotlinking them from somewhere else.
React to a form submission as a webhook, so a lead captured on the marketing site reaches your product immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent drafts a collection item and leaves it unpublished for a person to review before it goes live.
An agent reports which items changed since a date and which of them are still unpublished.
An agent publishes an approved change within scoped permissions, with the publish recorded.
Example prompt
Which blog collection items were updated this week, and are any of them still waiting to be published?
Set up Webflow in 4 steps
- 01Enable the Webflow connector in your fastn dashboard.
- 02Have each customer authorise their own Webflow site so calls run under their credentials.
- 03Map the collections, item fields and assets your product uses, subscribe to the webhooks you need, and decide who is allowed to publish.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Webflow integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Webflow integration without building it. Your customers connect their own Webflow account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Webflow update is not your on-call problem.
- One integration serves your product and your agents. The same governed Webflow connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
ContentfulWorks well with
Wix
SquarespaceOften used alongside
Tools the same teams tend to run next to Webflow, across other categories.
Shopify
Stripe
Jira
AsanaWebflow integration FAQ
How do I add a Webflow integration to my product?
Enable the Webflow connector in your fastn dashboard, then let each customer authenticate their own Webflow account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Webflow client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Webflow account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Webflow account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Webflow integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent drafts a collection item and leaves it unpublished for a person to review before it goes live.
Who maintains the Webflow integration?
fastn does. When Webflow changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Webflow integration run under?
Each customer's own Webflow grant. Where Webflow holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Webflow automatically?
Where Webflow supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Webflow integration?
A common starting point: let each customer connect their own Webflow site so content your product produces reaches their live pages with no copy and paste. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Webflow integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Webflow does not change your per-connector cost. You can start free with 3 connected accounts.
Add Webflow to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.