> For the complete documentation index, see [llms.txt](https://docs.scaleconnect.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleconnect.com.au/scaleconnect-docs/integrations/custom-integrations/slack.md).
# Slack
{% hint style="warning" %}
**Coming soon** — The Slack integration is on our roadmap and not yet available in ScaleConnect. The current notification system delivers alerts through in-app notifications and email. This page describes the planned functionality. Features and workflows may change before release.
{% endhint %}
The Slack integration sends ScaleConnect notifications directly into your Slack workspace — either to a shared channel for team visibility or as direct messages for personal alerts. Instead of switching to ScaleConnect to check what's happening, you see key events where you're already working.
This is especially useful for teams. When an AI Review is completed, a meeting is booked, or a client reaches a milestone, the whole team can see it in a shared channel — keeping everyone aligned without extra meetings or manual updates.
***
## Notification Types
The Slack integration supports notifications for the most important events in ScaleConnect. Each notification type can be individually toggled on or off.
| Notification | What triggers it | What the message contains |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------- |
| **AI Review completed** | An [AI Review](https://github.com/scaleapp-au/scaleconnect-docs/blob/main/integrations/ai-reviews.md) is generated for a client | Client name, review type, key observations summary, link to review |
| **Meeting booked** | A meeting is scheduled via the [Calendar Agent](https://github.com/scaleapp-au/scaleconnect-docs/blob/main/integrations/calendar-agent.md) or calendar panel | Client name, meeting date/time, platform (Meet/Zoom/Teams), link to event |
| **Client milestone reached** | A client hits a goal or milestone in their strategy | Client name, milestone description, goal progress percentage |
| **New client message** | A client sends a message through ScaleApp chat | Client name, message preview, link to conversation |
| **Client connected** | A new client accepts their invitation and creates a ScaleApp account | Client name, email, client type |
| **System alert** | Platform-level events — sync failures, integration errors, subscription changes | Alert type, description, recommended action |
***
## Channel vs Direct Message
You choose where each notification type is delivered — to a Slack channel or as a direct message (DM) to your personal Slack account.
### Channel notifications
Send notifications to a shared Slack channel (e.g. `#scaleconnect-alerts` or `#client-updates`) when you want the whole team to see what's happening. This is ideal for:
* **AI Review completions** — the team sees when reviews are ready, and anyone can pick them up from the Tasks queue
* **Meeting booked** — office managers or support staff can prepare for upcoming client calls
* **Client milestones** — celebrate wins and keep morale up when clients hit goals
* **System alerts** — everyone knows immediately if something needs attention
### Direct messages
Route notifications to your personal DMs when the information is relevant only to you. This works well for:
* **New client messages** — you get a private nudge when a client reaches out, without broadcasting it to the team
* **Meetings you're attending** — reminders about your own upcoming meetings
* **Reviews assigned to you** — notifications about reviews waiting in your personal Tasks queue
### Per-notification routing
Each notification type can be independently routed to a channel, a DM, or both. This lets you set up a configuration like:
| Notification | Channel | DM |
| ------------------- | -------------- | ------- |
| AI Review completed | `#reviews` | — |
| Meeting booked | `#meetings` | Your DM |
| Client milestone | `#wins` | — |
| New client message | — | Your DM |
| Client connected | `#new-clients` | — |
| System alert | `#ops-alerts` | Your DM |
{% hint style="info" %}
If you prefer everything in one place, route all notifications to a single channel. If you want a quiet setup, route only system alerts to your DM and disable the rest.
{% endhint %}
***
## Setup
### Prerequisites
| Requirement | Details |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| **Slack workspace** | An active Slack workspace where you have permission to install apps |
| **Slack admin approval** | Some workspaces require admin approval before third-party apps can be installed. Check with your Slack admin if needed. |
| **ScaleConnect account** | Active broker account with access to Settings → Integrations |
### Connection steps
1. Open **Settings → Integrations** in ScaleConnect.
2. Find the **Slack** card and click **Connect**.
3. You'll be redirected to Slack's OAuth authorisation screen. Select the workspace you want to connect.
4. Review the permissions ScaleConnect is requesting — permission to post messages to channels and send direct messages.
5. Click **Allow** to authorise the connection.
6. Back in ScaleConnect, choose your default notification channel from the dropdown. This lists all public channels in your workspace (and private channels the ScaleConnect bot has been invited to).
7. Select which notification types to enable and where each should be delivered (channel, DM, or both).
8. Click **Test** to send a sample notification to your selected channel or DM. Verify it arrives, then click **Save**.
{% hint style="info" %}
To send notifications to a private Slack channel, first invite the ScaleConnect bot to that channel in Slack (`/invite @ScaleConnect`), then it will appear in the channel dropdown.
{% endhint %}
***
## Message Format
Slack notifications from ScaleConnect use structured message blocks for readability. Each message includes:
* **Header** — the notification type as a bold title (e.g. "AI Review Completed")
* **Client name** — who the notification is about
* **Event details** — specific information relevant to the notification type
* **Summary** — a brief description or key takeaway (for AI Reviews, this includes the top observations)
* **Link back** — a direct URL to the relevant page in ScaleConnect, so you can click through and take action immediately
Messages are compact but informative. They're designed to give you enough context to decide whether you need to act now or can follow up later.
### Example: AI Review notification
> **AI Review Completed** **Client:** Sarah Chen **Type:** Investor — Quarterly Review **Key observations:** Fixed rate expiring in 3 months on 42 Elm St. Portfolio yield trending up. Borrowing capacity increased by $85K since last review. **→ Open in ScaleConnect**
### Example: Meeting booked notification
> **Meeting Booked** **Client:** James Park **Date:** Tuesday 15 April 2026, 2:00 PM AEST **Platform:** Google Meet **Booked by:** Calendar Agent (auto-scheduled from AI Review follow-up) **→ Open in ScaleConnect**
***
## Customising Notifications
### Toggle notification types
From the Slack integration settings page, toggle each notification type on or off independently. Disabled notifications won't generate any Slack messages, even if the underlying event occurs in ScaleConnect.
### Change routing
You can change the channel or DM routing for any notification type at any time. Go to **Settings → Integrations → Slack** and update the delivery preferences. Changes take effect immediately — no need to disconnect and reconnect.
### Quiet hours
If supported by your Slack workspace plan, you can configure Do Not Disturb hours in Slack itself. ScaleConnect notifications sent during quiet hours will be queued by Slack and delivered when DND ends. This is a Slack-side setting, not a ScaleConnect feature.
{% hint style="info" %}
For fine-grained control over which events generate notifications, combine the Slack integration with [Zapier](/scaleconnect-docs/integrations/custom-integrations/zapier.md). Zapier lets you add conditions and filters — for example, only notify about AI Reviews for clients with a portfolio value above a certain threshold.
{% endhint %}
***
## Managing the Integration
### View connection status
The Slack card on the Integrations page shows whether the connection is active, which workspace is connected, and the default notification channel.
### Change channels
To route notifications to a different channel, go to **Settings → Integrations → Slack** and update the channel selection. You can also change individual notification type routing without affecting other settings.
### Disconnect
To remove the Slack integration:
1. Go to **Settings → Integrations** and click the **Slack** card.
2. Click **Disconnect**.
3. Confirm in the dialog. This revokes ScaleConnect's ability to post to your Slack workspace.
Disconnecting stops all Slack notifications immediately. It doesn't delete any messages that were previously sent to Slack — those remain in your channel or DM history.
### Reconnect
If you need to switch to a different Slack workspace or re-authorise after a permissions change, disconnect and follow the setup steps again.
### Multiple workspaces
The initial integration supports one Slack workspace per ScaleConnect account. If your organisation uses multiple Slack workspaces, connect the one where your broking team is most active. Support for multiple workspaces may be added in a future release.
***
## Current Notification Channels
While the Slack integration is in development, ScaleConnect delivers notifications through:
| Channel | How it works |
| ------------------------ | ------------------------------------------------------------------ |
| **In-app notifications** | Badge count and notification panel inside ScaleConnect — always on |
| **Push notifications** | Mobile push via ScaleApp for client messages and meeting reminders |
| **Email** | Email notifications for AI Review completions and system alerts |
The Slack integration will complement these existing channels, not replace them. You'll be able to receive notifications through Slack *and* the existing channels simultaneously.
***
Will Slack notifications replace email notifications?
No. Slack is an additional notification channel, not a replacement. You can use both simultaneously or turn off email notifications separately from your notification preferences in ScaleConnect settings.
Can each team member have their own Slack notification settings?
Yes. Each broker configures their own Slack integration from their personal Settings → Integrations page. One broker might route everything to a shared channel, while another prefers DMs only. Settings are per-user.
Do clients see Slack notifications?
No. Slack notifications are internal — they're sent to your team's Slack workspace only. Clients are never added to your Slack channels and don't see any Slack messages. Client-facing notifications continue through ScaleApp and email.
Can I reply to a client from Slack?
No. Slack notifications are one-directional — they inform you about events but don't support replying back to ScaleConnect. To respond to a client message, click the link in the Slack notification to open the conversation in ScaleConnect.
What happens if the Slack connection breaks?
If the OAuth token expires or your Slack admin revokes the app, notifications will fail silently. ScaleConnect will show a warning on the integration card in Settings. Reconnect by clicking the Slack card and re-authorising.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.scaleconnect.com.au/scaleconnect-docs/integrations/custom-integrations/slack.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 `automate deployments from our CI pipeline` 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.