# Know the moment a Salesforce deploy lands. > The SyncOnAI 360 Slack connector posts the result of each Salesforce deploy to a Slack channel through an incoming webhook you create in your own Slack workspace. It sends notifications only: it is not a chat bot, it reads nothing from Slack, and removing the webhook in Slack or disconnecting it in SyncOnAI 360 stops it immediately. Source: https://synconai360.com/connectors/slack ## Key facts - **1**: Webhook, created in your own Slack - **0**: Messages read from Slack - **Every**: Deploy result posted - **Any time**: Remove it from Slack or the workspace ## Why teams miss Salesforce deploy results A deploy finishes in one tool while the team works in another. Failures are found when a user reports them, and successes are announced by hand, if at all. - **Results nobody sees.** A failed deploy waits in a tool nobody has open until someone asks why a change is missing. - **Manual announcements.** Someone has to remember to tell the channel what went to production. - **Broad bot permissions.** Chat integrations often ask to read channels when all that is needed is a message. - **Hard to switch off.** Noisy integrations linger because nobody knows who set them up. ## What does SyncOnAI 360 post to Slack? The result of each deploy: which org it went to, what changed, whether it succeeded, how many components were deployed, and who requested it; a failure carries Salesforce's reason. The message is posted as soon as the deploy finishes, so the channel learns about a failure at the same time as the person who started it. Slack receives deploy results only. Scan summaries and agent completions are not posted, which keeps the channel to the events that change an org. - Org, change and outcome - Posted as the deploy finishes - Deploy results only ## Why does the Slack connector use a webhook? An incoming webhook is created by you, in your own Slack workspace, for one channel. It can post to that channel and do nothing else: it cannot read messages, list channels or see members. You can remove it from Slack at any time without involving us, and disconnecting it in SyncOnAI 360 stops posting immediately. The webhook address is stored encrypted and is not shown in full after saving. - Created and owned by you - Post-only, one channel - Remove it from either side ## How do you connect Slack to SyncOnAI 360? Create an incoming webhook in Slack for the channel you want, then paste its address under Integrations, Slack in SyncOnAI 360. An admin sets this up once for the workspace. Test with a small sandbox deploy and the result appears in the channel. The integration page shows when it last posted and whether that worked, so a broken webhook is noticed rather than assumed to be fine. - Paste one webhook address - Set up once by an admin - Last delivery shown ## How do Slack messages fit the deploy record? The Slack message is a heads-up. The record is the deploy receipt in SyncOnAI 360: what changed, the request behind it, the checks it passed, who approved it and when, with rollback to the version recorded before it. When a deploy fails, Salesforce's reason is shown on the deploy and Fix in chat opens the conversation with the error, so the person who sees the Slack message can go straight to the fix. - Slack for awareness - Receipts for the record - Straight to the fix ## Which Salesforce deploys are posted to Slack? Every deploy that runs through SyncOnAI 360, to a sandbox or to production, posts its result, so the channel shows the whole flow of change rather than only releases. A success says how many components were deployed, and a result of zero components is reported rather than hidden behind a generic success line. A failure carries Salesforce's own reason, cut to a readable length, and names who requested the deploy, so the right person can pick it up straight away. - Sandbox and production deploys - Component counts, zero included - Failures with reason and requester ## Which Slack channel should receive deploy results? A workspace posts to one channel, the one its webhook belongs to. Choose the channel where the people who act on failures already are, usually the delivery or release channel, rather than a busy general one. Pair it with the activity log in SyncOnAI 360 for the full history: Slack shows what just happened, and the log and the receipts keep the record. - One channel per workspace - Where failures get acted on - Receipts keep the record ## Connecting Slack 1. **Create a webhook.** In Slack, for the channel you choose. 2. **Paste it.** Under Integrations, Slack, in SyncOnAI 360. 3. **Deploy.** Try a small sandbox deploy. 4. **Watch.** Every deploy result appears in the channel. ## Deploy results, missed versus posted | Without | With SyncOnAI 360 | |---|---| | Failures found by users | Failures posted as they happen | | Production changes announced by hand | Every deploy result posted | | Bots that read your channels | A post-only webhook you own | | Integrations nobody can switch off | Remove it from Slack or the workspace | ## Who watches the channel - **Release managers.** See every deploy result as it happens, and go to the receipt for the detail. - **Salesforce admins.** Know when a change reached production without opening another tool. - **Managed services teams.** Watch deploys across client orgs in one channel per client or one for the whole team. - **Delivery managers.** Hear about failures in time to adjust the plan rather than the next morning. ## Frequently asked questions ### What does SyncOnAI 360 post to Slack? Deploy results: the org, the change and whether it succeeded or failed. ### Is it a Slack bot? No. It is notifications only, through an incoming webhook. It does not read messages or respond to commands. ### Does it post audit results? Not today. Slack receives deploy results only. ### Can we choose the channel? Yes. The webhook you create in Slack decides the channel. ### Can it read our Slack workspace? No. An incoming webhook can post to its channel and nothing else. ### Who can set it up? A workspace admin, once for the workspace. ### How do we turn it off? Disconnect it in SyncOnAI 360, or remove the webhook in Slack. Either stops posting immediately. ### Is Slack on every plan? Yes. Every plan includes every feature. ### Are sandbox deploys posted? Yes. Every deploy that runs through SyncOnAI 360 posts its result, sandbox or production. ### Can we post to more than one channel? Not today. A workspace posts to the one channel its webhook belongs to. ### Is the webhook address kept secret? It is stored encrypted and not shown in full after saving. Anyone holding a webhook address can post to its channel, so treat it like a password.