Instance-specific OAuth
Plan Mastodon in the same workspace as the rest of your channels.
Mastodon
Respect the instance. Keep the workflow familiar
Connect the Mastodon instance your community uses, then prepare posts, media, replies, content warnings, language, and visibility from one consistent editor.
Mastodon publishing flow
Channel version
ValidatedTomorrow 09:30
Mastodon
Delivery state visibleRich post controls
Shape the native format before it reaches the publishing queue.
Ordered replies
Keep access, delivery, and provider state visible to the team.
Plan Mastodon with the rest of the campaign
Start from the shared brief and Brand Soul, then give this channel the timing, copy, and creative treatment it needs.
- Keep the source idea connected to every channel version
- Review the destination and schedule before delivery
- Use one calendar for the complete campaign
Mastodon plan01
1Instance-specific OAuth
2Rich post controls
3Ordered replies
Workspace state Reviewable
Publish formats that belong on Mastodon
BlendDuck keeps native settings where they matter and applies platform validation before the provider receives the request.
- Text and link posts
- Supported images and video
- Reply chains
Supported workflow02
1Visibility and language
2Content warning and sensitive flag
3Media alt text
Workspace state Reviewable
Know what is ready, what shipped, and what needs attention
Connection grants and provider responses stay separate from optimistic UI, so the team can act on the exact missing permission or failed target.
- Public status URL
- Instance response state
- Connection recovery readiness
Operational evidence03
1Connection checked
2Content validated
3Delivery recorded
Workspace state Reviewable