What is No-Code custom event builder and how to use it?

ZEPIC provides a simple rule-based system to create custom events without coding. This method is for triggering events based on the data coming from a different system. Some of the use cases will be:

1. If a customer gives a 5-star review in your review system and you want to track it, segment customers and run automated workflows.

2. If a customer raises a very urgent priority ticket and if they recently purchased a very high-priced item, you want your customer success team to be notified.

In this article, we will take a simple use case of an order getting cancelled and you being able to track it as an event to trigger flow automation.

Understanding Your Data Objects

In an e-commerce platform, let us assume you have these data objects:

• Customer: Contains customer details (name, email, etc.)

• Order: Stores order information (ID, status - draft/abandoned/shipped/complete)

• Product: Holds product details (images, availability, inventory)

• Wishlist: Tracks products that customers save for later

How No-Code Custom Events Works

Custom events trigger when specific values or properties change in these objects. For example:

•  When the order status changes to "paid"

•  When a customer adds an item to their wishlist

Previously, these events were predefined based on common use cases. Now, ZEPIC gives you the power to:

• Create custom events based on your specific criteria

• Align events with your business processes

• Set targeted triggers for important scenarios

Examples

1. Trigger abandoned cart notifications only for high-value items

2. Prioritize wishlist alerts for high-value customers

3. Notify your customer support team if a customer is unsatisfied and publishes a bad review about a product.

How to configure custom event rules in ZEPIC?

Pre-requisites:

• An object for which you want to trigger an event and another to which you want to associate it with.

Steps:

• In the left navigation bar, click on “Settings” -> “Custom Events”. Click on the “New Rule”:

• Enter the rule name and choose an object, based on which you want to configure the rule:

• You can configure the kind of changes that trigger a custom event. 

• Type of change: 

  • Created

  • Updated

  • Created or Updated

• Property change

  • Any property in the object

  • Specific properties in the object

• Name of the custom event

• Custom Event Properties

  • You can choose what properties should be part of the custom event. This is how the custom event properties would look once it is published.

• Target object

  • Choose the object to which you can publish this custom event

• You can add even more fine granular filter criteria based on your use case:

• The custom event rule becomes active immediately after saving. The configured events will publish automatically whenever the specified object conditions are met.

• You then use the custom events generated in “Segmentation” or “Flows” and run your campaigns or automation.

Key things to remember:

• Custom events only trigger changes that happen while the rule is active. Events cannot be triggered retroactively for past changes.

• Use the "Pause" feature when performing bulk updates or initial data uploads. Resume custom events once your bulk actions are complete. This helps prevent unwanted notifications during large-scale changes.

• When publishing custom events to a lookup field object, you can only use parameters from the anchor object. Parameters from multiple objects cannot be combined in a single published event.