Introducing the Trigger Broker Framework
What is the Trigger Broker Framework?
The Trigger Broker Framework is a solution designed to address Salesforce's limitations with record-triggered flows for certain objects. It enables admins and developers to automate processes for objects that cannot natively support record-triggered flows, using a flexible, event-driven architecture.
Why Does It Exist?
Salesforce does not support record-triggered flows for all objects, leaving gaps in automation. The Trigger Broker Framework bridges this gap by:
- Publishing platform events via lightweight Apex triggers.
- Enabling flows to subscribe to these events and implement low-code automation.
- Centralizing logic for easy governance and scalability.
How Does It Work?
- Triggers and Event Publishing:
- A trigger is added to an unsupported object. When certain conditions are met, it publishes a platform event (
TriggerBrokerEvent__e
).
- A trigger is added to an unsupported object. When certain conditions are met, it publishes a platform event (
- Event Subscription:
- Admins use flows to subscribe to these platform events, allowing business logic to be defined in a low-code way.
- Metadata-Driven Configuration:
- Using
TriggerBrokerEventSettings__mdt
, admins can control which objects and trigger events are supported and whether JSON payloads should be included.
- Using
Key Benefits
- Extensibility: Works with any object, including those Salesforce does not natively support.
- Low-Code Enablement: Build powerful automations using flows without writing additional Apex.
- Governance: Metadata-driven configurations ensure admins maintain full control over the framework's behavior.
How Can It Be Used?
The Trigger Broker Framework enables use cases like:
- Notifying users when files are attached to cases.
- Automating follow-ups for updates to unsupported objects.