You are here:
Send Notification Action
Call a notification type to send. Each Send Notification action corresponds to a supported notification type. Send Notification actions are available only for Slack-enabled custom notification types and certain Slack-enabled standard notification types.
Required Editions
To send notifications for Slack, enable Salesforce for Slack Integrations.
To create a custom Slack notification type supported by a Send Notification action, see Create and Send Custom Slack Notifications.
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To trigger a Send Notification action in flows that run in user context and REST API calls: | Send Custom Notifications |
Add an Action element to the flow. In the Action field, select the Send Notification-supported notification type that you want to configure. Each Send Notification action corresponds to a supported notification type. For example, if you created a custom notification type named My Opportunity Notification, look for the My Opportunity Notification action in the Notifications category.
Set Input Values
Use values from earlier in the flow to set the inputs for the notification type.
| Field | Description |
|---|---|
| Recipient IDs | Required. The IDs of the notification recipients or recipient types. The value must be a collection variable that represents one or more Salesforce User IDs or Collaboration Room IDs. Some Salesforce features link standard objects to Collaboration Room through the Swarm object. For these features, you can find an existing Collaboration Room ID from the Swarm object. The collection variable’s Data Type must be Text. The collection can have up to 500 values. |
| Record ID | Required. The ID of the record that the notifications are about. The record ID must be an ID from the Salesforce object related to the notification type. For example, enter the record ID for an opportunity when configuring a notification type associated with the Opportunity object. For custom notification types, you can find the related object by viewing the notification type's settings from Custom Notifications in Setup. For supported standard notification types, refer to the Standard Notification Types and Related Objects table. Enter a record ID or select a variable that identifies the record. This parameter accepts single-value resources of any type. That value is treated as text. |
Standard Notification Types and Related Objects
Use this table to identify which object applies to each standard notification type that’s supported by a Send Notification action. The object determines the value that you enter for Record Id.
| Standard Notification Type | Related Salesforce Object |
|---|---|
| Amount Updated | Opportunity |
| Close Date Reminder | Opportunity |
| Close Date Updated | Opportunity |
| Deal Won | Opportunity |
| Deals to Watch | Opportunity |
| High Priority Case | Case |
| New Allergy Intolerance | Allergy Intolerance |
| New Child Opportunity | Opportunity |
| New Care Determinant | Care Determinant |
| New Health Condition | Health Condition |
| New or Updated Care Plan Task | Task |
| Next Step Reminder | Opportunity |
| Stage Reminder | Opportunity |
| Stage Updated | Opportunity |
| Updated Care Plan | Case |
Usage
- Each notification can have up to 10,000 users as recipients. However, you can add another action to the same flow in Flow Builder to have more recipients.
- You can save up to 1.2 million custom notifications, but notification trays show only your most recent 1 million custom notifications.
- You can execute 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.
- The sending rates of Slack notifications are also subject to the limits of the Slack service.
