Loading
Salesforce now sends email only from verified domains. Read More
Help Agent Performance DegradationRead More
Automate Your Business Processes
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Considerations for Processes that Send Custom Notifications

          Considerations for Processes that Send Custom Notifications

          Before you begin sending custom notifications, learn about important storage, recipient, and org limits.

          Required Editions

          Available in: both Salesforce Classic and Lightning Experience
          Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions
          User Permissions Needed
          To create, edit, or view processes:

          Manage Flow

          AND

          View All Data

          Important
          Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See Workflow Rules & Process Builder End of Support.

          After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. 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.

          • You can create up to 500 custom notification types.
          • Each notification can have up to 10,000 users as recipients. However, you can add an action to the same process within Process Builder or to the same flow in Flow Builder to have more recipients.
          • 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 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.

            For example, your notification action processes are triggered 10,250 times between 4:00 and 4:59. Salesforce executes the first 10,000 of those actions. The remaining 250 notifications aren’t sent and are lost. Salesforce begins executing notification actions again at 5:00.

          • When you send a custom notification from a process, the Target ID for the notification is the record that started the process. However, target records that don't have their own detail page (for example, a case comment, which appears only in a Case Comment related list) don't support direct navigation. Use Flow Builder to send the notification from a flow and specify either a different Target ID or Target Page Reference.
            Tip
            Tip To see how to specify the target using JSON, see pageReference.
          • Custom notification title and body fields support plain text only.
          • The content of custom push notifications depends on the Display full content push notifications setting. If full content push notifications aren’t enabled, only the notification title is sent.
           
          Loading
          Salesforce Help | Article