FeedHive

Connect AI agents to FeedHive, an AI-assisted social media scheduling platform. Agents draft and schedule posts across connected socials, organize them with labels, and read the analytics behind each one.

23 actions API key available

FeedHive website ↗ Platform Documentation ↗ Capability data verified 2026-08-06

A batch of approved copy lands in the content system at the end of the week

Create Post writes each item as a draft across the connected accounts it targets

Create Label or List Labels resolves the campaign grouping the plan slots filter on

List Plan Slots returns the weekly windows, their recurrence, and their label restrictions

The drafts in scope are matched against the slots that would actually accept them

The content owner receives the resolved schedule, showing which post lands in which window

A person approves the resolved calendar before Assign Posts To Next Slots commits it

What This Integration Enables

The object that makes FeedHive different is the plan slot. Most schedulers store a calendar, which is a list of times somebody chose. FeedHive stores a rule: a plan slot is a recurring weekly window defined by a week day, a start and end time, a recurrence, and optionally a restriction to posts carrying specific labels. Assign Posts To Next Slots then takes a batch of drafts and places them into the next eligible occurrences of those slots automatically. That inversion is the point. The cadence stops being an accumulation of individual decisions and becomes a thing a team agreed to once and can inspect afterwards with List Plan Slots. Around that sit the parts you would expect: Create Post, Update Post, and List Posts with filters for status, labels, and social accounts; List Social Accounts and Get Social Account for the connected surfaces; and Labels as the grouping layer the slot restrictions actually filter on.

Three practical facts change how a flow gets built here. First, media upload is a three-step sequence rather than one call. Create Media Upload starts a session and returns a pre-signed S3 URL with an expiry, the file bytes are PUT directly to that URL by a step in the flow, and Complete Media Upload finalizes the permanent media record. Skip the last call and the bytes exist with no media item attached to anything. Second, Delete Post is a soft delete, which is worth saying plainly because it is unusual: in most of this category the delete is the irreversible operation, and here it is not, which moves the real risk elsewhere. Third, both analytics reads return a collection timestamp and a staleness indicator alongside the numbers. Get Post Analytics gives per-publication impressions, likes, comments, and clicks for each account a post reached, and Get Social Account Analytics gives follower count, impressions, and page views. FeedHive publishes no documented webhook subscriptions, so this connector ships no triggers at all. A flow starts from a schedule or from an approval upstream, and List Posts with a status filter is how it learns what has since gone out.

Without FlowRunner

Times chosen post by post Every draft gets a timestamp picked by whoever is scheduling that afternoon

Cadence drifts quietly The posting rhythm the team agreed on erodes over a few busy weeks and nobody notices

Performance checked in each network Reviewing how a post did means opening every platform it was published to, one at a time

With FlowRunner

Times come from a defined rule Plan slots hold the cadence, and Assign Posts To Next Slots places drafts into it

Cadence is inspectable List Plan Slots reports the agreed rhythm as data, so drift shows up as a difference rather than a feeling

One read per post, across networks Get Post Analytics returns per-publication metrics for every account the post reached

Use Case Scenarios

A week of drafts placed by the cadence rather than by hand

Approved copy accumulates in Notion through the week. On Friday a flow reads the approved rows and calls Create Post for each one, targeting the relevant connected accounts and attaching the campaign label so the plan slots can filter on it. It calls List Plan Slots to read the current windows and their label restrictions, and works out which drafts each slot would accept. The resolved schedule goes to the content owner as a single view: this post into Tuesday morning, that one into Thursday afternoon, two with no eligible slot. Assign Posts To Next Slots runs only after the owner approves. The scheduling labour is gone and the cadence is still something a person owns.

Media that arrives complete or not at all

A campaign asset is produced and stored. The flow calls Create Media Upload with the filename and MIME type, receives the pre-signed S3 URL and its expiry, PUTs the bytes to that URL in the next step, and calls Complete Media Upload with the returned upload id. Only then does it call Create Post referencing the finished media item. If the PUT fails or the URL expires first, the flow stops before Create Post rather than creating a post that references media which does not exist. Getting this sequence right is the difference between a scheduled post with an image and a scheduled post with a gap where the image should be.

A weekly report that says how fresh its own numbers are

Every Monday a flow calls List Posts filtered to published in the previous week, then calls Get Post Analytics for each one to collect per-account impressions, likes, comments, and clicks. It also calls Get Social Account Analytics for each connected account to capture follower count and page views. The numbers land in Google Sheets alongside the collection timestamp and staleness indicator FeedHive returns with them. The report carries its own freshness, so a Monday decision made on Thursday's numbers is a visible fact rather than a hidden one. That distinction matters more than the numbers themselves, because a stale metric that looks current is how a campaign gets extended for the wrong reason.

Human-in-Loop Highlight

