PostFast
Social MediaConnect AI agents to PostFast, a social media scheduling platform. Agents upload media, schedule posts across connected accounts, and work the social inbox, replying publicly or privately and moderating items on the source platform.
What This Integration Enables
Scheduling is the smaller half of PostFast. The larger half faces the audience. Alongside the expected publishing surface, this connector exposes the Social Inbox: comment threads and messages from the platforms that expose them, currently including TikTok, Instagram, Facebook, and Threads, with reply capability flags per conversation so a flow knows what it is allowed to do before it tries. That two-way surface is what makes PostFast a different proposition from a pure scheduler, and it is where most of the operational value and all of the real risk live.
The inbox is fully interactive, not read-only. List Conversations returns threads filterable by platform, account, triage status, unread state, and assignee. Get Conversation and List Conversation Items open a specific thread in order. Get Unread Count returns a single number for a badge or a wake-up condition. From there the agent can act: Reply To Item posts a public reply within the conversation's maxReplyLength, Send Private Reply sends a direct reply to the author where the platform supports it, limited to 1,000 bytes, and both accept an idempotency key so a retry after a network timeout cannot double send. Moderate Item hides, unhides, or deletes an item on the source platform and returns the resulting visibility state as VISIBLE, HIDDEN, or DELETED. Mark Conversation Read clears the unread count, Set Conversation Status moves a thread between Open, Snoozed, and Closed, and Assign Conversation hands it to a workspace user or clears the assignment.
The publishing side is built for scale without being careless about it. Create Posts takes 1 to 15 posts in a single request, each targeting one connected account with its own text, media items, and an optional automatic first comment, and each set to Draft to save without a schedule or Scheduled with a future time to publish automatically. Media goes in one of two ways: Get Upload URLs returns pre-signed S3 URLs to PUT files against, up to 8 for images and 1 for a video or document, or Upload Media From URL does the whole download-and-stream in one call from a public URL. Either way you reference the returned key in a post's mediaItems. Around that sit the target resolvers that stop a post from failing on a missing id: Search Places for Facebook and Instagram geotagging, Get Pinterest Boards, Get YouTube Playlists, and Get Google Business Locations. List Social Accounts reports every connected account with its platform, connection status, whether it supports the Social Inbox, and its latest follower count, and Get Follower History returns a daily time series with the net change across the range. Create Connect Link generates a link, optionally emailed, that lets someone connect their own accounts to your workspace without having a PostFast account at all, expiring after 1 to 30 days.
Two things worth knowing before the first flow. Delete Post removes a scheduled or failed post; published posts cannot be removed through it. And PostFast has no triggers. The inbox does not push into FlowRunner. A flow that watches it polls Get Unread Count or List Conversations on a schedule, which for a community queue is usually the right shape anyway.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The inbox that triages itself before anyone opens it
Every few minutes a flow calls Get Unread Count, and when it is non-zero calls List Conversations filtered to unread with the triage status Open. For each thread it calls List Conversation Items to read the exchange in order. The agent sorts what it finds. Simple questions with documented answers get a public Reply To Item with an idempotency key, keeping inside the conversation's maxReplyLength. Anything that reads like buying intent gets Assign Conversation to the sales owner and a note into HubSpot with the platform, the handle, and the comment text. Anything about a broken order gets assigned to support and opened as a ticket in Zendesk. Everything the agent handled itself gets Mark Conversation Read and Set Conversation Status to Closed. What the team opens in the morning is not an undifferentiated feed. It is the residue, already assigned.
A week of posts loaded in one request
A content calendar approves a week of posts across five connected accounts. The flow calls Upload Media From URL for each asset to get its storage key, then Create Posts once with up to 15 entries, each targeting one account with its own text, its media items typed as IMAGE or VIDEO, and an automatic first comment holding the link that platforms penalize in the caption. Where a post needs a target that is not just an account, the flow resolves it first: Get Pinterest Boards for a pin, Get YouTube Playlists for an upload, Get Google Business Locations for a Business Profile post, Search Places for a geotag on Facebook or Instagram. Everything is created with the Scheduled status and a future time. List Posts is then read the following week filtered to the failed status, and any failure with its last error is reported into Slack rather than being found by someone scrolling a feed and noticing a gap.
Growth reporting that survives being questioned
On the first of the month a flow calls List Social Accounts to enumerate connected accounts, Get Follower History per account over the previous period to get the current count, the net delta, and the daily series, and Get Post Analytics over the same range for likes, comments, shares, impressions, reach, and video watch-time per published post. It writes the whole thing to Google Sheets with one row per post and one per account, and posts a short summary to the client channel. Counts come back from PostFast as numeric strings, so the flow casts them before arithmetic rather than concatenating them by accident. The value is not the chart. It is that the underlying rows are there when a client asks which post drove the spike, instead of a screenshot nobody can drill into.
Human-in-Loop Highlight
Moderate Item takes three options and they are not equally consequential. Hide removes a comment from public view and unhide puts it back, so the pair is reversible and an agent can reasonably own it: a slur, a spam link, or a phishing attempt in a brand's comment thread should come down in seconds, not when someone gets in. Delete is different. It removes a real person's comment from Instagram, TikTok, Facebook, or Threads permanently, the response comes back DELETED, and there is nothing in this connector that restores it. The comment is not company content. It belongs to a customer who wrote it in public, and deleting it is visible to them and to anyone who saw it before. Brands get into genuine trouble over exactly this, because a deleted complaint reads as a cover-up in a way that a hidden one, or an answered one, does not, and the deletion of a critical comment cannot be explained afterwards with a screenshot nobody kept. So the split is drawn on reversibility. The agent hides autonomously against the policy it was given and logs what it hid. When it believes something should be removed outright, it stops and puts it to the community owner with the evidence attached: "Comment on the TikTok launch post from @handle, posted 14 minutes ago, 31 likes. Text: [full text]. Matches the harassment rule. I have hidden it. Delete permanently, leave it hidden, or unhide and reply?" The owner decides, and their decision is what the record shows. Framing this as human-in-the-loop rather than a confidence threshold is deliberate: the agent is not uncertain about what the comment says, it is unqualified to decide what removing it will cost the brand, and those are different problems.
Agent Capabilities
23 actionsAccounts and Connections
3- List Social Accounts Lists all social media accounts connected to the workspace tied to the API key, each with its platform, connection status, whether it supports the Social Inbox, and its latest captured follower or subscriber count. The returned account id is the socialMediaId used elsewhere.
- Get Follower History Returns the daily follower or subscriber history for a connected account, including the current count, the net change across the range, and a time series of daily snapshots ordered oldest first. Defaults to the last 90 days and is capped at 365. Counts come back as numeric strings.
- Create Connect Link Generates a secure link that lets someone connect their own social accounts to your workspace without having a PostFast account. The link can optionally be emailed to a recipient and expires after a configurable number of days, 1 to 30, defaulting to 7.
Post Targets
4- Search Places Searches geotagging locations, meaning Facebook Pages, that can be attached to Facebook and Instagram posts. The returned id works as both a Facebook place id and an Instagram location id. Requires a search string of at least two characters and returns up to 100 matches.
- Get Pinterest Boards Lists the Pinterest boards available for a connected Pinterest account. Use a board id as the target when scheduling a pin via post controls.
- Get YouTube Playlists Lists the YouTube playlists available for a connected YouTube account. Use a playlist id when scheduling a YouTube upload via post controls.
- Get Google Business Locations Lists the Google Business Profile locations available for a connected Google Business account. Use a location id when scheduling a Google Business post via post controls.
Posts
4- Create Posts Creates and schedules 1 to 15 posts in a single request, each targeting one connected account and carrying text, media items, and an optional automatic first comment. Set a post's status to Draft to save it without a scheduled time, or Scheduled with a future scheduledAt to publish automatically. Returns the ids of the created posts.
- List Posts Retrieves a paginated list of posts in the workspace, filterable by post ids, platforms, statuses, and a scheduled date range. Returns each post's content, status, schedule, media items, publish result, and any last error, automatically scoped to the workspace tied to the API key.
- Delete Post Deletes a scheduled or failed post by its id. Published posts cannot be removed through this endpoint, so a flow that treats it as a general retraction will be wrong at exactly the moment it matters.
- Get Post Analytics Retrieves performance metrics for posts published within a date range, optionally narrowed to specific platforms or accounts, including likes, comments, shares, impressions, reach, and video watch-time. Metric counts are returned as numeric strings.
Media
2- Get Upload URLs Generates pre-signed S3 upload URLs for attaching media to posts. Provide the file MIME type and how many URLs you need, 1 to 8 for images and a maximum of 1 for videos or documents. Returns key and signedUrl pairs: PUT each file to its signedUrl, then reference the key in a post's media items.
- Upload Media From URL Uploads a single media file from a publicly accessible URL and returns the media key to use in a post's mediaItems. The file is downloaded, a pre-signed upload URL is requested for the given MIME type, and the bytes are streamed to storage in one call.
Social Inbox
10- List Conversations Lists Social Inbox conversations, meaning comment threads and messages, across connected accounts, filterable by platforms, accounts, triage status, unread state, and assignee. Returns a paginated envelope with reply capability flags per conversation. Available for platforms that expose comments.
- Get Conversation Retrieves a single Social Inbox conversation by id, including its platform, triage status, unread count, and reply capability.
- List Conversation Items Lists the individual items within a conversation, meaning comments, replies, and messages, ordered as a thread. Item ids from here are what the reply and moderation actions take.
- Get Unread Count Returns the total number of unread Social Inbox items across the workspace. The cheapest poll for a flow that only needs to know whether there is anything to do.
- Reply To Item Posts a public reply to a Social Inbox item. The reply text must fit within the conversation's maxReplyLength. Supply an idempotency key so a retry after a network timeout cannot post the same reply twice.
- Send Private Reply Sends a private reply to the author of a Social Inbox item where the platform supports it, limited to 1,000 bytes. Also accepts an idempotency key for safe retries.
- Moderate Item Moderates a Social Inbox item by hiding, unhiding, or deleting it on the source platform, returning the resulting visibility state as VISIBLE, HIDDEN, or DELETED. Hide and unhide are a reversible pair. Delete is not, and nothing here restores a deleted item.
- Mark Conversation Read Marks all items in a conversation as read, clearing its unread count. Use it after the agent has handled a thread so the next poll does not pick it up again.
- Set Conversation Status Changes a conversation's triage status. Open is the default for a new conversation, Snoozed parks it for later, and Closed marks it as handled.
- Assign Conversation Assigns a conversation to a workspace user, or clears the assignment when no user id is provided. This is how a flow turns a comment into somebody's actual responsibility rather than a notification.
Frequently Asked Questions
What can FlowRunner do with PostFast?
FlowRunner agents can run List Social Accounts, Get Follower History, and Search Places in PostFast, plus 20 more actions.
Does connecting PostFast to FlowRunner require OAuth?
No. PostFast connects to FlowRunner with an API key, no OAuth flow required.
Can PostFast trigger a FlowRunner workflow automatically?
PostFast doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with PostFast
$100 in credits. No card required. Connect in minutes.