Skip to main content

Overview

Introduction

Events represent the structured data sent between actions. Events are JSON objects making them flexible and easy to read. All events are timestamped and "write-once", providing an audit trail and making them an ideal basis for calculation of key performance metrics.

Event Structure

When an event is emitted by a Tines action, it will contain the result of the action's action and, where there was one, the received event. For example, the below image shows an event emitted by an action called "Type is infection". The "Type is infection" action is configured to receive events from an action called "Receive events":

Example emitted event

important

The result of each action's action is contained in an object whose key is an underscored, lowercase form of the action's name. For example: if the action's name is 'Send email', the result of the action will be contained in a key titled 'send_email' in the emitted event.