Automate Triggers enables near real-time Salesforce events processing to transform and verify fields on records creation or modification.



Good to Know: Triggers are based on Salesforce Change Data Capture API. Considerations for CDC can be found here
General Considerations | Change Data Capture Developer Guide | Salesforce Developer
Default Change Event Allocations | Change Data Capture Developer Guide | Salesforce Developers



Accessing Triggers


Navigate to Triggers menu item under Automate module.


Adding New Trigger


Hit Add Trigger button, a dialog window will appear. Specify Trigger Name, select Object and Salesforce event when trigger should fire (Record Created and/or Record Updated) and select desired Actions to execute (Transform and/or Verify). Hit Next to advance to the next step.


Configuring Trigger


Depending on the actions selected a Transform or Verify steps will be shown. Specify desired actions to be executed similar to Brushr dataset configuration.


Learn more: Configuring Cleanse Datasets



Transform Actions


Verify Actions


If the field has been configured to synchronize back to Salesforce a green icon will appear next to the field name indicating that the verification status will be synchronized. More about Verifications can be found here


Hit next to advance to the Confirm step, hit Confirm button to create new trigger.



Good to Know: Triggers can be configured to bypass Salesforce Duplicate Rules, streamlining business logic and processes.



Execution Order


When multiple triggers are configured on the same Salesforce object, they are processed sequentially in the order they appear on the Triggers page. This guarantees a deterministic outcome when more than one trigger reacts to the same record change.


  • Triggers within an object group execute top-to-bottom based on their configured order.
  • A trigger whose event type does not match the incoming event (for example, an "On Update"-only trigger when the event is "Record Created") is skipped, and execution continues with the next trigger.
  • Disabled triggers are skipped entirely.
  • If a trigger fails, the pipeline continues with the next trigger in the sequence. The failure is logged in the Audit Log Browser with the error details.
  • Successful runs are logged in the Audit Log Browser with step-by-step timing per trigger.
  • A second change event on the same record waits for the active pipeline to complete before its own pipeline starts.


Good to Know: Drag a trigger up or down in the Triggers list to change its position within the object group. The new order applies on the next incoming change event.


Prompts Execution Order in Trigger


For triggers that include Enrichment actions, the prompts assigned to the trigger execute top-to-bottom following the same order configured on the Cleanse dataset. Later prompts can consume field values written by earlier prompts in the same trigger run.


Managing Triggers


The following functions are available from the Triggers page.

  • Edit trigger
  • Toggle (disable or enable) trigger
  • Delete trigger