Skip to main content

Events

Understanding how HireData events work

Updated over 2 weeks ago

When you connect your core app, such as Carerix, Salesforce, OTYS, etc., to HireData, it will start sending events, which are notifications that something has happened in your system. Events trigger your automations, making them crucial to how HireData works in the background. In this article, we'll explain how events work, where to find them, and how to analyse them if something doesn't go as expected.

What is an event

An event is a signal sent from your connected app to HireData. It usually represents a specific action or change, for example, a new candidate being created, a vacancy being updated, a placement being completed, etc. These events are used to trigger the automations you've set up in HireData, and every event includes Event Data, External Records and Processes.

Event example:

Individual event page

How to view event details

Navigate to the Settings menu and open the Events page to see a list of all events sent from your connected apps:

Events page in HireData

Use the filters for a more organised view, for example, if you want to see the events coming from one of your apps:

Setting up filters

To explore an individual event, click the [Details] button next to the event for a short overview or open the dropdown menu and click [View].

Event drop-down menu

This will open the event detail view, which includes:

  • Event Data – a summarised view of the data received from your app.

Event Data tab

  • External Records – additional fields from the source app, even if they aren't used in the automation.

External records tab

  • Processes – the list of automation(s) triggered by this event and the runs it created. You'll also see each run's status (e.g. Completed, Delayed, Cancelled).

Processes tab

Troubleshooting events

If an automation didn't run as expected, or you're seeing unexpected data:

  • Go to the Processes tab of the event and check if any runs were created.

  • Click into the run to view logs and see if a step failed or was skipped.

  • Compare the Event Data with the conditions in your automation to ensure it matches.

If no process was triggered, the event likely didn't meet the criteria of any active automations.

Still need help?

If you're unsure why an event didn't trigger your automation or want help interpreting the event data, feel free to contact our team at [email protected]. If you do, please include:

  • A link or the ID of the event;

  • A link or the name of the automation you expected to be triggered;

  • Any relevant steps or context that might help us investigate throughout.

Did this answer your question?