Skip to main content
Connect a Slack workspace and a playbook can post to it: a channel, a DM to the account’s CSM, or a channel named on the account itself. The message is built from blocks and filled in per account when the step runs.

Connecting

Go to Settings → Connections, add a connection and pick Slack. Continuing takes you to Slack, where you choose the workspace and approve the permissions — Zudo never asks you for a token. Slack sends you back and the connection appears with your channel list already loaded. Start and finish in the same browser. The link Zudo hands Slack is good for ten minutes and is tied to the person and organization who started it, so a link that has sat in a tab overnight, or one opened in a different organization, is refused and you start again from Connections. Adding an app to a Slack workspace may need an admin, depending on how that workspace is set up.

What Zudo asks for, and why

Zudo does not read messages. It only posts.

Posting from a playbook

Add a Post to Slack step to a playbook. It has two parts: where it goes, and what it says.

Where it goes

What it says

The message is a list of blocks you stack in order: Every text field takes inserted values: type {{ and pick one, and it is filled in per account when the step runs.
Values are read at the moment the step posts. A step that waits two weeks before posting sends the MRR as it is two weeks from now, not as it was when the account enrolled.

Testing it

The Slack connection has a Send a test message button, which posts to a channel you pick. That is the way to check a workspace is working without switching a playbook on and waiting for a check. The connection also has a Refresh channels button. Zudo reads your channel list when you connect, so a channel created later will not be in the picker until you refresh.

What happens when something goes wrong

A step that cannot post says why on its own counter in the playbook, and the reason is in the run’s log under Accounts.

What is not here yet

  • Health tier drops, completed requests and alerts do not post to Slack on their own. Slack is a playbook destination, so anything that reaches it does so because a playbook sends it
  • Zudo does not read or reply to Slack messages, and there is no Zudo app inside Slack
  • One workspace per organization. Connecting a second Slack replaces nothing, but the Add Connection screen offers Slack only while none is connected