Those of you who use Workflow Automation, that snazzy drag-and-drop canvas for visually architecting campaign workflows, know that there is a set of triggers we give you in the Workflow Toolbar to initiate your workflows.


For example, you can trigger a workflow when a contact is added in Bronto, or when a contact field is updated, or when someone texts in a keyword via SMS.

With the addition of the Received API Event Trigger, which is essentially an API hook for Workflow Automation, you can now use any event to trigger a workflow via the Bronto API.

The two specific API calls you can use to trigger a workflow are:

1. addContactEvent
2. addContactsToWorkflow

What’s the value?

Using the Bronto API with Workflow Automation offers a couple of key benefits:

  • Flexibility - Rather than wait for an event to occur in Bronto, you can now trigger a workflow programmatically, at your discretion, and you can choose the event that initiates the workflow—even if it’s an event that takes place outside of Bronto, i.e., in your database or e-commerce system. This opens up a lot of possibilities. Think sky is the limit, and use your imagination!
  • Ease of Use - This is a way to decouple the process of defining how a workflow is triggered, which is typically the developer’s domain, from what happens in the actual workflow, which is the marketer’s domain. Developers can use the API to ensure the right flow of data into Bronto, and marketers can use this data to work their magic on the canvas and make sure the right campaigns ensue.

What can I do with the Received API Event Trigger?

Here are 5 example events you could use to trigger a workflow via the API: (Caveat: all of these require an API integration.)

1. Abandoned cart - an abandoned shopping cart in you e-commerce system could spark an email or a series of emails in Bronto

2. Successful purchase - when a purchase occurs in your e-commerce system, it could set off a product review or a rewards program email

3. Multiple views of a product page - you could choose to have a message sent once someone views a product page a certain number of times

4. Abandoned ad - when someone clicks on a banner ad on your site, but does not convert, they could receive a specific message

5. Update preferences based on shopper behavior - when someone navigates certain categories or sections on your site, it could trigger a workflow to update their preferences accordingly in Bronto

I would love to hear how some of you are using, or planning to use, the Received API Event Trigger. Please share thoughts and ideas!

Also, if you need help writing an API integration, contact Bronto Professional Services at 888-BRONTO-1, or talk with your Account Manager.

Damian Trzebunia (Che-boon-ya)
Product Marketing Manager
Bronto Software