What is the TRIGGER_FLIPPER pattern?

TRIGGER_FLIPPER(flip_if_evaluated_true_optional) resets a checkbox field to FALSE in a Self-Adaptive #Trigger (before insert/update) while keeping the "flip" in memory. You can then use TRIGGER_IS_FLIPPED(field_name) in a #Trigger Action's scope filter to fire the desired automation.

It works like the Send notification email option on Case ownership changes—except instead of a UI-only checkbox, DSP uses a real field on your object. Flipping the field on record save fires automation, and the reset makes it reusable.

With an optional condition parameter (flip_if_evaluated_true_optional), TRIGGER_FLIPPER can also auto-flip the field when the condition evaluates to TRUE—making the automation not only on-demand (manual checking) but also dynamic (condition-driven).

Example:
Suppose you create a checkbox field SendEmailNotificationToOwner__c on Case.

  • In a Self-Adaptive #Trigger, set the mapping to:

    TRIGGER_FLIPPER(TRIGGER_IS_CHANGED_TO("Status", "Closed"))
  • Then, create a #Trigger Action that uses:

    TRIGGER_IS_FLIPPED("SendEmailNotificationToOwner__c")

    in the After Update Scope Filter, and configure it to send an email notification with Case details.

This way, SendEmailNotificationToOwner__c acts as a simple, reusable capability—triggered either manually by checking the field, or automatically when Status changes to Closed.