--- schema_version: "1" id: 76f336897171961aef476f4dde7972ea3042dbbd3f57230d843a1d7bf0875563 title: Configure the Process Trigger collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_start.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_start.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 59ba2b6557817c1986bee201bd24d41577c1f1f5a692686cd60dbf235944e8fb description: Every process includes a trigger, which tells the process when to start. How you configure that trigger depends on what type of process you’re creating. products: - Flow Builder - Salesforce Platform release: "264" --- # Configure the Process Trigger Every process includes a trigger, which tells the process when to start. How you configure that trigger depends on what type of process you’re creating. ### Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience

Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions

Event processes are available in: Performance, Unlimited, Enterprise, and Developer Editions

User Permissions Needed
To create, edit, or view processes:

Manage Flow

AND

View All Data
![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 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](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US). 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](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."). - **[Record Change](https://help.salesforce.com/s/articleView?id=platform.process_start.htm&release=264.0.0&type=5)** If the process starts when a record changes, associate the process with an object, and specify when to start the process. - **[Event](https://help.salesforce.com/s/articleView?id=platform.process_start.htm&release=264.0.0&type=5)** If the process starts when a platform event message is received, associate the process with a platform event and an object, and specify matching conditions. Because every process acts on a Salesforce record, it requires a single record as a starting point. That way, the criteria and actions know where to start evaluating and executing. - **[Invocable](https://help.salesforce.com/s/articleView?id=platform.process_start.htm&release=264.0.0&type=5)** If the process starts when another process invokes it, associate the process with an object. ## Record Change If the process starts when a record changes, associate the process with an object, and specify when to start the process. 1. Click **Add Object**. 2. Configure the trigger.
For this field ... Select ...
Object The object that you want to base this process on. Click Find an object. Type to filter the dropdown list.
Start the process

Which type of record change triggers the process.

  • only when a record is created
  • when a record is created or edited

If you're familiar with workflow rules and you're wondering what happened to the third option (created, and anytime it's edited to subsequently meet criteria), don't worry! You see that setting when you add criteria nodes if you selected when a record is created or edited.
Recursion - Allow process to evaluate a record multiple times in a single save operation?

Yes, if you want the process to evaluate a record multiple times in a single save operation. To see this field, expand the Advanced area.

When enabled, the process can evaluate the same record up to five more times in a single save operation. It reevaluates the record because a process, workflow rule, or flow updated the record in the same save operation. For more information, see Reevaluate Records in the Process Builder.
3. Before saving your changes, confirm the selection because you can’t change the object after you save it. ## Event If the process starts when a platform event message is received, associate the process with a platform event and an object, and specify matching conditions. Because every process acts on a Salesforce record, it requires a single record as a starting point. That way, the criteria and actions know where to start evaluating and executing. 1. Click **Add Trigger**. 2. Configure the trigger.
For this field ... Select...
Platform Event The platform event whose event messages can start the process.
Object The object whose records you want to associate with the event.
Matching Conditions

Criteria to identify one record to associate the event with. We recommend using an ID or other field that uniquely identifies records so the process can pick exactly one record.

The process fails if it finds:

  • Multiple records that match the criteria.
  • No records that match the criteria.
![Example configuration of an Event process' trigger](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/process_builder/pb_trigger_event.png) 3. Before saving your changes, confirm the selection because you can’t change the platform event or object after you save it. ## Invocable If the process starts when another process invokes it, associate the process with an object. 1. Click **Add Object**. 2. Select an object to associate with the process. Type to filter the dropdown list. This process can be invoked from any other process as long as the main process passes a record of this object type. For example, an Account-based invocable process can be called from a Contact-based record change process, because you can pass the contact’s account to the invocable process. 3. Before saving your changes, confirm the selection because you can’t change the object after you save it.