ContentStudio

Schedule and publish social media content through ContentStudio. Agents create, list, and publish posts across connected channels and enumerate the workspaces and channels available to your account.

6 actions API key available

ContentStudio website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A product update ships, a blog post publishes, or finished creative lands from the design pipeline

The agent drafts platform-appropriate copy variants from the source material

List Channels resolves the target channel IDs across the connected networks

Create Post saves each variant as a draft in the workspace, media URLs attached, no scheduled time set

The social manager gets the drafts with links to review each one

The manager reviews copy and imagery, edits what needs it, and approves the batch

Create Post schedules the approved variants at the times the manager set

What This Integration Enables

The bottleneck in social publishing is rarely writing one post; it is the assembly line around it, reshaping copy per platform, collecting media, filling the queue, and noticing what failed. ContentStudio's workspace, channel, post model gives that assembly line an API, and FlowRunner agents run it. Content produced anywhere in your stack becomes drafts in the queue, humans approve what goes out under the brand's name, and the queue's state stays visible without anyone logging in to check. - Turn launches, blog posts, and finished designs into per-platform draft posts - Schedule approved content across Facebook, Instagram, X, LinkedIn, Pinterest, and TikTok channels - Push a prepared draft live immediately when a workflow event calls for it - Audit the queue by status, including failed posts that would otherwise vanish silently - Work across multiple workspaces for agencies managing several brands The division of labor here is deliberate and it is the whole point. Social publishing mixes two very different kinds of work: assembly, which is repetitive and precise, and voice, which is judgment. Tools that automate both end up posting things a human never read; tools that automate neither burn the team's hours on copy-paste. FlowRunner splits the seam cleanly: agents own the assembly line from source content to staged draft, the [human-in-the-loop](/concepts/human-in-the-loop) gate owns the moment the brand speaks, and the queue audit keeps both honest. Publishing gets faster precisely because the judgment step stopped being rushed. For agencies running several brands through separate workspaces, the same split scales sideways: one set of flows, many queues, and a named human approver in front of each brand's voice.

Without FlowRunner

Social is the step that slips The launch ships, the blog publishes, and the posts announcing them go out two days late

One message pasted five times Cross-posting means manually reshaping the same copy per platform, or not bothering

The queue is a black box What is scheduled, what published, and what failed lives behind one person's login

With FlowRunner

Content events produce drafts instantly Every launch and publish arrives in the queue as reviewable drafts within minutes

Variants are drafted per platform Agents shape the copy for each channel and a person approves the batch once

The queue reports itself Scheduled, published, draft, and failed posts flow into audits and dashboards

Use Case Scenarios

From finished design to filled queue

A graphic exports from [Canva](/integrations/canva). The agent pairs it with copy variants drafted for each platform, calls List Channels to get the workspace's channel IDs, and creates one draft per platform with the media URL attached. The social manager opens the queue to find the week's campaign already staged, edits two captions, sets the schedule, and approves. The part of the job that was copying and pasting into six tabs is gone; the part that was judgment remains.

The queue audit that catches silent failures

Every morning an agent calls List Posts filtered to Failed, then to Scheduled for the next 48 hours. Failures post to [Slack](/integrations/slack) with the post content and target channel so someone can fix and republish before the gap is visible to followers. The upcoming schedule posts as a digest, which is how the team catches the double-booked slot where two campaigns would have landed on LinkedIn an hour apart. Post IDs and statuses log to [Google Sheets](/integrations/google-sheets) for the monthly content report.

The embargo lift that actually lifts on time

A partnership announcement is drafted and staged days early with Create Post, no schedule set. When the embargo lifts, the moment the partner's press release URL goes live, the flow fires Publish Post Now on the staged post IDs and the announcement hits every channel within the same minute. No one is hovering over a dashboard at 6am, and no channel gets forgotten in the scramble.

Human-in-Loop Highlight

Publish Post Now is the send button for the brand's public voice: the moment it runs, the post is live on Facebook, LinkedIn, X, and every other targeted channel, in front of followers and screenshot-ready even if it is deleted two minutes later. A wrong media attachment, a stale price, or a tone-deaf line during a news cycle becomes a public artifact under the company's name. So FlowRunner flows drive hard toward the draft state and stop there. Agents create, attach media, and stage; a person reads what the audience will read before anything goes live. Even the embargo workflow's instant publish is only instant mechanically: the content it fires was human-approved days earlier, and the automation's job is timing, not judgment. The queue fills at machine speed. The brand speaks only after a person has read the words.

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

6 actions

Posts

List Posts Lists a workspace's posts across scheduled, published, draft, and failed states, with status, target channels, content, and scheduled time. The read behind queue audits, failure alerts, and schedule digests.
Get Post Retrieves one post in full: content, target channels, status, media attachments, and scheduled time. Used to verify a staged post before publish and to investigate failures.
Create Post Creates a post targeting one or more connected channels, with a scheduled time for later publishing or no time to save as a draft. The workhorse that turns upstream content into a reviewable queue.
Publish Post Now Pushes an existing draft or scheduled post live to its target channels immediately, subject to each channel's rate limits and approval settings. The operation this page's human gate exists for.

Channels

List Channels Lists the social channels connected to a workspace, Facebook, Instagram, X, LinkedIn, Pinterest, TikTok, and others, with ID, platform, and display name. The routing table Create Post depends on.

Workspaces

List Workspaces Lists the workspaces accessible to the API key with ID and name. How multi-brand teams and agencies scope every other operation to the right client.

Frequently Asked Questions

What can FlowRunner do with ContentStudio?

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

Does connecting ContentStudio to FlowRunner require OAuth?

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

Can ContentStudio trigger a FlowRunner workflow automatically?

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

Start building with ContentStudio

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

Start Building Free Talk to us