Per-action Slack webhook URL (route different events to different Slack channels)

Currently the Slack webhook URL can only be configured at brand level (Settings → Automation → Notification Channels), so ALL Slack notifications — support tickets, new orders, paid invoices, client registrations, fraud alerts — post to a single Slack channel.

Request: allow overriding the Slack webhook URL per automation action (or per action category), falling back to the brand-level default when not set.

Use case: route ticket notifications to #support-tickets, order/invoice notifications to #orders, and fraud/provisioning alerts to #alerts. In Slack, each channel has its own incoming webhook URL, so this only requires exposing the existing webhook URL field (already present at brand level) on the automation action itself.

This would make Slack notifications far more usable for any team that separates operational workflows into dedicated channels — which is standard practice in Slack.

Feature Request

Allow overriding the Slack webhook URL per automation action (or per action category), with fallback to the brand-level default when not set. Currently the webhook URL is configured only at brand level (Settings → Automation → Notification Channels), so all Slack notifications post to a single channel.

How Would You Use This in Upmind?

I would route different event types to dedicated Slack channels: ticket notifications (Ticket / Ticket Message actions) to #support-tickets, order and payment notifications (Invoice created / Invoice paid) to #orders, and fraud/provisioning alerts (Fraud Review, Setup Failed, Email Complaint) to #alerts. Each Slack channel already has its own incoming webhook URL, so I would simply paste the appropriate URL into each automation action.

What problem does this solve for you?

All my Slack notifications currently land in one channel, mixing urgent items (support tickets that need a fast response) with informational ones (orders, paid invoices, registrations). Urgent tickets get buried between order notifications, and there is no way to apply different Slack notification preferences (mentions, sounds, mobile push) per event type, because Slack preferences are per channel.

Impact of not having this feature

As a solo operator, Slack is my primary notification channel — I moved away from email notifications entirely after outbound notification volume caused domain deliverability problems. Without per-action routing, I have to visually filter one mixed feed, which increases the risk of missing time-sensitive support tickets. The workarounds (Slack paid-plan workflows to re-route messages by keyword) add cost and fragility for something the platform could solve with one field.

Please authenticate to join the conversation.

Upvoters

Status

Suggested

Board

Webhooks, Triggers & Notifications

Date

3 days ago

Author

Web Admins

Subscribe to post

Get notified by email when there are changes.