Tokeet has many subsystems that need to communicate and coordinate with each other. This is mostly accomplished by the use of Events. Whenever something happens in Tokeet it causes an Event to occur. Think of an Event as our internal way of letting different systems know when something interesting or important happens. When an event occurs, Tokeet creates a new Event object and sends it to the Event handler for processing. For example, when a booking is confirmed, Tokeet creates a special event which communicates this to the Event Handler; When an invoice payment happens, Tokeet also creates an associated event.

All of these events are sent to the Event Handler which checks for subscribers to the event. Many of Tokeet's components subscribe to various events, then perform specific actions when these events happen. Tokeet allows you to subscribe to these same events via Tokeet Trigger. A Trigger is an instruction to Tokeet to perform a specific action when an event occurs.

Note that many user actions may cause multiple events to be created. For example, when Tokeet receives a new booking from Booking.com, an inquiry created event occurs as well as booking confirmed and guest created events. It is important to subscribe to the right event and understand that if you subscribe to multiple events all triggers may fire due to the same action.

If you have questions please contact the support team. We're always happy to help.

Did this answer your question?