Create Notification Actions in Flow

This process is less intuitive than you would hope. The following steps need to be completed in this order. Reference the screenshots that follow the instructions, below, that show a practical example where a notification is sent every time a contact is created or has an email updated.

  1. Set up a custom notification via Setup > Quick Find > “notification” > Custom Notifications. Note the API Name, in the example below it is Contact_Notification.
  2. Set up a new record-triggered flow using the Flow Builder in setup.
  3. In the new Flow, set up entry conditions such that the flow fires in all the situations where a notification should be issued. In the example below it is when Contacts are newly created, ISNEW(), or when the email is changed, ISCHANGED({!Record.Email}).
  4. The Custom Notification Type ID in later steps requires the record ID for the custom notification set up in step 1. Avoid hard-coding the actual record ID, and instead query the Custom Notification Type object for the API Name noted in step 1 (using the DeveloperName field in the Flow). In the example below it is Contact_Notification.
  5. The recipient IDs in later steps requires a text collection. It does not accepts a record collection (“sObject” collection). Add a new resource called RecipientIDs with data type Text to the Flow. In the example below, I include a single User ID, the owner of the new Contact. Up to 500 record IDs can be included, and IDs for queues as well as users can be added.
  6. Add an assignment called “Add Recipients” or similar to the flow to populate the RecipientIDs collection. The example below adds the owner of the new Contact.
  7. If logic based on whether the record ISNEW or ISCHANGED is needed, a formula resource can be added to the flow based on the ISNEW() function that each flow has.
  8. Set up a Decision to change the notification text, as required.
  9. Depending on the nature of the notification, setting up one or more formula resources like those shown below can be helpful to gracefully handle blank values. Example logic: BLANKVALUE({!$Record__Prior.Email}, 'No Email').
  10. Set up the actual custom notifications using the Custom Notification Type IDs and RecipientIDs from previous steps.

Worked Example

Step 1:

Step 3:

Step 4:

Step 5:

Step 6:

Step 7:

Step 8:s

Step 9:

Step 10: