Hootsuite
Social MediaSchedule and manage social publishing through Hootsuite. Agents queue posts to connected social profiles, review and cancel scheduled messages, register media uploads, and read account and organization details via the Hootsuite REST API.
What This Integration Enables
Social publishing is the rare workflow where the last step is instantly public and effectively permanent, which is why it deserves more orchestration discipline than most teams give it. This connector puts Hootsuite's publishing pipeline under agent control: FlowRunner agents resolve connected profiles across networks, register and attach media, queue posts for future send times or immediate publishing, and read the outbound queue by state and time window to audit what is about to happen and verify what did. The stance: automation should own the mechanics of publishing, the resolving, uploading, queueing, and verifying, precisely so humans can concentrate on the only part that matters, whether this copy should represent the company today. - Schedule posts across Twitter/X, Facebook, LinkedIn, Instagram, and other connected profiles from one flow - Drive publishing from a content calendar, CRM, or form instead of manual queue entry - Attach images and video via registered media uploads - Audit and cancel scheduled posts programmatically before they send - Confirm the connected account and organization scope before any publishing run
Without FlowRunner
With FlowRunner
Use Case Scenarios
The content calendar that publishes itself
Marketing plans the month in [Google Sheets](/integrations/google-sheets): copy, target profiles, send time, image link per row. Once the social lead approves the batch, the agent walks the rows, registers each image with Register Media Upload, schedules each post with Schedule Message, and writes the returned message ID into the row. The calendar becomes the system of record for what is queued, and a change of plan means editing the sheet and letting the agent reconcile the queue, not re-doing the week by hand.
The pre-send audit that catches the awkward post
Every morning, the agent calls List Messages for the next 48 hours across all profiles and posts the lineup to [Slack](/integrations/slack): what is going out, where, and when. When news breaks that makes a scheduled post tone-deaf, the team sees the conflict in the lineup, and the agent cancels the flagged post with Delete Message on the social lead's confirmation. The queue stops being a black box that occasionally embarrasses the brand.
Launch-day coordination across every channel
A product launch flow assembles the announcement from the release notes, generates per-network variants, and holds them for review. On the marketing lead's approval, Schedule Message queues the full set with staggered send times across LinkedIn, Twitter/X, and Facebook profiles resolved via List Social Profiles. After each send window, Get Message confirms the sent state, and the results log to the launch tracker. Every channel fires on schedule because one flow owns the sequence, not five people with reminders.
Human-in-Loop Highlight
Schedule Message with no send time publishes immediately, and once a post is live, Delete Message cannot pull it back from the network: the API can cancel a scheduled message, but an already-sent post is out, screenshot-able, and syndicated to however many feeds saw it. That asymmetry defines how FlowRunner flows use this connector. Everything before the queue is autonomous: profiles resolved, media registered, copy validated, timing planned. But no message enters the queue without the social lead approving the batch through a [human-in-the-loop](/concepts/human-in-the-loop) step, exact copy against exact profile IDs, because the difference between the test account and the flagship brand account is one ID in a socialProfileIds array. Cancellation is gated the same way in reverse: the agent flags, the human decides, Delete Message executes. Public speech at brand scale is the least reversible write in this entire catalog, and the flow treats it that way.
Agent Capabilities
9 actionsAccount
2- Get Me Retrieves the profile of the authenticated Hootsuite member, id, full name, email, and account details. The pre-flight check that confirms which account is connected before any publishing run.
- List Organizations Retrieves the organizations the authenticated member belongs to. Organizations group social profiles and team members, defining the member's scope of access.
Social Profiles
2- List Social Profiles Retrieves all connected social network accounts the member can publish to, across Twitter/X, Facebook, LinkedIn, Instagram, YouTube, and Pinterest. The returned profile IDs are required for scheduling.
- Get Social Profile Retrieves a single social profile by ID, including network type, owner, and the associated social account. Used to verify a target before scheduling to it.
Messages
4- Schedule Message Schedules a post to one or more social profiles at a future send time, or publishes immediately if no time is provided. Takes the post text, target profile IDs, an ISO 8601 send time, and optional registered media IDs. The write this page's human gate exists for.
- List Messages Retrieves outbound messages, scheduled, pending approval, or sent, filtered by state and a time window bounded by ISO 8601 start and end times. The audit call behind lineup reviews and failure alerts.
- Get Message Retrieves a single outbound message by ID with its text, state, scheduled send time, and target profile. The verification step after scheduling and after send windows.
- Delete Message Deletes or unschedules an outbound message by ID. Cancels publishing for scheduled posts that have not sent; already-sent messages generally cannot be removed from the originating network through this endpoint.
Media
1- Register Media Upload Registers a media file and returns a signed upload URL plus a media ID. PUT the raw bytes to the URL, then reference the media ID when scheduling. Takes the file size in bytes and MIME type.
Frequently Asked Questions
What can FlowRunner do with Hootsuite?
FlowRunner agents can run Get Me, List Organizations, and List Social Profiles in Hootsuite, plus 6 more actions.
Does connecting Hootsuite to FlowRunner require OAuth?
Yes. Hootsuite connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Hootsuite trigger a FlowRunner workflow automatically?
Hootsuite doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Hootsuite
$100 in credits. No card required. Connect in minutes.