Certificates are a great way to encourage learners and celebrate their progress through journeys at your company. Automating them helps ensure achievements are recognized consistently and without delay.
You can automate certificates to be granted when users complete specific progress milestones.
š„ Important:
Certificates will only be granted if the event type is set to one of the following:
Activity is completed
Journey/section is completed
Programme is completed
Grant certificate after activity completion
Go to Control > Behaviour > Automations, then click Create new automation
Set up the automation:
Event type: Activity is completed
Conditions:
Choose Is activity in event, then select the activity
Set Completion status: Completed
š” Tip: Use the āorā condition to select multiple activities if needed
Action: Grant certificate
Title: Name your certificate (visible to learners)
Attach to: Choose the activity
Activity source: Event > Invite > Activity
User source: Event > Invite > User
Save
Configure certificate field mapping
a. Click the Grant certificate action to open the full settings
b. Scroll to Certificate field mapping and map these fields:Name source: Event > Invite > User > First name / Full name
Activity name source: Event > Invite > Activity > Title
Date source: Event > Invite > Completed at
š” Tip: You can also map duration, expiry date, or contract start date
Save your automation āļø
ā Done! Learners will receive their certificate after completing the activity š
Grant certificate after journey or section completion
Go to Control > Behaviour > Automations, then click Create new automation
Set up the automation:
Event type: Journey/section is completed
Conditions:
Choose Is journey/section in event, then select the journey or section
Set Completion status: Completed
Action: Grant certificate
Title: Name your certificate
Attach to: Choose journey
Container source: Event > Module container
User source: Event > User
Configure certificate field mapping
a. Scroll to Certificate field mapping and map the following:Certificate/module name: Event > Module container > Title
User name: Event > User > Profile > Full name
Module name: Event > Module container > Title
Date achieved: Event > Recorded at
š„ Important: Optional fields like duration, expiry date, and contract start date can also be mapped.
Save your automation āļø
š Done! Learners will receive their certificate after completing the selected journey or section.
Grant certificate after multiple activities or journeys (in any order)
If a user needs to complete multiple activities or journeys, and the order is unknown, you can still grant a certificate once all are completed.
Hereās how:
Add a condition group with an "Or" condition:
Add all your activities or journeys in āActivity in eventā or āJourney in eventā conditions
Add a second condition group with an "And" condition:
Add the same activities or journeys using āActivity is completedā or āJourney is completedā
Make sure you use an "And" condition between the two groups.
š„ Important: The final activity or journey the learner completes must always be included in a ā[Item] is completedā condition to trigger the certificate grant.
Add the Grant certificate action and set up:
Title, Attach to, and mapping fields as shown in previous sections
Save your automation āļø
š Done! Certificate will be granted regardless of the order in which users complete the steps.
Certificate field mapping
The dynamic field mapping configured in the certificate will be reflected in the automation.
For example:
When creating a certificate, you add a name for the dynamic field
When adding the automation for the certificate
Final check-up
Always check if the automation does the intended behaviour by impersonating a user or testing first for yourself.
š„ Important:
Automations only apply going forward.
If a user completed the activity before the automation was created, they will not receive the certificate retroactively.