Every time an action in Tines runs, it emits an event. You can view an individual action's events in its Event panel, where each event is listed with details like:
A unique event ID identifier.
The action that created it.
The exact data (JSON payload) returned.
The time it was created.
You can expand any event to see the JSON data inside. This is a great way to understand what your story is working with at each step. For example, if your HTTP Request action fetched a list of users, you’d see that response data directly in the event’s JSON body.
Because the event data is stored this way, you can confidently build automations and agents that depend on accurate, traceable information. Whether you’re pulling a user ID, checking a response message, or confirming a result, everything you need is stored in the relevant action's event.
🖐️ Try this: Navigate the Events panel
How events come together via story runs
These individual action events are stored in the story’s runs, which serve as a history of everything that has happened during execution. You can view each story run completed via the three-dot menu > Story runs.
In addition to what individual event data includes, story runs include:
A unique identifier called a Story Run GUID.
How many events occurred during the story run.
When the story run started and when it completed.
The duration of the story run execution.