Slack messaging

Connect Slack once, and both your automated journeys and the assistant can post updates to the channels your team already works in — a heads-up when a contact needs attention, a link to a blog post that just went live, or a short report of how a send performed. The messages arrive as native Slack messages, formatted for readability, with buttons that link straight back into the app.

This is for posting to your team's own channels. It does not message your contacts — journeys still reach contacts by email and text.

Connecting Slack

1. Go to Settings → Integrations → Messaging.
2. Select Add to Slack. You'll be taken to Slack to choose the workspace and approve the permissions the app needs to post to channels.
3. After you approve, Slack sends you back to the app and the connection shows as Connected, along with the workspace name.
4. Pick a default channel — the one used when a journey or the assistant posts without naming a specific channel. You can always choose a different channel per message.
5. Confirm it works by asking the assistant to post a quick test message to a channel (see below) — it lands as a normal Slack message you can see.

Only someone who can install apps in your Slack workspace can complete the connect step. If your workspace requires an admin to approve new apps, Slack will guide that person through it during step 2.

Your Slack credentials are stored encrypted and never leave the service that talks to Slack — the app only keeps the workspace name and your channel choices.

Using Slack in a journey

On a Notify team action in the journey builder, Slack appears alongside email and in-app as a channel, once it is connected:

1. Add or open a Notify team action.
2. Tick Slack in the channels list.
3. Choose the Slack channel to post to.
4. Write the subject and body as usual. Merge fields like the contact's first name work the same way they do for email and in-app notifications.

The channels list offers only what is connected, so Slack is missing from it until you connect it. If neither Slack nor Microsoft Teams is connected, the list shows a greyed-out Slack or Microsoft Teams option instead, with a link to Settings → Integrations → Messaging. Journeys you set up with Slack before Teams was available keep posting to the Slack channel they were set up with.

When the journey runs, each matching contact triggers a Slack post to the channel you chose. Every post links back to both the journey it came from and the contact it is about (and the campaign, when the journey belongs to one), so a teammate can open either record in one click. Journeys run on their own, with no one present — if Slack is disconnected when the journey fires, that step is quietly skipped and recorded, and the rest of the journey continues; it never stops the journey.

Using Slack with the assistant

Ask the assistant to post to a channel in plain language, for example:

• "Post to the #marketing Slack channel that the Q3 launch blog post is ready, and link it."
• "Let the team know in Slack that the June newsletter just went out."

The assistant builds the message, attaches a working link to whatever it's referring to — an artifact, a contact, an automation, or a campaign — and shows you the message for approval before it posts. Nothing is sent to Slack until you approve it.

You can also just ask which channels it can post to — "what Slack channels can you post to?" — and it lists the channels the app has access to, marking the default one. Use that if you are not sure of a channel's exact name, or to check the app was added to the channel you had in mind.

The assistant can also read a channel to use as background when it creates something. For example: "Read our #product-feedback channel and draft a customer-proof snippet from what people said." It pulls the recent messages from the channel you name and grounds its draft in them.

Disconnecting

Remove the connection any time from Settings → Integrations → Messaging with Disconnect. This deletes the stored Slack credentials from our side, so the app stops posting to Slack immediately. It does not remove the app from your Slack workspace: it stays installed there until you remove it in Slack, and the card says so once the connection is removed. Journeys that used Slack simply skip that channel afterward (the rest of each journey still runs) until you reconnect. Reconnecting starts a fresh Add to Slack approval.

Good to know

• One workspace per account. Connect a single Slack workspace; posting targets the channels in that workspace.
• Approval on sends. Every message the assistant posts is shown to you first.
• Links open the app. The buttons in a Slack message open the login-gated app, so only your team can follow them to the record.
• Artifact links open where they were made. A link to something the assistant created — a blog post, an image, a file — opens the chat conversation (or the automation run, for a journey-created item) it came from, not a separate page for that item on its own.

What's coming later

This first release covers posting to and reading Slack channels. These are planned for a later release and are not available yet:

• Uploading files directly into a Teams channel. Microsoft Teams itself is available now (see Microsoft Teams messaging), but files can't be uploaded into it yet.
• Acting on messages inside Slack — buttons you can click and slash commands in the channel, plus a bot you can talk to in-channel (today the assistant lives in the app, and Slack is post-and-read only).
• Slack and Teams marketplace listings — for now you connect with Add to Slack from Settings rather than installing from an app marketplace.
• Connecting more than one workspace — a single workspace per account for now.