The site's content, updated from the thread.
Ask what the contact form collected, draft the post into the CMS, then publish it. Cedric proposes each live-site change and waits for your yes.
$50 in free credits when you sign up. No card needed.
- Webflow holds the site's content, its forms and its store, and updating any of them usually means opening the editor.
- Ask in plain words: what came through the contact form this week, which posts are live, whether an order shipped.
- Cedric creates or updates CMS items, edits page titles and meta descriptions, and uploads assets, proposed first.
- Publishing is a separate step. Cedric drafts, shows you, and publishes to the domains you name on your yes.
- Design stays in the designer: the connection cannot change layouts or styling, and deleting content always waits for your yes.
What can a Webflow AI agent do?
Most of what a marketing team needs from Webflow after launch is content. A Webflow AI agent lists the sites in the account with their pages, domains and settings, then creates, updates and deletes CMS collection items: blog posts, case studies, team profiles, whatever the collections hold. Cedric can also read and edit page content and the SEO settings on each page, titles and meta descriptions included, and browse or upload assets like images and files into folders.
The site also talks back. Cedric retrieves and reviews the form submissions collected from the site's pages, so the thread can ask what came in since Monday and get the entries summarized rather than forwarded one by one. Where the site sells, Cedric manages store products, variants and inventory levels, and views or updates customer orders. It can set up notifications too, so an external system hears when content is published or a form is submitted.
Publishing is deliberate. Cedric publishes a site, or specific items, so the change goes live on the domains you choose, and it proposes that step separately from the draft. What the connection cannot do is design: it does not redesign layouts or edit visual styling the way the design editor does. For the content side of the marketing work, that split is the right one.
Publishing day
The post is in the CMS, and the form has been read.
Hannah Kessler9:14 AM
@Cedric add the "Q3 product update" post to the Blog collection from the doc I pasted above, author me, and tell me what came in through the contact form since Monday.
CedricAPP9:15 AM
Drafted as a CMS item in Blog: title "Q3 product update", slug q3-product-update, author Hannah Kessler, 640 words, meta description taken from the first paragraph. Contact form since Monday: 9 submissions, 6 sales inquiries, 2 support questions, 1 press request from a trade publication. The post is saved as a draft and is not live. Proposed: publish the item to the production domain now.
Read
Form submissions, CMS items, pages and their SEO settings, store products and orders, across every site in the account.
Drafted
CMS items created or updated, page titles and meta descriptions edited, assets uploaded: proposed first, saved on your yes.
Published
A site or specific items pushed live to the domains you name, always as its own separate approval.
Connect Webflow in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect Webflow from the dashboard
Open the Integrations page and sign in with Webflow on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "what came in through the contact form this week?". You describe the outcome; Cedric picks the Webflow actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold Webflow into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
A form submission on the site is a lead. In one ask, Cedric can read the new entries in Webflow and propose the matching contacts in HubSpot or Salesforce, which is CRM automation that starts at the website.
Publish the post, then ask a week later how it did: Google Analytics has the traffic and Webflow has the item, so the answer names the page, the visits and the form entries it produced.
Where the limits are
Webflow is a catalog connection, not a built-in playbook. Cedric works from what the Webflow connection can read and do; ask in plain words and it says what it can reach there, and what it cannot.
Publishing and deleting are live-site changes. A published item is visible to every visitor and a deleted item is gone from the CMS, so both are proposed separately and wait for your yes. Webflow's rate limits apply.
Design stays in the designer. The connection cannot redesign layouts or edit visual styling. Cedric works on content, SEO settings, assets, forms and the store, not on how the page looks.
Cedric sees what the Webflow connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes. Webflow is one of the 3,200+ apps in Cedric's catalog: connect it once from the dashboard, on Webflow's own sign-in screen, and ask in plain words. There is no built-in playbook for it, so Cedric works from what the connection can read and do, and tells you when something is out of reach.
No. Layouts, styles and components are edited in Webflow's designer, and the API does not reach them. Cedric changes what the pages say: CMS items, page titles, meta descriptions and assets.
No. Creating or updating a CMS item leaves it as a draft. Publishing the site or the specific item is a separate action that Cedric proposes and runs only on your yes, to the domains you name.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Connect Webflow in a minute.
Ask what the contact form collected this week, then draft the next post into the CMS.
100K credits ($50) on sign up. No card needed.