Simplified

Publish and schedule social content, pull analytics, and generate AI images with the Simplified API. Agents queue posts across networks and hold anything sensitive for approval.

19 actions API key available

Simplified website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

An incident is declared and the status page moves to a degraded state

Agent calls Get Social Posts to list everything scheduled across every connected account for the next 24 hours

Agent reads each post's group ID, target networks, copy and send time

Agent separates promotional posts from anything already cleared to run during an incident

Agent posts the scheduled list into the incident channel with copy, networks and send times

The incident commander names which groups to pull, and the agent calls Delete Social Post on exactly those group IDs

What This Integration Enables

Simplified is a one-workspace, many-networks publisher, and the connector treats it that way. A single Create Social Post call fans one piece of content across Facebook, Instagram, LinkedIn, TikTok, YouTube, Pinterest, Threads, Bluesky and Google Business Profile, with per-network options and per-network character limits that differ by an order of magnitude. Around that sit the two things that make a publishing queue safe to automate: a draft and review-bundle stage where a client or stakeholder signs off on the actual content, and an analytics surface that returns both headline totals and day-by-day series so the report writes itself.

The AI image side is asynchronous by design, which is the correct shape for it. Generate Image returns a task immediately and the agent polls Get Image Generation Status until the job reaches DONE or FAILED, so a flow can produce campaign artwork from a prompt without blocking on it. What the connector deliberately does not give you is a fire-and-forget publisher. Nothing here schedules content to a customer-facing account without a person having seen it, and the queue an agent builds is the queue a person can read, question and pull. That is the difference between a scheduler and Orchestration as a Service.

Without FlowRunner

Marketing runs blind to incidents Scheduled campaigns keep publishing while customers are already watching the status page

The queue is visible in one tool Nobody outside the social platform knows what is going out in the next few hours

Approvals over screenshots Client sign-off happens on pasted images rather than the drafts that will actually publish

With FlowRunner

The queue reaches the incident channel What is about to publish is readable from the room where the incident is being run

One decision pulls a campaign Group IDs are resolved in advance so pulling posts is a single call, not a hunt through a calendar

Sign-off on the real drafts A review bundle holds the exact drafts that will go out, and nothing else can

Use Case Scenarios

Freezing the queue during a live incident

An incident opens in PagerDuty and Statuspage flips to degraded. The agent immediately calls Get Social Posts for everything scheduled in the next 24 hours across every connected account, reads the copy and the send times, and posts that list into the incident channel. Marketing usually has no idea what is queued when an incident starts, and the failure mode is recognizable: a cheerful product post landing on LinkedIn while the product is down, and screenshots of it in replies for the rest of the week. The agent does not delete anything on its own, because Delete Social Post removes rather than pauses and a pulled campaign has to be rebuilt from scratch. It puts the list in front of the commander and executes the decision.

Client approval on the drafts that will actually publish

An agency drafts a week of content and needs sign-off. The agent creates each post as a draft, groups them with Create Review Bundle, and extends the bundle with Add Drafts To Review Bundle as later batches are produced. The client reviews the bundle itself rather than a document describing it, so what they approve is byte-for-byte what publishes. Where the client asks for a change, the agent applies it with Update Social Draft and the bundle stays intact. Nothing moves from draft to scheduled until the bundle is signed off.

Weekly performance pack without a manual export

Every Monday the agent walks Get Social Accounts, then pulls Get Aggregated Analytics for headline totals, Get Analytics Range for the day-by-day series and Get Audience Analytics for follower composition, per account, over the previous week. Get Post Analytics ranks individual posts by engagement so the pack shows which content actually worked rather than only what the account did overall. All of it lands in Google Sheets with the prior week alongside it. Where an account's engagement moves sharply in either direction, the agent flags it in Slack with the posts that drove the change attached.

Human-in-Loop Highlight

