Hi <<First name>>!
Last month, the powerful concept of events was introduced to Flex. Today, we are releasing an update that extends the concept to transaction events. You can now build automations related to bookings, reviews, and transactions.
As a reminder, any change in your marketplace activity can constitute an event. Events, in turn, can be used to trigger a whole slew of automatic actions, like sending SMS notifications or triggering actions in third-party apps.
What you can do with transaction events
Here are some example automations you can build with transaction-related events.
Send SMS notifications about new bookings. Integrate to a tool like Twilio to send SMS notifications. Notify providers when someone books from them, customers when their booking is confirmed, and so on.
Update a third-party calendar. Update a provider's Google Calendar whenever someone books a time slot from them. You can do this by monitoring booking events and then calling the Google Calendar API when a new booking happens or an existing booking is cancelled.
Synchronize transactions with each other. Want to build a transaction flow where multiple people bid on a project? With transaction events, you can ensure other bids are automatically rejected when the customer approves one bid.
Update a third-party payment system. Adding a new payment system to your marketplace (instead of the built-in Stripe-powered system) is a lot easier with transaction events. For example, if a cancellation occurs in the marketplace, you can automatically trigger a refund in the third-party system. In short, transaction events help you keep your payment system in sync with the events on your marketplace.
Find events easily with the Flex CLI
In addition to support for transaction events, this release adds an improvement to the Flex developer experience. You can now use the Flex CLI to find all events related to a specific user, listing, or transaction.
|
