Agent · Integrations & data

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.

Add to workspace

4 stepsRuns on demandHTTP request · AI call · Filter / Branch · Workspace data

4chained stepsOn demandrun mode4step types1click to add

Trusted by 70+ brands & agencies

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.

✓One row per item, keyed by cms_item_id
✓Re-runs update existing rows — no duplicate sets
✓Carries title, slug and draft status
✓Per-item refresh then runs as grid columns

Webflow CMSGrids

Stage CMS collection in a grid

✓fetch_webflow_collection1.7s

✓map_item_fields1.0s

✓upsert_by_cms_item_id0.4s

✓write_grid_rows0.6s

4 steps · Runs on demand

Every run logs each step’s input, output and runtime.

The steps

What happens on every run.

Fetch the collection

Every item from the Webflow CMS collection, not a page of them.

Map the item fields

cms_item_id, title, slug and draft status onto grid columns.

Upsert by cms_item_id

A Filter step matches on the ID so re-runs update rather than duplicate.

Write the grid rows

One row per item, ready for per-item work.

Before & after

The time this gives back.

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

Steps that touch the outside world — a CMS, a channel, a live page — gate on human approval. You keep final approval.

FAQ

Questions, answered.

What happens if I run it twice?

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.

Why stage into a grid at all?

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.

Does it write back to Webflow?

Not this agent — it stages, so writes go through the CMS push step in the publish agent, which uses the staged cms_item_id.

Other agents in Integrations & data

Create content brief from keyword →Create article from brief →Add FAQ to an article →Add key takeaways to an article →Internal link suggestions from sitemap →

See the whole agent library →

Trusted by 70+ brands & agencies

Add this agent to your workspace.

Start free. Customize the steps, run it on demand or on a schedule, and approve anything that ships.

Add to workspace

First Growth Signal in ~2 minutes