Connect Mastodon Custom Instance to Devad POST

Connect a Mastodon-compatible instance and publish statuses with optional media.

What this channel does

• Mastodon Custom uses a tenant instance URL and access token, so your workspace controls the credential.
• Only superadmin-enabled and plan-allowed channels appear to tenants in POST.

Before you start

• A Mastodon instance URL.
• An access token with `write:statuses` and `write:media` when using media.
• A POST plan that includes Mastodon Custom.

Connect in Devad POST

• Open `/workspaces/apps/post/channels` and choose Mastodon Custom.
• Instance URL: for example `https://mastodon.social`.
• Access token: paste the app token.
• Username: optional display username.
• Save the connection and confirm the channel appears as connected.

Publish with this channel

• Select the connected instance.
• Choose visibility when needed.
• Attach supported image or video media within instance limits.

Common fixes

• Unauthorized: check token scopes.
• Media rejected: reduce size or use a supported media type.

Security notes

• Never paste tokens, webhooks, passwords, or API keys into tickets, screenshots, public docs, or AI prompts.
• Use a credential dedicated to Devad POST and revoke it if access changes.
• Use HTTPS endpoints only.