> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/workflows/notifications.md). # Notifications and follow-up Add notifications where the team needs to act, and add follow-up actions where a prospect needs another way to continue. ## Notify in Slack Connect Slack, then add **Notify in Slack**. Choose the destination and write a message using the data picker. For booking alerts, place it on **Show Scheduler → Booked** and include the guest, host, and meeting time. For unassigned leads, place it on the assignment's **Unassigned** or rulebook's **Else** path. Use the supported mention picker for people and upstream owner references. A display name in plain text is not necessarily a Slack mention. **Create Slack Channel** and **Add Members to Slack Channel** can build a shared workspace around a lead. Use the channel output from the create step and review who should be added. ## Notify by Email Add **Notify by Email**, choose the recipients, and configure the subject and message. Use confirmed meeting details only after Booked. Use prospect details for a lead that did not book. Check the sending setup and recipient addresses with controlled live test data. ## Call a webhook Use **Call Webhook** to send workflow data to another system. Set the URL, method, authentication, and body. Choose secret values through the connection or authentication settings; keep them out of visitor URLs and message text. The step picker also offers presets for tools such as Zapier and analytics services. A preset helps fill the request; you still need to configure its authentication and required data. ## Follow up when no meeting is booked Connect **Show Scheduler → Not booked** to an action your team can act on: * Notify the lead owner or a shared channel. * Create a CRM task using the relevant CRM record step. * Add the lead to a connected sequence or campaign. Sequence actions include Apollo, Amplemarket, Salesloft, Smartlead, Gong Engage, HubSpot, and Outreach where configured. Provider permissions, sender identity, and access to the selected sequence are still required. See [Integration availability](/data-and-integrations/availability.md) for dependencies that may block a step. ## Avoid duplicate messages A workflow can send a message after booking while the event type also sends meeting messages. Review both configurations. Use one owner for each notification you need, and test booking, cancellation, and no-show paths separately. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/workflows/notifications.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.