Triggers, conditions, and actions reference

Last updated: July 23, 2026

Reference for the building blocks inside an automation: the 12 events across four groups (Students, Proposals, Enrollments, Sales), the 'When it runs' timing options, conditions, action types, and the variables you can use in email and webhook content. Use this article when building or editing an automation.

This is the reference for the building blocks you use to build an automation: the event that starts it, the conditions that decide if it runs, and the actions it performs. Use it alongside How to set up Automations.

What it is

Every automation is made of three parts:

  • Event — the thing that happens in Edvisor that starts the automation (for example, a new student is created).
  • Conditions (optional) — extra rules that must be true for the automation to run.
  • Actions — what the automation does when it runs (for example, send an email).

You choose these in the automation builder. This article lists every option you can pick.

Events

An event is the trigger that starts an automation. There are 12 events, grouped into 4 categories.

Students

  • A new student is created
  • A student is updated
  • A student is deleted
  • It is a student's birthday
  • A student's visa is about to expire

Proposals

  • A proposal (quote) is created
  • A proposal is issued or sent to the student

Enrollments

  • A new enrollment is created for a student
  • An enrollment is accepted by the school

Sales

  • A sale is started
  • An accommodation sale is started
  • A sale is created

Note: New events will be added over time, to expand the range of events that can trigger an automation.

When it runs

For each event you set the timing:

  • Instantly — the automation runs as soon as the event happens.
  • Before — it runs a set number of days before a date.
  • On the day — it runs on the date itself.
  • After — it runs a set number of days after a date.

Date-based events (like a student's visa expiry or a course start date) ask you to enter a Duration in days for Before or After. Date-based events cannot run "Instantly", because they depend on a future date.

Conditions

Conditions are optional rules that must be true for the automation to run. If you add conditions, they use AND logic — every condition must be met.

Right now there is one condition field:

  • Student Nationality — with operators such as "is any of".

For example, you can set an automation to run only for students of a specific nationality.

Actions

Actions are what the automation does when it runs. You can add more than one. Actions run one after another and each runs independently — if one action fails, the others still run.

Actions are grouped into two categories.

Communication

  • Email student — sends an email to the student. The student's email is filled in automatically. You set the Subject and Body (both required), and you can use variables (see below).
  • Email Counselor — sends an email to the student's assigned counsellor.

Integrations

  • Create Task — creates a task. You set the task name, due date, and assignee.
  • Send Webhook — sends data to a URL you choose. You set the URL and the Payload. For safety, webhooks can only be sent to public addresses, and they follow a maximum of 5 redirects.

Variables

Variables let you insert real student and agency details into an email. When the automation runs, each variable is replaced with the real value.

Student

  • Student ID
  • First Name
  • Last Name
  • Email
  • Date of Birth

Agency

  • Agency Name
  • Office Name

If a variable cannot be filled (for example, the student has no date of birth), the placeholder is removed from the message.

Related