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 hold the workflow: a discount over a threshold waits for the deal desk in a Neblex task, and the link reaches them in Slack
• The decision, the approver, and the timestamp are written back to Salesforce and recorded in the run, so an approval is provable later
• An overdue task escalates: the escalation flow posts to a channel so someone else can pick it up, 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

Started when a Salesforce quote reaches review, with an escalation when the task is overdue.

1. 1
   Trigger: Salesforce New or updated quote, polled on the schedule you set, with a Filter for Status = In Review and Discount__c > 0.20.
2. 2
   Resolve approver: a data table maps the owning rep's region to a deal desk lead's email. Slack Find user by email returns their Slack user.
3. 3
   Request approval: a Wait for form step creates the approval task for the deal desk lead with the account, amount, discount, and a link to the quote, due in 4 working hours.
4. 4
   Notify: a Slack message to the approver carries the summary and a button that opens the task.
5. 5
   Escalate: if the task passes its due time, the escalation flow posts to #deal-desk so another lead can take it.
6. 6
   On approve: a Salesforce update on the quote sets Status = Approved, Approved_By__c to the person who decided, and Approved_At__c to now, and the flow posts the outcome in Slack.
7. 7
   On reject: the quote goes to Rejected with the reason from the task form, and the reason is posted back to the rep in a thread.

The map is Salesforce fields to the approval task and the Slack message, and the task decision 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 create an approval task for a named person and send the link in Slack. (Salesforce to Slack)
• Approval decisions. The decision, the approver, the timestamp, and any reason are written to the record and the run. (Neblex to Salesforce)
• Activity logging. A scheduled flow can read new messages in a deal channel and log them as activities on the opportunity. (Slack to Salesforce)

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

• Run history. Every notification and approval is a run. An approval records the approver, the decision, and the time, so it is provable later.
• Approval steps. The core of this pair: a Wait for form task holds the flow until a named person responds, with a due time and an escalation flow.
• 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.