Skip to main content

Automatic generation and dispatch of certificates using Actions

Wiktoria Jeziorska avatar
Written by Wiktoria Jeziorska
Updated over 2 months ago

Introduction

The Actions module in Gridaly allows you to automate many repetitive tasks. One of the most common uses is to automatically generate and send certificates to participants who meet the conditions you specify, such as completing a gamification task.

From this article you will learn:

  • How to prepare a certificate template?

  • How to set up an action that will automatically issue a certificate?

  • How to create a system email that will send the certificate to the participant?

  • How does a participant receive and download their certificate?


Step 1: Prepare a certificate template

Before you set up automation, you must first create a certificate template. It will be the basis for generating a unique document for each participant.

  1. In the event administration panel, in the menu on the left, go to Other, and then select Certificates.

  2. Click the + button to add a new template.

  3. Configure its appearance and content using the available variables, and then save.


Step 2: Configure the Certificate Issuing Action

Once you have the template ready, you can proceed to create the automation that will generate the documents.

  1. In the menu on the left, go to Actions.

  2. Click the + button to create a new action.

  3. In the action creation form, fill in the key information:

    • Name: Enter a name that allows you to easily identify this action, such as "Certificate for completing gamification."

    • Action type: Select Issue certificate from the drop-down list .

    • Certificate: Select a previously prepared template from the list.

    • Trigger (Trigger): Select an event to trigger the generation of the certificate, such as Participant completed the task.

  4. After configuring the fields , click "Save".

Your action is ready. Now, when the participant meets the condition, the system will generate a certificate for him. The next step is to configure the automatic mailing.


Step 3: Configure the automatic mailing.

In order for a participant to receive a notification with a generated certificate, you need to create a corresponding System Mail.

  1. In the menu on the left, go to Communication, and then System Mails.

  2. Click the + button to add a new email template.

  3. In the Action field, expand the list and select the event: Certificate | Issued.

  4. Customize the body of the message. You can use the {certificateItem.publicUrl} variable to insert a direct link to download the certificate in the body of the email.

  5. Save the template.

From now on, the system will work fully automatically. The action will generate a certificate, and the System Mail, reacting to this event, will send it to the participant.

Important: The certificate is automatically attached to the email as a PDF attachment. Using the {certificateItem.publicUrl} link in the body is an added convenience for the recipient.


How does the participant receive the certificate?

When the action is launched, the participant will immediately receive an email with the generated certificate attached. Regardless, the document will also always be available for download in his participant profile on the event platform.


FAQ

Do I need to create a system email for each type of certificate?

No. You just need to create one system email for the Certificate | Issued action . It will handle the mailing of all certificates generated at your event, regardless of which action issued them.

Can I issue certificates retroactively for participants who met the condition before the campaign was created?

Actions do not work retroactively. To grant certificates historically, you can use an action with the trigger Manual, and then in the Participants module select the desired people and run the action for them in bulk.

What happens if I update a certificate template that has already been generated for some people?

Participants for whom the certificate has already been generated will keep the original version. The updated template will be used only for those for whom the action will be performed in the future.


​

Did this answer your question?