Connect Salesforce to Slack

Reps and managers live in Slack. The deal data lives in Salesforce. The usual result is a bot that posts every field change as noise, or an approval that happens over DM with no record. Neither scales, and neither is auditable.

• Alerts are selective and contextual: a closed-won post carries the amount, product, and a link, and threads the onboarding checklist underneath
• Approvals pause the workflow: a discount over a threshold waits for the deal desk, and the run does not continue until someone acts
• The decision, the approver's Slack user, and the timestamp are written back to Salesforce and recorded in the run log, so an approval is provable later
• A timeout escalates: no response in the window re-posts to a channel and re-assigns, rather than the deal silently stalling

The approval flow most revenue teams turn on first.

A quote over 20 percent discount waits for the deal desk before it is sent

Triggered when a Salesforce quote reaches pending approval, with a timeout escalation.

1. 1Trigger: Salesforce New or updated record on Quote where Status = In Review and Discount__c > 0.20.
2. 2Resolve approver: a data table maps the owning rep's region to a deal desk lead's email. Slack Get user by that email returns the Slack user ID.
3. 3Request approval: Slack posts a Block Kit message to that user with the account, amount, discount, a link to the quote, and Approve and Reject buttons. The run pauses.
4. 4Timeout: no response in 4 working hours re-posts to #deal-desk and re-assigns the decision.
5. 5On approve: Salesforce Update record on the quote sets Status = Approved, Approved_By__c to the deal desk lead, and Approved_At__c to now. The original Slack message is edited to show the outcome.
6. 6On reject: the quote goes to Rejected, a follow-up modal captures the reason, and it is posted back to the rep in a thread.

Slack has no record model, so the map is Salesforce fields to the Block Kit message, and the interaction payload back to Salesforce.

• Deal alerts. Closed-won, stage regressions, large new opportunities, and stalled deals post to the relevant channel with the record context. (Salesforce to Slack)
• Approval requests. Discounts, non-standard terms, and credit holds post an approval card to a named person and pause the workflow. (Salesforce to Slack)
• Approval decisions. The approve or reject action, the approver, the timestamp, and any reason are written to the record and the run log. (Slack to Salesforce)
• Quick updates. An emoji reaction or a slash command on a deal alert can log an activity or advance a stage, without opening Salesforce. (Slack to Salesforce)

The same controls apply to this sync as to every other Neblex workload.

• Ordered run log. Every notification and approval is an event log. An approval records the approver's user ID, the decision, and the time, so it is provable later.
• Approval steps. The core feature of this pair: a flow pauses in Slack until a named person responds or a timeout escalates.
• Scoped access. Slack uses OAuth scopes limited to the channels and actions the flows use. Salesforce uses a permission set limited to the objects that are read and written.
• Environments. Build against a Slack test workspace and a Salesforce sandbox, then promote the same flow to production.