Summary

Alta sends Slack notifications through four separate paths. Three of them are built-in streams configured on the Notifications page (prospect replies, daily plan, Manual Task approvals). The fourth is Workflows — a Flow can include a Slack action that posts a fully custom message into any channel, on any trigger you can model. This article covers all four.

Who this is for: Anyone who's already connected Slack to Alta and wants notifications to land in the right place — typically RevOps, the campaign owner, or whoever onboarded Slack.

Before you start

You'll need Slack already connected to Alta. If Slack isn't connected, the Notifications page shows an empty state — "Slack is not connected. Connect Slack to manage notification settings" — with a Connect Slack button that takes you to Settings → Integrations.
You'll need permission to manage Slack channels in your workspace. The Alta Slack app must be invited to any channel you want to route notifications into.
If you haven't connected Slack yet, see How to Connect Your Slack Channel first.

How to find the Notifications settings

Open Settings in the Alta sidebar.
Open Notifications. If Slack is connected, you'll see three Slack channel selectors stacked vertically — one per built-in stream.

The four notification paths

The first three rows are the built-in streams on the Notifications page; each is independent. The fourth (Workflows) lives outside the Notifications page entirely.

1. Prospect replies

"Select Slack channels to receive notifications for prospect replies."

Fires whenever a prospect responds to an outbound message (email or LinkedIn). Best routed to the channel where reps actively work — they want this in real time.

2. Daily plan (Beta)

"Select Slack channels to receive daily plan notifications."

A once-a-day summary of what's queued and where attention is needed. Best routed to a #pipeline / #revenue channel where leadership and ops can see the day's state. This stream is marked Beta in the UI.

3. Manual Task approvals

"Select Slack channels to receive Manual Task approval notifications."

Fires when a campaign step that's gated on a human (Manual Task) is ready for approval. Best routed to whoever owns approving Manual Tasks — typically the campaign owner or a dedicated #task-review channel.

4. Workflows (custom)

The first three streams are fixed — Alta defines what fires them. The fourth path is for everything else: build a Flow (Settings sidebar → Workflows) with any trigger you want — a webhook, a scheduled cadence, a Flows integration event — and add a Slack action that posts a message into a channel of your choice. You can shape the message body with data from earlier steps, post into a different channel per branch, and chain it with other Flow actions.

Reach for Workflows when:

You want a notification on something Alta doesn't natively send — for example, "post in #pipeline whenever a campaign crosses 50 prospects".
You need conditional routing — "post to #revenue-EMEA only if the prospect's region is EMEA".
You want a custom message format beyond what the built-in streams provide.

See How to Build and Manage Flows in Alta for the Flow builder itself.

How to wire a built-in stream to a channel

Open Settings → Notifications.
Click the channel selector for the stream you want to configure (Replies, Daily plan, or Manual Task).
Pick one or more channels from the dropdown — these are the Slack channels Alta is allowed to post into.
If a channel doesn't appear in the picker, invite the Alta Slack app to it from inside Slack: /invite @Alta in the channel, then return to the picker.
Your selection saves automatically.

Tips and common pitfalls

Built-in streams vs Workflows. If a notification you want is in the built-in list (replies, daily plan, Manual Task), use the Notifications page — zero code, instant. Reach for Workflows only when the built-in streams don't cover it.
One stream can go to multiple channels. Useful when (say) you want prospect replies to land in both the rep's regional channel and a leadership #revenue channel.
Replies stream > Daily plan > Manual Task — usually. Reply notifications are time-sensitive (a rep needs to follow up the same hour); the daily plan is a once-a-day digest; Manual Task approvals tend to be batched. Route accordingly.
If a channel is missing, it's almost always an invite issue. Alta only sees public channels the app has been added to, plus private channels where the app has been explicitly invited. This applies to both the Notifications page and the Slack action inside Workflows.
"Slack is not connected"? The Notifications page can't be used until Slack is in a Callable state. Hit Connect Slack on the empty state, complete OAuth, and come back.
Daily plan is Beta. Expect copy and cadence to change — the underlying notification stream is real, but the format is being iterated on.
Workflow Slack notifications need a published Workflow. Building a Flow with a Slack action in Draft state won't send anything until you Publish and toggle the Flow to Active.
Notifications differ by product. If you're on the RevOps product, you'll see slightly different copy on the Notifications page than the Outbound SDR product. The three built-in buckets — replies, daily plan, Manual Task — are the same in both, and Workflows is available regardless.