There are almost endless use cases for why you might want to get notified in Slack when something happens in Salesforce.
.avif)
There are almost endless use cases for why you might want to get notified in Slack when something happens in Salesforce. Some examples off the top of my head are:
For the purposes of this demo, we’re going to take a real-life scenario. When someone comes to our website and sends us a message via the Contact Us form, we want to notify everyone in Slack so that we can follow up as soon as possible.
Here’s how you’d achieve that in Salesforce - no joke - in ten minutes or less. I’ll start my stopwatch!
First of all, we need somewhere to post those alerts to. If you have an existing channel in Slack, you can skip this step. Otherwise, log in to your Slack workspace and complete the following steps:

Creating a new Slack channel
Now that you have your shiny new channel, you want to set up an email integration so that data can be emailed to it. To do this:

Creating a new email integration in Slack
Let’s head back into Salesforce and create an email template.
It doesn’t matter whether you create a Classic or Lightning template and whether it’s HTML or plain text, so long as it contains the information you want to be able to see in Slack.
Make sure you make it available for use. Below is a screenshot of my alert template.

This is more or less what your template should look like
The next step is to set up the email alert itself. This is the action that references the template we just created and which we will later associate with an automation tool like workflow rule or process builder.

This is how your edit screen should look after adding in the Slack email address

Once saved, your workflow rule will look something like this
Now that we have our Slack integration, our email template and our email alert, we can put the final step in place, which is building the automation that actually pings the email address.
I’m going to be using Workflow rule, since it’s a little quicker and easier to demo, however this works just as well in Process Builder, Flow or other tools.

Here’s how mine ended up looking
You’re now ready to start testing. Let’s see what happens when I submit the Contact Us form on the website now…

SUCCESS!
Hopefully you’ve been successful, but if not, here are a few common issues and their solution:
My email is corrupted or looks strange
Check your email template for errors and try sending it to a regular email address to see how it renders. If you are using HTML, there is most likely a formatting issue or a broken tag somewhere.
I don’t get a notification in Slack at all
Add another recipient’s email to your email alert so that you can tell if the issue is that the automation isn’t firing or if there’s some issue with the data getting into Slack. If the other email address successfully receives the email, but Slack doesn’t, try double-checking your email integration. Is it set up correctly and firing to the right channel? If so, check your email alert and make sure you’ve entered the Slack email address correctly.
I don’t get a notification in Slack AND additional emails I added didn’t get the email either
In this case, it’s likely that either your forgot to active your workflow rule/process builder (it happens!) or else the criteria it’s supposed to fire under are not met. On records where you expected the rule to fire, go through each criteria to check whether it is met for the record in question. If not, there’s your culprit!
Now that everything is working as planned, give yourself a pat on the back and enjoy the fruits of your labour!
If you have any questions or are looking for help with your Salesforce instance, feel free to contact us with the Contact Us form - we’ll be notified immediately ;)
Candybox Team
RevOps, Salesforce & HubSpot experts
Candybox designs and runs the Salesforce, HubSpot and AI systems behind fast-growing B2B SaaS companies.
Straight answers to what B2B SaaS teams ask us most. Don't see yours? Just ask us.
As SaaS companies grow, disconnected tools and teams create data gaps, forecasting issues, and misaligned incentives. RevOps solves this by centralizing GTM operations, ensuring teams share the same metrics, and creating scalable processes that support predictable growth.
Most startups benefit from RevOps as early as Series A, when multiple tools and messy handoffs start creating inefficiencies. Signs it’s time include unreliable forecasts, unclear funnel conversion, poor customer experience at handoffs, and leadership needing trustworthy dashboards.
Sales Ops focuses on sales team processes and CRM upkeep.
Marketing Ops manages martech and the marketing-to-sales handoff.
RevOps spans the entire GTM lifecycle, integrating sales, marketing, and customer success with shared processes, tools, and KPIs.
Most of our clients are B2B SaaS companies - often between 50–500 employees - with fast-moving GTM teams and a need for clean, connected systems. We're especially strong with companies using Salesforce, HubSpot, Stripe, and product-led GTM motions.
RevOps, short for Revenue Operations, is the alignment of sales, marketing, and customer success under a unified strategy. It focuses on people, processes, platforms, and data to reduce silos, improve forecasting, and accelerate growth in SaaS businesses.
Primarily Salesforce and HubSpot. Our tools and processes are built to work natively with both, and we’ve handled orgs running both systems simultaneously.
Yes. We don't just hand you a Notion doc and walk away. We blend RevOps strategy with hands-on systems execution - so we’ll help you define the right logic, then build it directly in Salesforce or HubSpot (or both), end-to-end.