Skip to main content

Variable overview

Variables are a powerful feature that allow you to make your platform communications dynamic, personalized, and context-aware

Written by Marie Xhauflair

First need help with setting up the automation for the notifications? Then check out this article! 🚀

What are variables?

First, let's talk about what variables actually are. Essentially, variables are dynamic placeholders to personalize content. Instead of writing each user’s name, module title, or manager manually, variables pull in this data automatically which saves time and makes communication to users more relevant.

Where can we find variables?

  • Notifications

    • Platform

    • Emails

  • Magic wall

  • Learning content

  • Workflows

For who are variables for?

  • Users

  • Buddies

  • Direct and indirect managers

  • Everyone and anyone, really!


📚 List of available variables

⏰ Note: These variables are related to the conditions (users or activities) that trigger the event. Which variables you can use depends on the event that triggers the notification. See "Variables per event" further down for the full overview.

Example user

Profile of user

Groups of user

👤 About the user

Which user is this about?

Variable

Description

Example user

{{event.user.first_name}}

First name

John

{{event.user.last_name}}

Last name

Smith

{{event.user.get_full_name}}

Full name

John Smith

{{event.user.username}}

Username

jsmith

🗓️ About the user contract

What is the contract start/end date of the user?

Variable

Description

Example user

{{event.user.profile.contract_start_date}}

Start date of the user's contract

1 May 2025

{{event.user.profile.contract_end_date}}

End date of the user's contract

N/A

🤝 About the buddy

Who is the buddy of the user?

Variable

Description

Example user

{{event.user.profile.buddy.first_name}}

Buddy’s first name

Jane

{{event.user.profile.buddy.last_name}}

Last name of the buddy

Cook

{{event.user.profile.buddy.get_full_name}}

Full name of the buddy

Jane Cook

✏️ About the manager

Who receives the notification as the manager?

Variable

Description

Example user

{{manager.first_name}}

First name of the manager

Lisa

{{manager.last_name}}

Last name of the manager

de Jong

{{manager.get_full_name}}

Full name of the manager

Lisa de Jong

{{manager.username}}

Username of the manager

ldejong

👀 Good to know

The manager variables show the details of the person who receives the notification. They only show your manager's name when To manager is switched on. With it off, they show the learner's own name, or the buddy's name when To buddy is on.

✏️ Tip

Sending a notification to managers and want to use their name? Switch on To manager, then add the manager variable to your text. For example: Hi {{manager.first_name}}, {{event.user.get_full_name}} completed {{event.module.title}}.

📥 Receiver

Who will receive the notification/email? This can be the learner, their manager or their buddy.

Variable

Description

{{receiver.first_name}}

First name of the message recipient

{{receiver.get_full_name}}

Full name of the message recipient

{{receiver.last_name}}

Last name of the message recipient

{{receiver.username}}

Username of the message recipient

📤 Sender information

Who is the notification sent on behalf of? The sender is only filled when To manager or To buddy is switched on. In that case, the sender is the learner. Otherwise, the sender variables stay empty.

Variable

Description

{{sender.first_name}}

First name of the sender

{{sender.get_full_name}}

Full name of the sender

{{sender.last_name}}

Last name of the sender

{{sender.username}}

Username of the sender

🧠 Variables per event

Which activity, journey, programme, goal or group is this about? These come on top of the variables above and depend on the event that triggers the notification.

Event

Variable

Description

Activity complete / reset

{{event.invite.module.title}}

Title of the activity

Journey or section complete

{{event.module_container.title}}

Title of the journey or section

Activity ready for grading

{{event.module.title}}

Title of the activity

Activity graded

{{event.module.title}}

Title of the activity

{{event.grade}}

The grade

{{event.grade_comment}}

Comment or feedback left by the grader

{{event.grade_description}}

Descriptive label for the grade (e.g., “Excellent”)

{{event.graded_by.first_name}}

First name of the person who graded the activity

{{event.graded_by.last_name}}

Last name of the person who graded the activity

{{event.graded_by.get_full_name}}

Full name of the person who graded the activity

Programme complete

{{event.programme.title}}

Title of the programme

Goal complete

{{event.goal.title}}

Title of the goal

User added to / removed from group

{{event.group.group.name_i18n}}

Name of the group

👀 Good to know

Periodic events only have the variables from the sections above. If you use a variable that isn't available for an event, it stays empty in the message.

📅 Event

When did the event occur?

Variable

Description

{{event.recorded_at}}

Date and time when the event was logged

🔗 Actionable Links

Accessing a link.

Variable

Description

<a href="/#/reporting/user-detail/{{event.user.pk}}/">Click here to grade the activity.</a>

Direct link to the reporting page of the user the message is about


💡 Good to know!

The way variables behave can differ slightly depending on whether you're working with platform notifications or email notifications. For instance:

  • For platform messages, you could add a greeting and explicit mention of the user involved.

  • For email messages, they automatically include greetings, so you can skip "Hi {{...}}".

Did this answer your question?