A Boomi Flow listener is used to listen to events on a particular record or file. We can also add business rules that determine which path the flow takes.
When an event occurs (for example, a record is updated) in the underlying application (say, in Salesforce), the Flow platform can trigger an event or an action.
Listeners work as follows:
- We send the service the objects we want to listen to (referencing the appropriate value). In addition, we specify the type of event we are interested in (Say, record created).
- The service will notify the platform when that event has happened on the associated object(s). This will populate the referenced value with the latest data from the service.
- We specify the outcomes (with comparisons/rules) under which we “accept” the event and the path the flow should follow. If the comparisons/rules are met, the flow will proceed to the next map element in the flow as defined by the matching outcome. If not, the flow will continue to wait until the appropriate event occurs.
Some examples of a listener use-case are:
- Listening for updates to a task record in Salesforce, and only progressing the flow when the task is completed.
- Listening to a particular file for updates and/or modifications.
- Listening to a case record in Salesforce, and only progressing once it’s “Closed Won”.
- And the list goes on…
Check out the glossary for a definition of terms and key concepts that appear in the Boomi Flow website, Drawing Tool, technical documentation, blogs, and marketing communications.