Curator.io

Connect AI agents to Curator.io, a social media feed aggregation platform. Agents pull posts from connected sources, set feed moderation mode and manage sources, and inject custom posts alongside the aggregated stream.

13 actions Basic auth available

Curator.io website ↗ Platform Documentation ↗ Capability data verified 2026-08-06

A campaign hashtag goes live, or a scheduled audit run starts against the feed estate

List Feeds returns every feed with its current moderation mode and widget configuration

Create Source adds the campaign hashtag or account to the feed that powers the landing page

List Feed Posts is polled with the Disabled filter to see what a reviewer has already hidden

The hidden-to-visible ratio is compared against what the brand considers acceptable for a public page

The web owner receives the source list, the moderation mode, and the current hidden count

A person decides whether the feed stays on Pre-moderation before the campaign traffic arrives

What This Integration Enables

Curator.io is not a publishing tool, and reading it as one leads to the wrong flow. Every other social connector in this catalog writes content the brand owns onto a platform someone else runs. Curator.io does the opposite: it pulls posts other people wrote onto a page the brand owns. That inversion is the whole design problem. A hashtag wall on a product launch page is user content on your property, under your logo, and the failure mode is not a missed post. It is a post you would never have written appearing above your own footer. So the surface this connector exposes is the feed's configuration, not its contents. Create Feed, Update Feed, and Delete Feed manage the aggregation widget. Create Source, Update Source, and Delete Source manage what the widget is allowed to pull from. Create Custom Post, Update Custom Post, and Delete Custom Post inject your own content into the aggregated stream, each carrying its own visibility status.

Be precise about the moderation boundary, because it is where flows get designed wrong. Update Feed sets the feed's moderation mode: Post-moderation shows aggregated posts immediately and lets a reviewer hide them afterwards, and Pre-moderation holds them until a reviewer approves. List Feed Posts reads the aggregated stream and filters by Active, Disabled, or All, so an agent can see what has been hidden. What the API does not expose is an action to approve or hide one individual aggregated post. That per-post call belongs to a person in the Curator.io dashboard, and no amount of flow design changes it. An agent can set the policy, add and remove the sources the policy applies to, and report what the policy is catching. Deciding which of somebody else's posts appears on your homepage stays with a human, because the platform kept it there. There are also no triggers here, since Curator.io publishes no event subscription, so change detection is a scheduled List Feed Posts poll rather than a push.

Without FlowRunner

Feed changes made by hand at launch Sources are added in the dashboard on the day of the campaign, and nobody records what changed

Moderation mode is set once and forgotten A feed built for a controlled launch is still running months later under whatever mode it started with

No visibility into what was hidden The reviewer knows what they took down; the marketing owner finds out when someone asks

With FlowRunner

Sources managed as part of the campaign flow Create Source and Delete Source run alongside the rest of the launch, in the same audited run

Moderation mode is an explicit decision Update Feed carries the mode, and changing it is a step somebody approved rather than a setting nobody owns

Hidden volume surfaces on its own List Feed Posts with the Disabled filter reports what moderation is actually catching

Use Case Scenarios

A campaign hashtag wall that opens closed

A product launch page carries a live hashtag wall. Two weeks before launch, a flow calls Create Feed with the moderation mode set to Pre-moderation, adds the campaign hashtag and the three brand accounts through Create Source, and posts the returned public key to the web team so the widget can be embedded on the Webflow page. Nothing appears on the wall until a reviewer approves it. On launch day a second flow calls Create Custom Post to pin the launch announcement at position one, so the brand's own message sits above the aggregated stream rather than competing with it. The wall is live, and it is live in the closed state by default rather than by somebody remembering to close it.

Retiring a campaign without leaving it running

Campaigns end; their feeds usually do not. A monthly audit flow calls List Feeds, matches each feed against the campaign register held in Airtable, and finds the feeds whose campaigns closed more than sixty days ago. For each one it calls List Sources to show exactly what that feed is still pulling, and List Feed Posts to show whether anything new has arrived recently. The findings go to the web owner as a single summary. Delete Feed removes the feed along with all of its sources and posts, so it never runs unattended: the flow proposes the list and a person confirms it. Stale hashtag walls are a slow, quiet brand risk, and the cure is a scheduled audit rather than an incident.

