Edit history

A UX problem currently exists where messages from webhooks in an announcement channel are not auto-published to followed channels. For these messages to publish, someone has to manually publish the message. This is an issue as of Fluxer 2026.1107.20335.

There are two proposed changes that I'm providing, the first being the most ideal and the second being the least ideal:

1. Have webhook messages be auto-published. If someone is managing many announcement channels across multiple communities, it becomes incredibly difficult to remember to publish these messages, especially if webhook messages are being sent by another party and not the creator of the announcement channels.

2. Make it incredibly obvious to the users who have permissions to publish these messages that they haven't been published yet. This is an improvement over the current UX, but manually publishing many webhook messages can still be a chore.

Message appears in the announcement channel for Community A, but is not published into #text-channel of Community B

The webhook message appears in #text-channel of Community B.

Reproduction steps

1. Create an announcement channel in Community A.
2. Add a webhook to the announcement channel.
3. Follow the announcement channel in #text-channel in Community B.
4. Send message through the webhook.

Build information Fluxer 2026.1107.20335