GatherContent

Connect AI agents to GatherContent, now Bynder Content Workflow, the content operations platform. Agents create and update content items, apply templates, organize folders, and manage webhooks so structured content moves from plan to CMS without manual handoffs.

Verified 22 actions Basic auth available

GatherContent website ↗ Platform Documentation ↗ Capability data verified 2026-08-10

A page request is approved in the project intake queue

Agent calls Create Item from the matching template and places it in the right folder

Agent gathers source material and writes it in with Update Item Content, keyed by field UUID

Agent calls List Project Statuses and moves the item into the review status the project actually uses

Agent tells the assigned editor the item is populated and waiting

Editor reviews the structured fields and moves the item to Approved, which fires the webhook the agent subscribed to and resumes the flow

What This Integration Enables

GatherContent, now Bynder Content Workflow, is where content exists before a CMS is willing to accept it. That distinction is the whole reason to connect it. A CMS wants finished, structured entries. A content project produces half written fields, missing images, and three people disagreeing about the subhead, and it needs somewhere to do that in the open. GatherContent is that place, and its unit of work is the item: a record built from a template, holding field content keyed by field UUID, moving through the project's own workflow statuses.

FlowRunner agents work on both sides of that. They create items from templates, write field content, rename and move items between folders, duplicate an item to spin up a variant, and subscribe to project webhooks so a status change becomes the trigger for what happens next. The pattern that makes this worth automating is not bulk creation, it is the handoff: an agent assembles and structures, a person judges, and a status change is the human-in-the-loop signal that releases the work downstream. Agents move content into shape. Editors decide when it is ready.

Without FlowRunner

Content lives in attachments Copy arrives as documents named v3_final and gets rekeyed into the CMS by hand

Structure is discovered late Nobody finds out a field is missing until someone tries to load the page

Status is a conversation Whether a page is approved depends on who you ask and which thread you read

With FlowRunner

Content is structured from the start Every item is built from a template, so the fields exist before the words do

The CMS receives clean fields An approved item maps onto the destination entry without a rewrite step

Status is a signal A status change fires a webhook that an agent can act on, not a message someone has to notice

Use Case Scenarios

Intake to a structured, populated item

A request for a new landing page is approved upstream. The agent calls List Templates to find the matching page template, calls Create Item against the project with that template id, and drops the item into the campaign folder. It then writes what it already knows into the item with Update Item Content: the product name, the target audience, the offer terms pulled from the source system, each mapped onto its field UUID. The writer opens an item that is already framed and half filled instead of a blank template, and List Project Statuses tells the agent which status the project uses for review so it can move the item there rather than assuming a name.

Approved content into the live CMS

An editor moves an item to Approved. The webhook the agent subscribed to fires, the agent calls Get Item to pull the field content, and it maps those fields onto an entry in Contentful or a post in WordPress. Because the item was built from a template, the field structure is known in advance and the mapping is stable across every item of that type. Nothing is rekeyed and nothing is pasted. The approval is the publish instruction.

Restructuring a project onto a new template

A team redesigns their page type and wants forty existing items rebuilt on the new template. The agent calls List Items to collect them, Get Template to read the new structure, and then works through them one at a time rather than in a single sweep, because applying a template is destructive to the content already in the item. That constraint is what turns this from a bulk operation into a supervised one, and the section below is what the agent does about it.

Human-in-Loop Highlight

Apply Template To Item is the operation that earns a gate on this connector, and it is easy to underestimate. It replaces the item's current fields with the template's fields and does not copy the existing content across. Whatever was written in those fields survives only in the item's revision history, which means recovery is a person opening each item and reading backward, not an undo. An agent running a template migration across a project could quietly empty forty items in a few seconds and technically succeed at every call.

