--- schema_version: "1" id: 3ba986711dcfbbb7a24bd420779d72211444f6b0a6b479426c419b71bb137324 title: Send Custom Notification Action collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_ref_elements_actions_sendcustomnotification.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_actions_sendcustomnotification.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 4088d36b539698d3330d0d3c76950bf12dcf985ff0ad8203024985c9dd2c899d description: 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. products: - Flow Builder - Salesforce Platform release: "264" --- # 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

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](https://help.salesforce.com/s/articleView?id=platform.automate_flow_build_example_send_custom_notification.htm&release=264.0.0&type=5 "Create a flow that sends 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."). ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png) Important The Send Custom Notifications user permission is enforced in orgs created in Winter ’21 or later. ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_tip.png) Tip - Before you begin, make sure that the custom notification type you want to call from your flow exists. If not, [create the notification type](https://help.salesforce.com/s/articleView?id=platform.notif_builder_custom_type.htm&language=en_US). - 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: `"{"type": "standard__objectPage","attributes": {"objectApiName": "Account","actionName": "list"},"state":{"filterName":"Recent"}}"` 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png) Important Support and updates for Process Builder are scheduled to end as of December 31, 2025. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US). 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](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules."). - 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. #### See Also - [Create and Send Custom Desktop or Mobile Notifications](https://help.salesforce.com/s/articleView?id=platform.notif_builder_custom.htm&language=en_US) - [Flow Run Context](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_context.htm&release=264.0.0&type=5 "Flows run in user context or system context. For a flow running in user context, the running user’s profile and permission sets determine the object permissions and field-level access of the flow. For a flow that runs in system context, whether it runs with or without sharing determines its data access. Understanding context helps you control what your flows can read and update on behalf of your users.") - [Flow Elements](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements.htm&release=264.0.0&type=5 "An element represents an action that the flow can run. Examples include reading or writing Salesforce data, displaying information and collecting data from flow users, runnning business logic, or manipulating data.") - [Add and Edit Elements](https://help.salesforce.com/s/articleView?id=platform.flow_build_elements.htm&release=264.0.0&type=5 "Use elements to define actions that the flow can run. When they’re on the canvas, connect them to create the order in which they run.") - [Customize What Happens When a Flow Fails](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault.htm&release=264.0.0&type=5 "Learn how fault paths customize what happens when a flow fails. Choose how to notify admins, guide users, and take a follow-up action.") - [Move and Connect Elements to Change a Flow Route](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_route_add.htm&release=264.0.0&type=5 "Identify which elements the flow runs and in what order by connecting the elements on your canvas together. To change the run order, move elements and add or remove connectors.")