What is the Trigger Broker Framework?

The Trigger Broker Framework allows automation for objects that don’t natively support record-triggered flows. It uses lightweight triggers to publish platform events, enabling flow-based business logic for record changes.

Why Contact Us to Add a New Object?

To maintain consistency and avoid duplication, all object triggers are managed within the package. This ensures:

• No Duplication: Prevents multiple triggers running on the same object.
• Error-Free Updates: You’ll automatically benefit from ongoing updates and improvements.
• Streamlined Management: We handle the technical setup so you can focus on building flows.

How to Request Support for a New Object

If you need a new object added to the Trigger Broker Framework:

1. Email us at [email protected].
2. Include the following details:
   • Object Name: The API name of the object you’d like added (e.g., ContentDocumentLink).
   • Reason: A brief explanation of why you need this object supported.

Our team will review your request and provide updates on when the object can be added.

Currently Supported Objects

Our initial use-case for this feature is for the ContentDocumentLink Object. This will allow you to configure flows that notify users when a file is attached to a record. See Subscribing to Trigger Events in Flow for details.

If you require a new object, simply reach out, and we’ll handle the rest!