Scribd
Upload
85 views1 page

Custom Notification Actions in Salesforce

This document summarizes custom notification actions that allow sending custom notifications via desktop or mobile channels. It requires creating a notification type first. The action can be triggered in flows running in system context without permission, but requires the "Send Custom Notifications" permission when running in user context or via the API. It supports GET, HEAD, and POST HTTP methods and requires the custom notification type ID and recipient ID/type as input parameters.

Uploaded by

Alejo1895
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
85 views1 page

Custom Notification Actions in Salesforce

This document summarizes custom notification actions that allow sending custom notifications via desktop or mobile channels. It requires creating a notification type first. The action can be triggered in flows running in system context without permission, but requires the "Send Custom Notifications" permission when running in user context or via the API. It supports GET, HEAD, and POST HTTP methods and requires the custom notification type ID and recipient ID/type as input parameters.

Uploaded by

Alejo1895
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Action Objects Custom Notification Actions

Custom Notification Actions


Send custom notifications to recipients via desktop or mobile channels.
Before you send a custom notification, you must first create a notification type.

Important: In orgs created in Winter ’21 or later, the Send Custom Notifications user permission is required to trigger the Send
Custom Notification action in flows that run in user context, REST API calls, and Apex callouts.
The Send Custom Notifications user permission isn’t required to trigger the Send Custom Notification action in processes or flows
that run in system context.

This object is available in API version 46.0 and later.

Supported REST HTTP Methods


URI
/services/data/vXX.X/actions/standard/customNotificationAction
Formats
JSON, XML
HTTP Methods
GET, HEAD, POST
Authentication
Authorization: Bearer token

Inputs
Input Details
customNotifTypeId Type
reference
Description
Required. The ID of the Custom Notification Type being used for the notification.

recipientIds Type
reference
Description
Required. The ID of the recipient or recipient type of the notification. Valid recipient or recipient
type values are:
• UserId — The notification will be sent to this user, if this user is active.
• AccountId — The notification will be sent to all active users who are members of this
account’s Account Team.

Note: This recipient type is valid if account teams are enabled for your org.

• OpportunityId — The notification will be sent to all active users who are members of
this opportunity’s Opportunity Team.

You might also like