So it does not run the sweep. The agent calls Get Item on the first item in the batch, captures its current field content, and posts to the content channel: "Applying template [name] to [item] will clear its current fields. Here is what that item holds today, and here are the 39 other items queued behind it. Apply to this one, apply to all, or stop?" The content lead answers once, with the actual content in front of them, and the agent proceeds under that answer. This is the digital andon cord applied to content operations: the agent is entirely capable of finishing the migration, and it stops the line at the point where finishing it wrong is unrecoverable.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

22 actions

Account

Get Current User Retrieves the profile of the user whose API key is configured, including id, email, name, and timezone. Used to verify the connection and identify the acting user in an audit trail.
List Accounts Lists the accounts the configured user can access. Used as the entry point when an agency operates across more than one client account.

Projects

List Projects Lists the projects belonging to an account with their id, name, and status. Used to resolve a project by name before any item, template, or folder work.
Get Project Retrieves a single project by id, including its name, owning account, active state, and text direction. Used to confirm an agent is writing into a live project.
List Project Statuses Lists the workflow statuses configured for a project, such as Draft, In Review, or Approved. Used so an agent moves items into the status a project actually defines rather than a status name it assumes.

Items

List Items Lists content items in a project with filtering by template, status, folder, and name, plus sorting and pagination. Used to find work in a given state, such as everything sitting in review past its due date.
Get Item Retrieves a single item with its field content keyed by field UUID, optionally including the item structure. Used to read approved content before pushing it to a CMS, and to capture current content before a destructive operation.
Create Item Creates a content item in a project from either a template id or a custom structure, with optional name, status, folder, position, and initial field content. Used to turn an approved request into a structured, partly populated record.
Update Item Content Updates field content on an existing item, changing only the fields included in the request. Repeatable fields take an ordered array, and entries left out are removed. Used to write source data into an item without disturbing what a writer has already done elsewhere in it.
Rename Item Renames an item without touching its content or structure. Used to apply a naming convention across a project.
Move Item Moves an item to a new position and optionally into a different folder. Used to file work as it changes state, such as moving approved items into a ready folder.
Apply Template To Item Applies an existing template to an item. The template fields replace the item's current fields without copying content across, so prior content remains only in revision history. Used for deliberate, supervised restructuring, never as an unattended bulk operation.
Duplicate Item Duplicates an item including its status, template, content, and files. Comments, conversations, assignees, and due dates are not carried over. Used to spin up a localized or segment specific variant from an approved original.

Templates

List Templates Lists the reusable content templates defined in a project, with optional pagination and full structure. Used to resolve a template by name before creating items.
Get Template Retrieves a single template with its field structure grouped into field groups. Used to build the field mapping between GatherContent items and a destination CMS.

Folders

List Folders Lists all folders in a project as a flat list, where each folder's parent uuid describes the hierarchy. Optionally includes trashed folders. Used to resolve a destination folder before creating or moving items.
Create Folder Creates a folder inside an existing parent folder. Used to provision a per campaign or per release space when a project starts.
Rename Folder Renames an existing folder. Used to keep project structure aligned with an upstream naming scheme.

Files

List Files Lists files uploaded to a project, optionally including the items each file is attached to, file metadata, and uploader details. Used to check that every item has its assets before content moves to a CMS.

Webhooks

List Webhooks Lists the webhook subscriptions configured for a project with the event each one listens for and its destination URL. Used to audit which flows are watching a project.
Subscribe To Webhook Creates a webhook subscription in a project for a chosen event, sending a payload to the destination URL when the event fires. Used to make an editor's status change the trigger for downstream publishing.
Unsubscribe From Webhook Deletes a webhook subscription by id, stopping further deliveries. Used to retire a listener when a project closes or a flow is replaced.

Frequently Asked Questions

What can FlowRunner do with GatherContent?

FlowRunner agents can run Get Current User, List Accounts, and List Projects in GatherContent, plus 19 more actions.

Does connecting GatherContent to FlowRunner require OAuth?

No. GatherContent connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can GatherContent trigger a FlowRunner workflow automatically?

GatherContent doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with GatherContent

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us