Skip to main content

Certifier Triggers: Automate Workflows from Credential Events

Start an automation when a credential is created, issued, expired, viewed, shared, or downloaded, or when someone submits a Certifier Form.

Written by Caroline Tyrko

What Are Certifier Triggers?

Certifier triggers start an automation from an event in Certifier itself, such as a credential being issued, viewed, or shared. You can then send that credential data to a connected app, or use it to issue another credential.

Each automation is one trigger (the Certifier event) followed by one action (what happens next). To do two things on the same event, create two automations.

This article lists the triggers and actions available today and what each one does.


Available Certifier Triggers

There are seven Certifier events that can start an automation. Six are credential events, each set up for one Credential Template. The form event is set up for one Certifier Form.

Trigger

Fires when

Set up for

Credential created

A new credential is created in the Credential Template, either saved as a draft or created and issued in one step.

In the second case, Credential issued fires too.

Credential Template

Credential issued

A credential in the Credential Template is issued to its recipient.

Credential Template

Credential expired

A credential in the Credential Template reaches its expiry date.

Credential Template

Credential viewed

The recipient opens their credential in the Digital Wallet.

Credential Template

Credential shared

The recipient shares the credential to LinkedIn (as a post or with Add to profile), Facebook, X, Messenger, WhatsApp, Pinterest, Telegram, or Weibo. Copying the link doesn't count.

Credential Template

Credential downloaded

The recipient downloads the credential as a PDF.

Credential Template

New form response received

Someone submits a response to the selected form.

Certifier Form

📓 Learn more about the form trigger: How to Use Certifier Forms


What Data Each Trigger Passes

The trigger data is what you use to fill in the action's fields. All credential triggers pass the same data:

  • Credential ID

  • Public ID

  • Status

  • Recipient Name

  • Recipient Email

  • Issue Date

  • Expiry Date

  • Every custom attribute on your account

  • The time of the event (for example, Issued At or Viewed At)

Credential shared also passes the Share Channel.

A new form response received passes the Form Submission ID, the Form Submission Time, and the answer to each active question on the form.


Available Actions

Any Certifier trigger can be followed by any of these three actions.

App

Action

What it does

Google Sheets

Add new row

Adds a row to the spreadsheet and worksheet you choose. The columns come from the worksheet's header row, and you choose which trigger data fills each one.

HubSpot

Update contact property

Finds the HubSpot contact by email (usually Recipient Email) and sets one contact property to the value you choose. Hidden, calculated, and read-only properties aren't available.

Certifier

Issue credential

Issues a credential from the Credential Template you choose, using the trigger data for the recipient and attributes. This is the same action used with triggers from other apps, such as Zoom or HubSpot.

💡 Tip: Add a header row to your worksheet before you set up Add new row. Certifier uses it to show the columns you can fill.


Events That Only Count When the Recipient Does Them

Credential viewed, Credential shared, and Credential downloaded only start an automation when the recipient does them.

If someone else views, shares, or downloads the credential, for example, an employer checking it, the automation doesn't run. A webhook still fires in both cases.


Want to Learn More?

📓 Related articles:

If you still have questions, do not hesitate to contact us via the chat icon or email us directly: [email protected]

Did this answer your question?