Stage the whole collection, then work it row by row.
It stages every collection item as grid rows keyed by cms_item_id, so a re-run updates instead of duplicating.
4 steps · runs on demand · added to your workspace as a draft
What it does
Pre-built, then yours to customize.
Add it to your workspace in one click. Sensible defaults and example inputs are already filled in.
Reads from · writes to
- Webflow CMS
- Grids
The template, step for step
- Trigger
- Connector
- Stage rows in grid
- Notify
Added to your workspace as a Draft, with example inputs filled in. Every step is yours to change.
- 01
One row per item, keyed by cms_item_id
- 02
Re-runs update existing rows — no duplicate sets
- 03
Carries title, slug and draft status
- 04
Per-item refresh then runs as grid columns
In, and out
You give it a Webflow collection. This is what comes back.
- Shape
- 4 steps
- On demand
- run mode
- 1
- click to add
| cms_item_id | Title | Slug | Status |
|---|---|---|---|
| 64f1…a2 | AI visibility guide | /ai-visibility-guide | draft |
| 64f1…b7 | AEO checklist | /aeo-checklist | published |
| 64f2…09 | GEO vs SEO | /geo-vs-seo | published |
| 64f2…1c | Schema for answers | /schema-answers | draft |
Illustrative output.
Run it twice
Same rows. Not twice as many.
Every row is keyed by the CMS item's own id, so a second run updates in place.
01 · Run one: every item in the collection becomes a grid row.
02 · Each row carries the CMS item's own id. That's the key.
03 · A week later you run it again. One title changed in the CMS.
04 · Every key is matched, and updated where it already sits.
05 · Five rows before, five rows after. Nothing doubles.
Run 1 · stage the collectionRun 2 · same collection, a week later
5rows · still 5
- 64f1…a2AI visibility guide/ai-visibility-guidedraft
- 64f1…b7AEO checklist/aeo-checklistpublished
- 64f2…09GEO vs SEOGEO vs SEO in 2026/geo-vs-seopublished
- 64f2…1cSchema for answers/schema-answersdraft
- 64f3…5eReddit and AI search/reddit-ai-searchpublished
Matched on cms_item_id: five updated in place, one title rewritten, none added. Then each row is worked as grid columns.
The steps
What happens on every run.
- fetch_webflow_collection
- map_item_fields
- upsert_by_cms_item_id
- write_grid_rows
4 steps · Runs on demand0 / 4
Run history keeps each step's output and runtime, and the input of every step that completed.
Before & after
The time this gives back.
The templates that publish put a Human review step before the CMS step, and nothing ever posts to Reddit for you. Review is a step, not a lock: a workflow you build or edit can publish or message a channel without one, so add it wherever you want the sign-off.
Doing it by hand~2 hrs
Stage CMS collection in a grid~15 min
Bars to scale: the time a person spends, each way.
Doing it by handyour team
- Exporting the collection~30m
- Cleaning it into a sheet~45m
- Re-doing it after changes~45m
Per collection, by hand~2 hrs
Stage CMS collection in a gridLive
- Agent fetches and mapsauto
- Agent upserts by IDauto
- You work the grid~15m
One agent run~15 min
FAQ
Questions, answered.
The Filter step upserts on cms_item_id, so the second run updates the rows already there. You do not end up with two copies of the collection.
Because per-item work then runs as grid columns. Staging once means a bulk refresh across a hundred items becomes one column of work rather than a hundred separate runs.
Not this agent — it stages, so writes go through the CMS push step in the publish agent, which uses the staged cms_item_id.
Free to start
Add this agentto your workspace.
Start free. Customize the steps, run it on demand or on a schedule, and approve anything that ships.