Mastodon
Social MediaPublish and manage statuses on Mastodon from AI agents: post toots with controlled visibility, boost and favourite, read home and public timelines, search the fediverse, and pull notifications for triage.
What This Integration Enables
Mastodon is where a specific and valuable audience lives: developers, researchers, and the people who left centralized platforms on principle. That audience punishes broadcast spam and rewards presence, which makes it exactly wrong for naive auto-posting and exactly right for orchestrated posting with a human gate. FlowRunner agents handle the mechanics on any instance: drafting statuses from source content, controlling visibility per post, sweeping timelines and notifications, and searching the fediverse, while the judgment calls stay with the person who owns the account's reputation. - Publish statuses with explicit visibility: Public, Unlisted, Followers Only, or Direct - Attach content warnings and sensitive-media flags where the audience's norms expect them - Sweep home and public timelines, account statuses, and notifications on a schedule - Search accounts, hashtags, and statuses across the fediverse with remote resolution - Favourite and boost programmatically in response to events, under the same review discipline - Verify the connected account before anything posts under the brand's handle
Without FlowRunner
With FlowRunner
Use Case Scenarios
Release announcements that reach the fediverse the same hour
When a release post goes live, the agent drafts the toot with the summary, link, and the project's hashtags, and posts the draft to [Slack](/integrations/slack) for the social owner. On approval, Post Status publishes it as Public. The agent then watches List Notifications for the following days, logging boosts and favourites to the engagement sheet and routing substantive replies back to the channel. The announcement reaches the instance's local timeline and federates outward while the release is still news.
Brand and topic monitoring across instances
Every fifteen minutes, an agent runs Search for the product name and key hashtags with Resolve enabled, and Get Public Timeline filtered to the local instance where the community congregates. New matches are deduplicated against the log in [Google Sheets](/integrations/google-sheets), then routed: bug reports and support questions go to the support channel, praise and reviews go to marketing, and everything gets an entry with author, link, and text. The team hears about a widely-boosted complaint from the agent, not from a screenshot two days later.
Cross-posting with per-network judgment
The content team writes once and distributes everywhere, but the fediverse version should not read like a repurposed ad. The agent pulls approved posts from the content calendar, adapts each draft, and queues it for review with visibility suggested: Public for announcements, Unlisted for the third repost of the same link. Approved toots publish via Post Status; selected community posts from Get Home Timeline flow the other way, mirrored to [Bluesky](/integrations/bluesky) after the same review. Each network gets a native voice, and no network gets an accident.
Human-in-Loop Highlight
Post Status with Public visibility is the least recallable publish in this catalog, because federation is replication: the moment a toot posts, other instances copy it, followers' clients cache it, and any boost carries it into timelines your account does not control. Delete Status will remove it from your instance and return the source text for redrafting, but the connector cannot unsend what federation already delivered. So the brand account's public posts run gated. The agent drafts, runs Verify Credentials to confirm which account it holds, and presents the toot with its visibility setting spelled out: "Public, brand account, 480 characters, one link. Post?" The social owner reads it as the audience will, fixes the tone that was fine everywhere else and wrong here, and approves. On a network built by people who distrust automated brands, the human gate is not overhead. It is the strategy.
Agent Capabilities
12 actionsStatuses
5- Post Status Publishes a new status to the connected account with plain-text content, optional content and spoiler warnings, sensitive-media flagging, reply threading, attached media, and explicit visibility. The publish this page's human gate exists for.
- Get Status Retrieves a single status by ID, including HTML content, author account, media attachments, visibility, and engagement counts for favourites, reblogs, and replies.
- Delete Status Permanently deletes a status owned by the connected account, returning the deleted status with its source text for redrafting. Cannot be undone, and federated copies may persist.
- Favourite Status Adds the connected account's favourite to a status and returns the updated status with the incremented count. Used sparingly and under review, because engagement is also speech.
- Boost Status Reblogs a status so it appears to the connected account's followers, returning a new status wrapping the original. A public endorsement, so gated like one.
Timelines
2- Get Home Timeline Retrieves statuses from followed accounts in reverse chronological order, with paging by max and since ID. The feed behind curation and cross-posting workflows.
- Get Public Timeline Retrieves public statuses across the fediverse, restrictable to the local instance, with paging and a media-only filter. The listening post for community monitoring.
Accounts
3- Verify Credentials Retrieves the authenticated account's details: display name, handle, avatar, follower and following counts, and source settings. The check that confirms which account an agent is about to speak as.
- Get Account Retrieves a public profile by account ID, including display name, handle, bio, avatar, header image, and follower, following, and status counts.
- Get Account Statuses Retrieves an account's published statuses in reverse chronological order, filterable to exclude replies and reblogs or show only media and pinned posts.
Search
1- Search Searches accounts, hashtags, and statuses matching a query via the v2 search API, filterable to one result type, with remote resolution for handles and URLs. The discovery step behind monitoring and outreach research.
Notifications
1- List Notifications Retrieves the connected account's notifications, mentions, favourites, boosts, follows, and poll results, newest first, filterable by type and paginated. The queue behind reply triage.
Frequently Asked Questions
What can FlowRunner do with Mastodon?
FlowRunner agents can run Post Status, Get Status, and Delete Status in Mastodon, plus 9 more actions.
Does connecting Mastodon to FlowRunner require OAuth?
No. Mastodon connects to FlowRunner with an API key, no OAuth flow required.
Can Mastodon trigger a FlowRunner workflow automatically?
Mastodon doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Mastodon
$100 in credits. No card required. Connect in minutes.