Mastodon scheduling that respects the instance

Start with the account’s instance

Mastodon connects through instance-specific OAuth. The server URL matters as much as the account handle; a token from one instance is not a universal Mastodon credential. The implementation registers and resolves an application for the selected instance rather than using one shared destination.

Review visibility and content warnings

The provider includes text, image, video and poll paths. It also passes visibility and content-warning text. It has a 500-character default and an instance-limit lookup, so check the actual server’s limits instead of treating the default as universal.

• Choose visibility deliberately before scheduling.
• Include a content warning when the material calls for it.
• For polls, review options, duration and whether multiple choices are allowed.

Keep the draft appropriate for its community

In an enabled workspace, give the agent the instance, audience and approved source material. Ask it to prepare a draft with the requested visibility and content warning for review, not to assume that a public cross-post is always appropriate.

Prepare a Mastodon draft for this account using the approved text. Keep the requested content warning, show the visibility choice, and do not schedule yet.

Mastodon availability

Customer Mastodon connections and hosted publishing are not open in PostDelegate’s public preview. Real authorization and publishing must be verified on the intended instance. This guide does not claim compatibility with every server, extension or federation configuration.