A #Trigger Action uses the triggering records as input to perform an action on other records — related, parent, child, or entirely different objects. Unlike a Self-Adaptive #Trigger, which transforms the same record, a #Trigger Action reaches outward.

When a trigger event fires, DSP evaluates the Scope Filters to determine which triggering records qualify, then runs the configured action against the target. Common patterns include:

• Update related records — e.g., update a parent when a child changes, or cascade updates down to child records.
• Create new records — e.g., generate tasks, log entries, or follow-ups.
• Send notifications — e.g., email alerts or in-app bell notifications.
• Publish Platform Events — for integration with external systems.

This makes #Trigger Actions a natural fit for cross-record logic — keeping parent–child data in sync, automating downstream processes, and orchestrating notifications, all defined declaratively as record-based configuration.