Automate Certifier With Make: 3 Modules, Zero Code Needed

What you can automate

What does the Certifier Make integration do?

The Certifier Make integration links your Certifier account to Make, so a scenario (the automation you build in Make, a chain of modules) can create groups and issue credentials for you. Something happens in another tool, and Certifier does its part without anyone copying names by hand.

Credentials that follow a completion. A learner finishes a course on your platform, the scenario receives the learner details, and Issue a Credential creates, issues and sends the credential to that person. Nobody exports a list at the end of the program.

A group ready before the first graduate. When a new session is opened in your planning tool, Create a Group adds the matching group in Certifier, so the next step of the scenario has somewhere to file what it issues.

Anything else the API offers. The module list is short. When the two dedicated modules stop short, Make an API Call lets you ask Certifier for anything else its API offers, with the same connection.

What Make does not give you here: a trigger. Certifier has no module that starts a scenario, so the flow always begins in another app or on a schedule. The Certifier documentation on Make also warns that it is AI-generated from the vendor's docs, so double-check anything critical with Certifier. To pick a plan, read Make pricing; to learn the editor properly, see Make training; and if you are weighing the other tool, n8n vs Make lays out the criteria.

Connect

How do you connect Certifier to Make?

01
Get your API key from Certifier
You need an active Certifier account and an API key before Make can talk to it. Sign in to Certifier, copy the key, and keep it at hand for the next step. No account yet? Create one on Certifier first.
02
Add a Certifier module and open the connection
In your Make scenario, add any Certifier module and click Create a connection. A connection is your Certifier account linked to Make once, then reused by every Certifier module you add later.
03
Name it and paste the key
The Connection name field is optional, but a clear name helps when several accounts coexist. Paste the credentials copied from Certifier, or follow the on-screen instructions, then save.

First scenario

Your first scenario with Certifier

GoalWhen someone completes a course in another app, Make issues and sends their Certifier credential.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to place the first module. Since Certifier has no trigger, this first module comes from the app where completions happen.
02
Pick the starting app
Search that app by name, choose its module, and connect it with Create a connection. Each completion it passes along becomes a bundle, one item that flows to the next module.
03
Add Issue a Credential
Click the + on the right of the first module, search Certifier and pick Issue a Credential. Use your Certifier connection, then map the recipient from the data the first module received.
04
Test with Run once
Click Run once to run the scenario a single time. Open each module to read the bundles it received and confirm the right person got the credential before going further.
05
Schedule and switch on
Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. From now on, each completion flows to Certifier without a manual export.

Modules

What the Certifier modules do

Certifier gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Certifier1

Create a Group

Action

In Make“Creates a group.”

This module gives you a new group in your Certifier account straight from the scenario, so a program or session exists in Certifier before anyone needs a credential from it.

When to use it

a new session is opened in your planning tool and you want Certifier to mirror it without a manual setup step.

Watch out

the module runs once per bundle it receives, so feed it one item per session or you will end up with duplicate groups.

Certifier2

Issue a Credential

Action

In Make“Creates, issues, and sends a credential to a recipient.”

Here is the module that delivers the result people wait for: it creates the credential, issues it and sends it to the recipient in a single step. Each run counts as one operation, one execution that Make counts on your plan.

When to use it

right after the step that confirms a completion, a passed exam or an attended event.

Watch out

sending is part of the action, so test with your own address under Run once before real learners are mapped in.

Certifier3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module lets you ask Certifier for anything its API offers, using the connection you already set up. It covers what Create a Group and Issue a Credential leave out.

When to use it

you need an operation of the Certifier API that neither dedicated module offers.

Watch out

you write the request yourself, so keep the Certifier API documentation open and verify the endpoint there, as the Make page on Certifier is AI-generated.

Need help

Need help automating Certifier with Make?

A person reads every message.

FAQ

Questions about the Certifier Make integration

01Is the Certifier Make integration free?

Yes, on the Make side. Certifier is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and lift the active scenario cap. Certifier itself needs an active account with API access, and its own subscription is set by Certifier, not by Make.

02What is needed to connect Certifier to Make?

An active Certifier account and an API key. Once you have them, add any Certifier module to a scenario, click Create a connection, optionally give the connection a name, and paste the credentials copied from Certifier. The connection is then shared by all three Certifier modules, so you only do this once per account. If the connection is refused, check the account status and the key in Certifier before looking at the scenario.

03Does Certifier react in real time in Make?

No, because Certifier has no trigger in Make: all three of its modules are actions. The scenario starts elsewhere. Either another app provides the trigger, instant if that app notifies Make by webhook, scheduled if Make checks it on a clock, or the scenario itself runs on a schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan. Certifier then acts at whatever pace that first module sets.

04What if a Certifier module is missing in Make?

Use Make an API Call. It calls any endpoint of the Certifier API with the connection you already have, so an operation missing from Create a Group and Issue a Credential is still within reach. You write the request yourself from the Certifier API reference. Keep in mind that the Certifier documentation on Make is AI-generated from the vendor's docs and may contain mistakes, so confirm important details with Certifier directly.

05Should Certifier be automated with Make or n8n?

It depends on criteria, not on a winner. On Make, Certifier comes with three modules, one of which, Make an API Call, opens the whole API. Check whether n8n offers a Certifier node before comparing, then look at where your other tools already live, who will maintain the scenarios, and how your team prefers to build. The n8n vs Make comparison linked above goes through these points one by one without ranking either tool.

Get your API key from Certifier

Add a Certifier module and open the connection

Name it and paste the key

Create the scenario

Pick the starting app

Add Issue a Credential

Test with Run once

Schedule and switch on

Need help automating Certifier with Make?