The gate is the scheduled post that would land during an outage. It is worth naming plainly because it is the most avoidable public failure a marketing team has: a campaign queued three days ago publishing into a live incident, timed perfectly to look like nobody is paying attention. The agent can see it coming, because Get Social Posts returns everything scheduled with its send time, and it can act, because Delete Social Post accepts a whole post group by group ID. What it cannot do is decide, because deleting is not pausing. Simplified has no unschedule operation, so pulling a campaign means destroying the scheduled instances and rebuilding them later, and the call on whether a given post is tone-deaf or entirely fine belongs to whoever is running the incident. So the agent posts into the incident channel: "6 posts scheduled in the next 24 hours across 4 accounts. Group 8812 goes to LinkedIn and Threads at 14:00 with launch copy. Group 8817 is a recruiting post at 17:00. Delete which groups? Deleted posts must be recreated." The commander names them. The agent deletes exactly those and confirms. Human-in-the-loop here costs one message and prevents a screenshot that outlives the outage.

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

19 actions

Accounts and Workspaces

Get Social Accounts Lists the social accounts connected to the workspace with each account's internal ID, display name and network. The IDs returned here are what Create Social Post and every analytics operation expect. Can be narrowed to a single network.
List Workspaces Lists the Simplified workspaces the API key can reach, with their IDs and names. The workspace ID is what the AI image operations run against on multi-workspace accounts.

Publishing

Create Social Post Publishes, queues, schedules or drafts a post across one or more connected accounts in a single call. Supports media by URL, threaded follow-up comments with per-comment delays, and per-platform options such as YouTube privacy status or LinkedIn audience. Character limits vary by network, from 300 on Bluesky to 3000 on LinkedIn.
Get Social Posts Reads published and scheduled posts for the workspace, optionally filtered to specific accounts or a category, with paging. Used to audit what has gone out and to resolve a post or group ID before changing anything.
Update Social Post Edits a scheduled or queued post's message, media or send time. Supply only the fields that change. Posts already published are not editable on every network.
Delete Social Post Removes a scheduled or published post. Takes either a whole post group by group ID, meaning every network variant created together, or a single network's scheduled instance by post schedule ID. Exactly one of the two is supplied, and the removal is not a pause.

Drafts and Review

Get Social Drafts Reads unpublished drafts for the workspace, optionally filtered to specific accounts, with paging. The draft IDs returned here feed the update, delete and review-bundle operations.
Update Social Draft Edits a draft's message, media or per-platform options before it is published or sent for review. Supply only the fields that change.
Delete Social Draft Removes one or more drafts, either a whole draft group by group ID or specific drafts by their IDs.
Create Review Bundle Groups drafts into a named bundle so a client or stakeholder approves them together before anything publishes. Returns the bundle ID.
Add Drafts To Review Bundle Appends further drafts to an existing bundle without recreating it. Used when content is produced in batches but reviewed as one set.

Analytics

Get Aggregated Analytics Returns headline performance totals for one connected account over a date range, such as reach, impressions, engagement and follower count. Used for summary reporting.
Get Analytics Range Returns a day-by-day series for the selected metrics on one account, bucketed across the requested range in a supplied timezone. Used to chart growth or find the day a spike started.
Get Post Analytics Returns per-post performance for one account over a date range, so individual posts can be ranked by engagement rather than rolled into an account total. Paged.
Get Audience Analytics Returns audience composition and follower data for one account over a date range. Used to check whether a campaign built an audience or only generated impressions.

AI Images

Generate Image Starts an AI image generation job from a text prompt, optionally with one or more reference images, producing between one and four images. Returns a task and art variation ID immediately, because generation is asynchronous.
List Image Models Lists the image models available to the workspace with the capabilities each supports. Called before Generate Image, since model availability changes over time.
Get Image Generation Status Checks whether a generation job has finished and returns the image URLs once it has. Status runs CREATED, PENDING and PROCESSING to either DONE or FAILED.

Jobs

Get Task Status Reads the state of any asynchronous Simplified task by its task ID, with the current status and any result payload. Simplified delivers no webhooks, so polling this is how long-running jobs are followed to completion.

Frequently Asked Questions

What can FlowRunner do with Simplified?

FlowRunner agents can run Get Social Accounts, Create Social Post, and Get Social Posts in Simplified, plus 16 more actions.

Does connecting Simplified to FlowRunner require OAuth?

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

Can Simplified trigger a FlowRunner workflow automatically?

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

Start building with Simplified

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

Start Building Free Talk to us