Webflow's Data API lets an agent create CMS items, read form submissions and work with Ecommerce orders. We build the agent so everything it writes to the CMS lands as a draft, and a person on your team decides what gets published.
01Use
Each one does a single job through the Data API. Content arrives as drafts, and nothing goes live on your site without a person.
Drafts CMS items from your briefs, fills reference fields, and checks new items against the style rules you give it.
Reads each form submission, scores it against your criteria, and routes it with a drafted reply to the right person.
Reads new Ecommerce orders, flags ones that need attention, and prepares fulfillment updates.
02Wire
Five surfaces, all on the Webflow Data API. The agent never edits your Designer layout, only the content and data behind it.
Read access is broad enough to answer the question, write access is narrow, and every write has a gate until you decide otherwise.
| Agent | Reads | Writes | Human gate |
|---|---|---|---|
| Content operations | Collections, style rules | CMS items as drafts | Publishing |
| Lead triage | Form submissions | Routing, drafted reply | Every outbound reply |
| Order operations | orders, inventory |
Order fulfillment | Fulfillments and refunds |
03Gate
Webflow already separates draft content from published content. We keep the agent on the draft side, so review happens in the CMS your editors know.
In the Webflow CMS itself. Drafted items appear in their collection, marked as drafts, next to everything else your editors manage.
The drafted item in full, plus a link to the run trace showing the brief, the sources and the checks it passed.
Publishing any CMS item, every outbound reply to a lead, and every fulfillment or refund.
A deleted or rewritten draft is recorded with its trace and becomes an eval case, so the agent is tested against it on every change.
04Asked
No. It writes CMS items as drafts. Publishing stays with a person unless you tell us, in writing, to change that for a specific collection.
No. It works through the Data API, which covers CMS content, forms and Ecommerce data. Your layouts and styles are untouched.
Yes. They are separate tools with separate permissions, so a content agent cannot touch orders and an order agent cannot touch content.
Tell us the content, lead or order task that eats the most time. We will tell you what the agent would draft, what it would read, and where a person signs off.
