Skip to main content

Managing Destinations

The Destinations page lets you create and manage delivery targets for your events.

Creating a Destination​

Discord (Manual)​

  1. Click Create Destination
  2. Enter a name
  3. Select Discord as the type
  4. Paste a Discord webhook URL
  5. Optionally enter a Thread ID to post all messages to a specific thread (see Thread Support)
  6. Optionally filter by event types
  7. Click Create

Discord (OAuth)​

  1. Click Connect Discord
  2. Authorize the Dispatch bot for your server
  3. Select a channel
  4. Dispatch creates the webhook and destination automatically

Slack​

  1. Click Connect Slack
  2. Authorize the Dispatch app for your workspace
  3. Select a channel
  4. Dispatch creates the destination and configures posting to the selected channel

Telegram​

Click Connect on the Telegram card and choose a mode:

Direct messages — authenticate with your Telegram account, start a conversation with the bot, then verify DMs are open.

Group or channel — add the bot to your group or channel, generate a verification code in the dashboard, send the code in the chat, and Dispatch auto-detects it.

See Telegram for the full step-by-step setup.

Google Chat​

  1. In your Google Chat space, click the space name → Apps & integrations → Webhooks → Add webhook
  2. Name the webhook (e.g. Dispatch) — this becomes the sender display name in Google Chat
  3. Click Save and copy the webhook URL
  4. In Dispatch, click Add Destination → Webhook URL tab
  5. Select Google Chat as the provider, paste the webhook URL, and name the destination
  6. Click Add Destination

Custom Webhook​

  1. Click Create Destination
  2. Enter a name
  3. Select Webhook as the type
  4. Enter the target URL
  5. Click Create

Event Type Filtering​

Set the Event Types list to only receive specific event types. Leave empty to accept all events.

Example: Set event types to ["push", "pull_request"] to only receive those GitHub events at this destination, even if the endpoint receives other event types.

Active/Inactive Toggle​

Deactivate a destination to stop delivering events to it. Events are still received and stored by the endpoint — they're just not delivered to inactive destinations.

Editing​

Update the destination name, webhook URL, event type list, or active status at any time. Changes take effect for the next delivery.

Deleting and Archiving​

Click the trash icon on a destination to remove it. Dispatch picks one of two outcomes automatically so your delivery history and billing stay intact:

  • Permanent delete when the destination has zero delivery attempts. The destination and all its endpoint-destination links are removed from the database with no record left behind.
  • Archive when any deliveries have been attempted. The destination is hidden from the active list and skipped during fan-out, but every past delivery attempt remains in the database so it stays visible on the Events page and counts toward billing.

Archived destinations show up under the Archived option in the status filter on the Destinations page. Click Restore on any archived destination to re-enable it — its links, retry policy, and delivery history are preserved.