Send Custom Notifications in Salesforce Using Flow: A No-Code Guide

Users miss things. A high-value opportunity stalls, a case sits untouched for days, an approval request goes unnoticed — not because Salesforce can't surface these moments, but because nobody thinks to look in the right place at the right time.

Custom notifications fix that. They push an alert straight to the Salesforce notification bell (and the mobile app) when something important happens, and the whole thing can be built with clicks in Flow Builder — no Apex required.

What you need before you start

Two building blocks:

1. A Custom Notification Type — created once in Setup (Notification Builder > Custom Notifications). Give it a name, set the channels (desktop, mobile, or both), and finish. This is the "envelope" your flow will use.
2. A Flow — typically a record-triggered flow that decides when the notification fires and who receives it.

Building the flow

Create a record-triggered flow on the object you care about — Opportunity, Case, or whatever matches your use case. Set it to trigger on create or update, then add your entry criteria so it only fires when it matters (for example, an opportunity stage changing to "Negotiation" with an amount over a threshold).

Next, add the Send Custom Notification action element. This is where you wire up the pieces:

• Notification Type — the custom notification type you created in Setup. You'll need its ID (grab it from a Get Records on the CustomNotificationType object, or reference it directly).
• Title and Body — build these with formula resources so the message feels personal: something like "Opportunity {Record.Name} needs attention" with the stage and amount in the body.
• Recipient IDs — a collection variable of user IDs. Use Get Records to find the right people (opportunity owner, team members, managers) and assign their IDs into the collection.
• Target ID — the record the notification should deep-link to, so one click takes the user exactly where they need to act.

A practical example

Say you want managers notified whenever a deal over $50K goes idle for more than 7 days. A scheduled-triggered flow can run daily, query opportunities that match, and send one notification per record to the owner and their manager. The recipient gets a bell notification and a mobile push with the deal name, stage, and a link straight to the record — instead of a forgotten line in a report.

Tips that save you headaches

• Keep the title short. The bell banner shows limited text; put the detail in the body.
• Mind volume. Scheduled flows plus broad criteria can spam people fast. Filter aggressively, and consider batching into a summary message.
• Test as a non-admin. Notification visibility respects sharing; verify the recipient can actually open the target record.
• Use mobile push for the truly urgent. Bell-only notifications are cheap and quiet; save push for escalations.

Custom notifications are one of those small Flow features with outsized impact: five minutes of configuration, and your team stops missing the moments that matter.

---

Originally published at Way2Force