TrackerRMS Help

Your one-stop shop for help on TrackerRMS

Back to Topics

Help Topic: EVA & Agentic | Triggers (Automated Agents)


In this lesson we cover:

  • Introduction

  • Creating Triggers

  • What happens next?

  • Example One | Creating a Trigger for Resume Summary

  • Example Two | Creating a Trigger for Job Screening Questions

  • Example Three | Creating a Trigger for Alignment Scorer

 

Introduction

Triggers can be set up for any Agent Instance, meaning when the triggering action(s) occur the Agent Instance is automatically run in the background. Whilst it runs you can be getting on with whatever's in front of you. You don’t have to wait for it, Tracker will give you an Alert to let you know its working, and when its finished.

You can use the same agent instance in multiple triggers, or create multiple of the same trigger, each with a different outcome (Agent Instance), so that more than one thing happens off the back of an action.

For example, you create two triggers for when a new candidate is created:

One to create an Agency resume and the other to run the Resume Scrubber.

Once they're built, they just run, every time that trigger happens, with no one needing to remember to kick them off.

 

Creating Triggers

Creating a Trigger is simple, will go through the basic steps here, then see a couple of examples.

Remember, you can have multiple agent Instances for any one Agent, so for example you may want different resume templates depending on a candidates type or sector - in which case you could set those up as separate Triggers.

 

Starting Point

Click the New button in the Triggers area.

Step One - Trigger

Select the appropriate record type for the Agent Instance you’ll be using.

For example, Agents creating Resume’s or Resume Summaries will be for Candidate Records, the screening questions are a job related agent, and the Alignment Scorer is linked to Placement records.

When the appropriate record type is selected, the Triggers shown are relevant for that record type.

If multiple Triggers are selected, all must be matched in order for the Agent to run.

Step Two - Cool Off

In Step two we can set a cooling off period so that the agent doesn’t get run multiple times in quick succession, or set it to only ever run once per record.

Step Three - Agent

In step three we pick the Agent Instance to run when the trigger or triggers are matched.

What happens next?

There’s not more hands on involvement from you other than doing the action as set in Step one - the Trigger.

Once you complete that action, Tracker will get to work. It's all done here for you, without you having to think about it.

You’ll get notified via an Alert when it starts to run the action.

You’ll also get an Alert once its completed.

 

 

Example One | Creating a Trigger for Resume Summary

Outcome of Trigger

When a new candidate is created a summary will be produced as a PDF which will attach in the candidates documents as a PDF.

Step One

As this is Candidate related, in step one you will pick Candidate as the record type, and then choose Created/Registered as the Trigger.

Step Two

We’ll only ever create the Candidate the once, which means this will only automatically trigger one. So in this scenario I’ll set it to run once per record (it can always be run manually later if a new resume is acquired).

Step Three

This is where we pick the Agent Instance for this trigger - in this case - Resume Summary | PDF.

 

Example Two | Creating a Trigger for Job Screening Questions

Outcome of Trigger

When a Permanent Job is created, screening questions are generated.

Step One

As this is Job related, in step one you will pick Job as the record type, and then choose the tow triggers to be met.

  • Created/Registered

  • Job Type = Permanent (selected from drop down)

Step Two

We’ll only ever create an individual Job the once, which means this will only automatically trigger one. So in this scenario I’ll set it to run once per record (it can always be run manually later if a new resume is acquired).

Step Three

This is where we pick the Agent Instance for this trigger - in this case - Job Screening Questions.

 

Example Three | Creating a Trigger for Alignment Scorer

Outcome of Trigger

When a candidate is shortlisted to a Job, an alignment score is created for them.

Step One

As the Shortlist status is related to Placement records, in step one you will pick Placement as the record type. You will then pick Placement status as the Trigger, and select Shortlisted from the drop down list.

Step Two

Let’s take the scenario you send a shortlisted candidate internally for review, off the back of feedback get a new/updated Resume for them and move them back to Shortlisted, you might want a new Alignment Report. So in this instance we’ll set the Cool off period to Don’t run again after firing for 1 Day.

Step Three

This is where we pick the Agent Instance for this trigger - in this case - Alignment Scorer