Overview
The event transform action (also referred to as ETA) offers great versatility, with its primary purpose being to "transform" your event data in a highly flexible manner.
Tines references
Before getting started, we recommend familiarizing yourself with the surrounding functionality this article covers:
Make it happen
✅ Check one: What do you need the event transform action to accomplish?
With its multiple modes, the event transform action can cover a variety of use cases:
Mode | What it does | When to use it |
Leverages AI for data transformation | You want to utilize Tines AI to perform data calculations in one action. See also: tips for automatic mode. | |
Only allow unique values to flow through based on a provided identifier. | Your user attempts to open multiple, duplicate tickets to an IT team, and you need to remove the duplicates so that only one is actually created. | |
Create buffer time before the next action. | You submit a request via an HTTP request action to a service, but need to wait a few minutes before the result is ready. | |
Execute every item in an array as a separate element and its own event. | You have an HTTP request and need to give it individual items and not a whole array. | |
REGEX to extract data | You want to use a REGEX expression to extract specific values from a string. | |
Assemble an array from multiple events that occurred previously in the story. | You have event data that you want to pull together into one event, either from an explode or from a story fork. | |
Leverages dynamic/static event data to emit | You want to restructure your data before the next action. | |
Allow event data to emit at a rate that you determine. | You are reaching out to an API service that has a rate limit. |
✅ Check two: Familiarize yourself with each mode's configuration and options
A large aspect of Tines is configuring your actions to run the way you want. Let's take a look at some important tactile concepts.
When you pull an event transform action onto your storyboard, it defaults to Message only mode. You'll see that there are key components of the action, such as it's name and description, in the config panel on the right. As you use different modes of the event transform action, you'll see these change.
Tines Tip: Built out your action, but need help naming it? Use our AI "Generate name" feature next to the action name ( ✨ icon) to automatically generate an action name based on what it's doing!
When creating an action, you'll find a + Option button at the bottom of the config panel. Some settings here can apply to all modes, while others are specific to the selected mode. Exploring these options over time can help you customize actions more effectively.