Post Mastodon Status: Mastodon action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Status Text status	string	Required	Status Text
Visibility visibility	options	Optional	Visibility. Options: Public, Unlisted, Followers only, Direct
Content Warning sensitive	boolean	Optional	Content Warning

Sample request

{
  "status": "{{trigger.status}}",
  "visibility": "{{trigger.visibility}}",
  "sensitive": "{{trigger.sensitive}}"
}

Returns

{
  "id": "status123",
  "url": "https://mastodon.social/@user/status123",
  "content": "<p>Hello fediverse!</p>",
  "created_at": "2026-04-11T10:00:00Z",
  "visibility": "public"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Post Mastodon Status.

What does the Post Mastodon Status action do in Mastodon?

Posts a toot with text up to the instance's limit (default 500 chars), optional visibility (public/unlisted/private/direct) and content warning. For cross-network publishing workflows.

What inputs does Post Mastodon Status require?

Required: Status Text. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Mastodon returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Post Mastodon Status support batch operations?

Yes. Run Post Mastodon Status inside a Loop node to process arrays. Tiny Command handles Mastodon's rate limits automatically so you don't have to throttle manually.

More actions