The gate on this connector is not a publish and not a delete, because Delete Post here is a soft delete and recoverable. It is Assign Posts To Next Slots, which is the one call that hands scheduling authority away from the flow. The agent supplies a batch of draft ids and nothing else. FeedHive decides where they land, using slot definitions written by somebody else, filtered by label restrictions the agent did not set, across a recurrence pattern it cannot see the downstream effect of. A batch that looks like eight posts can resolve into eight posts inside two days, or two posts a week for a month, and the difference is invisible at the call site. So the agent resolves the outcome before committing to it. It calls List Plan Slots and List Posts, works out which slot occurrence each draft would fall into, and sends the content owner the resolved calendar rather than the batch: "Assigning 11 approved drafts to plan slots. As written they resolve to 7 posts next week, 5 of them on Tuesday and Wednesday, plus 4 with no eligible slot because the Product label is not on any slot restriction. Assign, or adjust the slots first?" Approving a batch is easy. Approving the calendar that batch turns into is the decision that was actually being made.

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

23 actions

Posts

Create Post Creates a draft or scheduled post across one or more connected accounts. Creating as a draft is what makes the planning actions useful later, since Assign Posts To Next Slots operates on drafts rather than on posts that already carry a time.
List Posts Lists posts with filters for status, labels, and social accounts, using cursor-based pagination. This is the polling action that substitutes for the triggers FeedHive does not offer, and the way a flow reconciles what it intended against what is actually scheduled.
Get Post Fetches a single post by id. Used to resolve an id into something a reviewer can read before a change or a schedule is proposed against it.
Update Post Updates an existing post as a partial update, so only the fields you supply change. Used for the revision pass after review, and for retargeting a post to a different set of accounts without rebuilding it.
Delete Post Soft-deletes a post. Unusually for this category, the delete here is recoverable rather than final, which is worth knowing when deciding where the approval gates in a flow actually belong.

Socials

List Social Accounts Lists the connected social accounts. Run it before a batch so a disconnected account surfaces as a check rather than as a post scheduled to a surface that can no longer publish.
Get Social Account Fetches a single connected social account by id. Used to confirm a specific target before scheduling against it.

Labels

List Labels Lists all labels. Labels are what plan slot restrictions filter on, so this is the action that explains why a draft did or did not qualify for a slot.
Create Label Creates a new label. Used at campaign kickoff so every post created afterwards carries the grouping the planning layer needs.
Update Label Updates a label's title. Used to keep grouping names aligned with how the team currently describes its campaigns.
Delete Label Deletes a label. Removing a label also removes the basis on which any label-restricted plan slot was selecting posts, so check slot restrictions before calling it.

Media

List Media Items Lists media items in the library. Used to find an existing asset before uploading a duplicate, and as the first half of any library audit.
Get Media Item Fetches a single media item by id, returning its filename, content type, and storage details. Used to confirm an asset is real before a post references it.
Create Media Upload Starts an upload session and returns a pre-signed S3 URL with an expiry. The file bytes are then PUT directly to that URL by the next step in the flow. This call alone does not create a usable media item.
Complete Media Upload Finalizes an upload session after the bytes have reached the pre-signed URL, creating the permanent media record that posts can attach. Omitting this call leaves uploaded bytes that no post can reference.
Delete Media Item Deletes a media item from the library by id. Check for posts still referencing the item first, since a scheduled post whose media has been removed fails at publish time rather than at delete time.

Planning

List Plan Slots Lists the recurring plan slots on the account. Each slot defines a weekly time window into which draft posts can be scheduled automatically, so this action is how a team reads back the cadence it agreed to.
Create Plan Slot Creates a recurring plan slot from a week day, a start and end time, and a recurrence, optionally restricted to posts carrying specific labels. This is where the posting rhythm is defined rather than repeatedly re-decided.
Update Plan Slot Updates an existing plan slot as a partial update, where omitted fields keep their current values, including the timezone. Changing a slot changes where every future assignment lands, so it deserves the same care as changing a schedule directly.
Delete Plan Slot Deletes a plan slot definition. Posts already scheduled into occurrences of the slot are not affected, so this removes future placement rather than existing commitments.
Assign Posts To Next Slots Batch-assigns the given draft posts to the next eligible plan slot occurrences, scheduling them automatically according to the slot definitions. The single call in this connector where the flow supplies the content and the platform decides the timing.

Analytics

Get Post Analytics Retrieves analytics for a published post, returning per-publication metrics such as impressions, likes, comments, and clicks for each social account the post reached, along with collection timestamps and a staleness indicator. One read covers every network a post went to.
Get Social Account Analytics Retrieves the latest account-level analytics for a connected social account, including follower count, impressions, and page views, with the collection timestamp and staleness status. Use the staleness flag rather than assuming the numbers are current.

Frequently Asked Questions

What can FlowRunner do with FeedHive?

FlowRunner agents can run Create Post, List Posts, and Get Post in FeedHive, plus 20 more actions.

Does connecting FeedHive to FlowRunner require OAuth?

No. FeedHive connects to FlowRunner with an API key, no OAuth flow required.

Can FeedHive trigger a FlowRunner workflow automatically?

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

Start building with FeedHive

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

Start Building Free Talk to us