Custom posts that follow the commerce calendar

A retailer's homepage feed mixes customer photos with the brand's own promotional cards. When a promotion goes live in Shopify, an agent calls Create Custom Post with the promotional image, the link, position 1, and Status set to active, so the card enters the aggregated stream at the top. When the promotion ends, Update Custom Post sets the status to disabled rather than deleting the record, which keeps the card available for reuse next season. The aggregated customer content around it never changes. Only the brand's own inserted cards move, which is the part the brand actually controls.

Human-in-Loop Highlight

The gate here is not on a post. It is on a single field in Update Feed. Moderation mode has two settings with very different consequences: Pre-moderation holds every aggregated post until a reviewer approves it, and Post-moderation puts every incoming post from every source straight onto the live page and relies on someone noticing afterwards. When an agent is asked to relax a feed to Post-moderation, whether to reduce reviewer load or to speed up a live event, it does not just send the update. It gathers the evidence first: List Sources for what that feed pulls from, and List Feed Posts filtered to Disabled for how many posts a reviewer has already had to take down. Then it stops and messages the web owner: "Switching the homepage feed to Post-moderation. It pulls from 4 sources including an open hashtag, and reviewers have hidden 23 posts in the last 30 days. Under Post-moderation those posts would have gone live first, and this connector has no action to hide an individual post. Confirm?" That last sentence is the one that matters. The agent is telling the owner where its own reach ends, which is what a digital andon cord is for.

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

13 actions

Feeds

List Feeds Retrieves all feeds in the account. Each feed returns its id, API id, public key, name, moderation mode, widget type, and styling, which makes this the starting point for any audit of what is currently embedded and where.
Create Feed Creates a new feed, which is the aggregation widget itself. Takes a display name and optionally the moderation mode, and returns the generated API id and public key used to embed the widget on a page. Setting Pre-moderation at creation is how a feed starts closed rather than open.
Update Feed Updates an existing feed's name, moderation mode, and widget colour scheme. Only the fields you provide change. The moderation mode field is the one with real consequences, because it decides whether third-party posts reach the live page before or after a person sees them.
Delete Feed Permanently deletes a feed along with all of its sources and posts. There is no undo and no partial version of this, so it belongs behind a person in every flow that calls it.

Posts

List Feed Posts Retrieves the aggregated posts for a feed with pagination and network, source, and status filters. The status filter returns Active, Disabled, or All, which is how an agent measures what moderation is catching without being able to moderate itself.

Sources

List Sources Retrieves sources, optionally filtered to a single feed. Use it to answer the question every brand safety review asks, which is what exactly this widget is allowed to pull from.
Create Source Adds a source to a feed, such as a hashtag, an account, or a URL. This is the action that widens a feed's reach, so pairing it with the feed's current moderation mode is the difference between a controlled campaign and an open door.
Update Source Updates a source's display name. Used to keep source labeling readable for the people reviewing the feed rather than for the API.
Delete Source Permanently removes a source from its feed. Used when a campaign ends, or when a hashtag turns out to be attracting content the brand does not want to be near.

Custom Posts

List Custom Posts Retrieves the custom posts injected into feeds, optionally filtered to one feed. Used to reconcile which brand-owned cards are currently live in the stream.
Create Custom Post Creates a custom post injected into a feed at a defined position, with a visibility status. This is the brand's own content entering the aggregated stream, and unlike aggregated posts, its visibility is fully controllable from the flow.
Update Custom Post Updates an existing custom post, including its position and visibility status. Setting a card to disabled retires it without destroying it, which is usually what a seasonal promotion actually needs.
Delete Custom Post Permanently deletes a custom post. Used for cleanup once a card is genuinely finished rather than merely paused.

Frequently Asked Questions

What can FlowRunner do with Curator.io?

FlowRunner agents can run List Feeds, Create Feed, and Update Feed in Curator.io, plus 10 more actions.

Does connecting Curator.io to FlowRunner require OAuth?

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

Can Curator.io trigger a FlowRunner workflow automatically?

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

Start building with Curator.io

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

Start Building Free Talk to us