Skip to main content

How to grant a certificate

How to set up the automation for a certificate

Written by Marie Xhauflair

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 are most commonly granted with one of these event types:

  • Activity is completed

  • Journey/section is completed

  • Programme is completed

Scheduled automations can grant certificates too. The certificate must be published before an automation can grant it.


Grant certificate after activity completion

  1. Go to Control > Behaviour > Automations, then click Create automation

  2. 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 (the other options are journey and programme)

      • 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

        • šŸ”„ Important: Map every dynamic field on your certificate, for example duration, expiry date or contract start date. Otherwise the automation won't save

  3. Save your automation āœ”ļø

āœ… Done! Learners will receive their certificate after completing the activity šŸš€

šŸ’” Note: If you also add a group condition, combine it with Is activity in event using AND. Without the in-event condition the certificate is granted every time a group member completes any activity.


Grant certificate after journey or section completion

  1. Go to Control > Behaviour > Automations, then click Create automation

  2. 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

  3. 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: Map every dynamic field on your certificate, including duration, expiry date and contract start date if the certificate uses them. Otherwise the automation won't save

  4. Save your automation āœ”ļø

šŸŽ‰ Done! Learners will receive their certificate after completing the selected journey or section.


Grant certificate after programme completion

Follow the same steps as for a journey, with these differences:

  • Event type: Programme is completed

  • Attach to: Choose programme

Then map every certificate field and save your automation āœ”ļø


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:

  1. Add a condition group with an "Or" condition:

    • Add all your activities or journeys in ā€˜Activity in event’ or ā€˜Journey in event’ conditions

  2. Add a second condition group with an "And" condition:

    • Add the same activities or journeys using ā€˜Activity is completed’ or ā€˜Journey is completed’

  3. Make sure you use an "And" condition between the two groups.

    1. šŸ”„ Important: The final activity or journey the learner completes must always be included in a ā€˜[Item] is completed’ condition to trigger the certificate grant.

  4. Add the Grant certificate action and set up:

    1. Title, Attach to, and mapping fields as shown in previous sections

  5. Save your automation āœ”ļø

šŸŽ“ Done! Certificate will be granted regardless of the order in which users complete the steps.


Email the certificate to the learner

By default, learners find their certificate in the platform. If you'd rather send it straight to their inbox, the Grant certificate action can email it with the certificate PDF attached, so there's nothing for them to click!

  1. Open the Grant certificate action in your automation

  2. Scroll to the bottom, just under the User field, where it reads Sends email to the user with certificate as attachment

  3. Tick Send e-mail, this opens three extra fields

  4. Fill in the email:

      • Email template (required): choose the template the email is built on

      • Email subject (optional): the subject line learners see

      • Email message (required): the body of the email, with bold, italic, headings, links and images

  5. Save your automation āœ”ļø

āœļø Tip

Both the subject and the message can use variables for dynamic content, for example {{variable}}, so you can greet learners by name or name the activity they completed. Both fields have the translate icon too, so you can set them up per language

🚧 Be careful

  • Learners without an email address on their profile won't receive anything, they still get the certificate in the platform

  • Test the automation on a test user with a real email address first, that way you see exactly what lands in the inbox before you switch it on for everyone


Certificate field mapping

The dynamic field mapping configured in the certificate will be reflected in the automation. Every dynamic field needs a source, otherwise the automation can't be saved.

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.

  • An event automation fires at every matching completion, so if an activity is reset and completed again, the certificate is granted again.

  • Keep in event conditions and is completed conditions in separate AND groups. An OR between them fires at every completion by a user who meets the state condition.

Did this answer your question?