How do I send different schedules to different Slack channels?
Set a per-schedule Slack webhook URL to override the workspace default. Useful for routing weekly win-loss and daily ops to different channels.
TL;DR
Each schedule can store its own Slack webhook URL. When set, that URL overrides the workspace-level Slack integration just for that schedule. Useful for routing different cadences to different channels without rewiring the integration.
Steps
- 01In Slack, generate an incoming webhook URL bound to the target channel. Steps live in How do I send Callmine notifications via a manual Slack webhook?.
- 02Copy the webhook URL.
- 03In Callmine, open
/schedules, click the schedule you want to route, and click Edit. - 04Find the Slack webhook override field under Notifications. Paste the channel-specific webhook URL.
- 05Save. The schedule now posts to the override URL instead of the workspace default. Existing runs that already fired are not affected; the next firing uses the new URL.
A common setup
Most teams use the override to fan out cadences:
- ·Daily sales-ops standup →
#ops-callminevia per-schedule webhook. - ·Weekly win-loss review →
#sales-leadershipvia per-schedule webhook. - ·Ad-hoc one-off analyses → workspace-default channel (the
OAuth-connected one in
/settings).
This works because Callmine resolves the Slack destination at run time: schedule override first, workspace integration second. No shared global state to fight with.
When the override fires no notification
- ·The override URL is blank — workspace default is used.
- ·The override URL is malformed — Callmine logs an error and falls back to the workspace default.
- ·Both override and workspace default are unset — the run completes
silently. Reports still appear on
/dashboardas usual.
The resolution always happens; the only difference is which channel ends up receiving the Block Kit message.