Skip to main content

Delivery channels

Delivery channels are where you publish prepared content. A digest can combine materials from any supported source and be sent to Telegram, Discord or several channels at once. To retrieve results in your own system, use the API and outgoing webhooks; these are separate from publication destinations.

Connect a destination​

Open Delivery channels and choose the service you want to connect. The Telegram and Discord tabs here group connection settings; you choose the channels for each publication in the digest editor.

Telegram​

  1. Connect a Telegram account and enable its publishing role. See Telegram integration.
  2. Synchronize its channels in Delivery channels → Telegram.
  3. Check the destination and its publishing account. The account must have permission to post to the channel.

The collecting account and publishing account can be different.

Discord​

You need a webhook URL for a Discord channel you manage. You do not need a Telegram account to publish to Discord.

  1. Open Delivery channels → Discord.
  2. Add a destination name and its webhook URL, then save.
  3. Use Send labelled test message to check the connection. It sends “Signailist test delivery” to that channel. Saving a connection alone sends nothing.

Treat the webhook URL as a secret: it allows messages to be sent to the channel. Signailist stores it encrypted. Do not put it in source URLs, topic instructions or setup names.

For a saved connection, the URL field is masked and disabled. Choose Change URL to enter an updated URL for the same webhook. Add a different webhook as a new destination. Revoking a connection removes its saved URL and disables the linked destinations.

Publish a digest​

  1. Prepare the digest using the Text, Image and Sources tabs.
  2. Open Publication and check the saved preview. Prepare a new publication revision if you changed the content.
  3. Approve the revision you want to send.
  4. Select one or more destinations. You can combine Telegram and Discord channels. For Telegram, choose the publishing account or use the accounts configured for each channel. Only enabled accounts with publishing permission are offered; the account must have permission to post to the selected channels.
  5. Choose Now or a future send time, then send to the selected channels.

All selected channels receive the same approved revision. They share the chosen send time; each service processes its delivery separately, so messages may arrive a little apart. Formatting and message length limits depend on the service.

Editing a digest does not change a revision already queued for delivery. Cancel a queued delivery if needed, then prepare and approve a new revision. Choosing channels for a manual publication does not enable a recurring schedule.

If publishing is paused, you can continue editing and reviewing the digest, but sending is unavailable. There is no alternate send form. The selected Telegram account is saved with the delivery; changing channel defaults later does not change that delivery.

Check delivery​

Each destination has its own delivery status and receipt details:

  • Queued / Sending / Waiting to retry: delivery is still in progress.
  • Delivered: the service accepted the message. Open the destination channel to see the publication.
  • Failed: check the destination and follow the instructions beside the error.
  • Unknown: the service may have accepted the message without returning confirmation. Check the channel before trying again to avoid duplicates.
  • Partial delivery: some parts were delivered. Inspect the channel and delivery details before sending again.

One channel's result does not confirm delivery to another channel. Saved delivery details remain available after a page refresh. Queued deliveries can be canceled from the publication history.

Recurring publications and alerts​

Configure recurring digest rules separately in Signals and autopublish. A rule has its own destination and schedule; it does not inherit the channels selected for a manual send.

Signal alerts and Telegram moderation cards have their own settings. Connecting a Discord publication destination does not redirect these notifications.