You are here:
Send Custom Notification Action
Send a custom notification to users when a specific event occurs. Custom notifications appear in the notification bell and can be delivered to the Salesforce desktop or mobile app.
Required Editions
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To view notification types: | View Setup and Configuration |
| To create and edit notification types: | Customize Application |
| To send custom notifications: | Send Custom Notifications |
| To open, edit, create, activate or deactivate a flow using all flow types, elements, and features available in Flow Builder, including Einstein and Agentforce for Flow: | Manage Flow |
In Flow Builder, add an Action element to your flow. In the Action field, enter Notifications, and select Send Custom Notification.
To see an example of a flow that sends a custom notification, see Send a Custom Notification With a Flow.
The Send Custom Notifications user permission is enforced in orgs created in Winter ’21 or later.
- Before you begin, make sure that the custom notification type you want to call from your flow exists. If not, create the notification type.
- To query for the Notification Type ID directly from a flow, add the Get Record element to your flow and filter by API name. If you’ve installed a notification type via a managed package, filter by the namespace prefix and the API name.
- To add recipients, define recipient IDs as a text collection variable. Then add values to your recipient IDs collection by using the Assignment element in your flow.
Set Input Values
Use values from earlier in the flow to set the inputs for the notification. Specify at least one recipient for the notification.
| Field | Description |
|---|---|
| Custom Notification Type ID | The ID of the Custom Notification Type being used for the notification. To use, add a Get Records element to get the DeveloperName of the custom notification type to use. Then, select the record ID that the Get Records finds. This parameter accepts single-value resources of any type. That value is treated as text. |
| Notification Body | The body of the notification that recipients see. Enter text, or select a resource with text in it. For example, create a text template resource. The content of mobile push notifications depends on the Display full content push notifications setting. This parameter accepts single-value resources of any type. That value is treated as text and is limited to 750 characters. |
| Notification Title | The title of the notification as seen by recipients. Enter text, or select a resource with text in it. For example, create a text template resource. This parameter accepts single-value resources of any type. That value is treated as text and is limited to 250 characters. |
| Recipient IDs | A text collection variable with one or more IDs in it. To use, create a collection variable of type Text. Then use an Assignment element to add IDs to the collection. Select the collection for this input's value. This parameter accepts collection variables of type Text and is limited to 500 values. The values that you enter for an individual Send Custom Notification action can represent a total of up to 10,000 users as recipients. |
| Target ID | Optional. The record ID of the record that the user is navigated to if they click the notification. This parameter accepts single-value resources of any type. That value is treated as text. |
| Target Page Reference | Optional. The string that defines the pageReference type of the page where a user is navigated to if they click the notification. This parameter accepts single-value resources of any type. That value is treated as text. For example, to be redirected to the list view of recent account records, enter this:
To see how to specify the target by using JSON, see pageReference. |
| Sender ID | Optional. The user ID of the sender of the notification. This parameter accepts single-value resources of any type. That value is treated as text. |
Usage
- Each notification can have up to 10,000 users as recipients. However, you can edit an
action to the same process within Process Builder or to the same flow in Flow Builder to
have more recipients.Important Support and updates for Process Builder are scheduled to end as of December 31, 2025. See Workflow Rules & Process Builder End of Support.
After December 31, 2025, you can continue to activate, deactivate, and edit any existing processes. To migrate existing processes, plan your switch to Flow Builder and use the Migrate to Flow tool. For new automations, create flows in Flow Builder.
- Your org saves your most recent 1 million custom notifications for view in notification trays. Your org can save up to 1.2 million custom notifications, but it trims the amount to the most recent 1 million notifications when you reach the 1.2 million limit.
-
An org can send up to 10,000 notification actions per hour. When you exceed this limit, no more notifications are sent in that hour, and all unsent notifications are lost. Notification actions resume in the next hour.
For example, your notification action processes are triggered 10,250 times between 4:00 and 4:59. Salesforce run the first 10,000 of those actions. The remaining 250 notifications aren’t sent and are lost. Salesforce begins running notification actions again at 5:00.
