Publish & grow
Publish to communities, chat channels, and the fediverse
Connect bots, webhooks, and community accounts, choose the exact destination, and troubleshoot permissions for nontraditional publishing channels.
Updated
Connect a messaging destination
| Destination | Connection and routing | Check before approving |
|---|---|---|
| Telegram | Add @KrevayaBot as an administrator, then connect the channel handle or private chat ID. | The bot must be able to post. Private groups may not provide a public message link. |
| Discord | Authorize the bot for a server, then choose a channel on the post. | Allow Send Messages, Attach Files, and Embed Links in that channel. |
| Slack | Authorize the workspace, then choose a public channel. | Private Slack channels are not supported by this integration. |
| LINE | Connect a Messaging API channel access token. | A broadcast reaches followers and counts against the LINE quota. |
| Microsoft Teams | Connect the channel's supported incoming webhook URL. | The post appears as a webhook card, not a named user's message. |
| Google Chat | Connect a space webhook URL. | The space must offer webhooks; personal Gmail spaces do not. |
| Mattermost | Connect an incoming webhook for the intended channel. | The HTTPS server must be reachable from Krevaya. |
Choose a forum or community destination
Lemmy needs an instance login and a community, title, and optional link on the post. Discourse uses a user-level API key and posts a new topic in the selected category. Circle uses an Admin API token and a selected space. Whop uses OAuth and a selected forum.
The connected account is not always the final destination. Read the category, forum, space, or community on every post. A valid connection can still be refused by a community's rules or by the account's permissions.
Use fediverse and specialist channels
For Mastodon or Pixelfed, enter your server in Connections and authorize on that server's page. Mastodon visibility can be public, unlisted, or followers only; check that choice for each post. Server-specific character and media limits can vary.
Tumblr lets you choose the blog on a post. Dribbble publishes a single image shot with a title and optional tags; inspect the 4:3 crop. Vimeo requires a video and its available video settings. These destinations do not share a single universal post format.
Test one message before building a routine
- Connect the destination and verify the displayed account, workspace, or server.
- Create a small draft with the exact channel or community selected.
- Check bot membership, webhook location, and media format before approving.
- Publish only when the message is ready for that audience, then inspect the result in the destination.
- If it fails or is held, read the permission or routing message before creating another post.
Treat webhook URLs and channel tokens as credentials. If one is exposed or revoked, replace it in the provider and update the connection rather than pasting it into a support screenshot.