# Stage the whole collection, then work it row by row.

A four-step agent that pulls every item from a Webflow CMS collection into grid rows keyed by cms_item_id, so re-runs update rows instead of duplicating them.

_Source: https://mentionova.com/agents/stage-cms-collection-in-a-grid_

It stages every collection item as grid rows keyed by cms_item_id, so a re-run updates instead of duplicating.

Category: Integrations & data.

- **4** chained steps
- **On demand** run mode
- **1** click to add

## 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

Integrations: Webflow CMS, Grids.

Steps in the template: Trigger → Connector → Stage rows in grid → Notify.

## 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.

## The time this gives back.

| Doing it by hand | Time |
| --- | --- |
| 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 grid | Time |
| --- | --- |
| Agent fetches and maps | auto |
| Agent upserts by ID | auto |
| You work the grid | ~15m |
| One agent run | ~15 min |

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.

## 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](https://mentionova.com/agents/create-content-brief-from-keyword)
- [Create article from brief](https://mentionova.com/agents/create-article-from-brief)
- [Add FAQ to an article](https://mentionova.com/agents/add-faq-to-an-article)
- [Add key takeaways to an article](https://mentionova.com/agents/add-key-takeaways-to-an-article)
- [Internal link suggestions from sitemap](https://mentionova.com/agents/internal-link-suggestions-from-sitemap)

---

_Mentionova, https://mentionova.com. Markdown rendering of the page above for AI readers._
