Resources · Make integration

Procertif Make integrationAutomate Procertif with Make.

Can Make issue and track Procertif certificates for you? The Procertif Make integration gives you 4 modules: 3 triggers that watch certificates and sequencing events, plus 1 action that issues a certificate. This page walks HR and training teams through the connection and a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Procertif Make integration let you automate?

The Procertif Make integration links your Procertif account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule. Each module is one brick of that chain. With Procertif you get 3 scheduled triggers and 1 action, so Make can react to certificate activity or create certificates for you.

Certificates issued from another tool. Someone completes a step recorded in a different app, and Issue a Certificate creates the Procertif certificate without anyone retyping names. This is the scenario built step by step further down.

A record of every issued certificate. Watch Issued Certificate hands each new certificate to the next module, so you can copy it into a sheet, a CRM or a chat message for the people who need to know.

Follow-up on registrations and sequences. Watch Registered Certificate and Watch New Sequencing Events start a scenario from the other side of the workflow; the documentation does not describe either, so test them with Run once before building on them.

Know the limits up front: Make's own documentation for Procertif is marked as limited, with no field list and no official description of the modules. There is no Make an API Call module either. If you want a second opinion on the platform, read our Make review, and if you weigh it against another tool, the n8n vs Make comparison lays out the criteria. Teams that prefer to hand the build over can talk to our Make agency.

Connect

How do you connect Procertif to Make?

  1. 01

    Add a Procertif module

    In your scenario, click the + and search for Procertif, then pick any of its modules. A panel opens with a Create a connection button: click it. The connection is your Procertif account linked to Make once, then reused by every Procertif module.

  2. 02

    Name the connection

    Giving the connection a name is optional, but a clear label such as the account owner or the workspace helps later, when several people build scenarios in the same Make team and need to pick the right account.

  3. 03

    Authorize and save

    Make then asks you either to authorize access on the Procertif page or to paste the key Procertif gives you. The documentation does not say which one applies here. Complete whichever screen appears, then click Save.

First scenario

Your first scenario: Procertif issues a certificate by itself

GoalWhen a new entry lands in another app, Make issues the matching certificate in Procertif.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that holds your source data, for instance the form or sheet where completions are recorded.

  2. 02

    Set up the source module

    Connect that app and fill its fields. Once the connection exists, Make lists the sheets or objects it can read, so you choose from a menu instead of typing paths.

  3. 03

    Add Issue a Certificate

    Click the + on the right of the first module, search for Procertif and choose Issue a Certificate. Create the connection, then map the data coming from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one person. Check the certificate in Procertif.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; the Free plan cannot go below that, paid plans go down to 1 minute. Then switch the scenario on.

Triggers

Procertif triggers in Make

3 modules start a scenario when something happens in Procertif. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Procertif as soon as it happens.

Procertif1Watch Issued Certificate

Watch Issued Certificate

triggerIn the docs only

Start a scenario from certificates that have already gone out: judging by its name, this trigger picks up certificates issued in Procertif and passes each one to the next module as a bundle. Make's documentation gives no description, so confirm what it returns with a first test.

How it fires
scheduled, Make checks Procertif on the scenario's schedule, not the moment a certificate appears.
When to use it
to log each issued certificate in a shared sheet or post a note to the team that follows learners.
Watch out
run it once and read the bundle before mapping fields, since no field list is published.
Procertif2Watch New Sequencing Events

Watch New Sequencing Events

triggerIn the docs only

Going by its name, this trigger gets you a feed of the sequencing events Procertif records, each arriving in Make as its own bundle. What counts as a sequencing event is not explained in the documentation, so treat that as something to check inside your Procertif account first.

How it fires
scheduled, Make queries Procertif each time the scenario's schedule comes round.
When to use it
when your process in Procertif runs in ordered stages and another tool has to hear about each new one.
Watch out
every event processed by every module costs operations, the unit Make counts on your plan.
Procertif3Watch Registered Certificate

Watch Registered Certificate

triggerIn the docs only

You get a scenario that starts from the registered side of Procertif: going by its name, this trigger returns certificates marked as registered. The documentation does not say how registered differs from issued, so compare both triggers with a test before choosing.

How it fires
scheduled, Make polls Procertif on the scenario's schedule and collects what is new since the last check.
When to use it
when registration is the moment that matters to you, for example to update a record in your HR tool.
Watch out
the clock badge means a delay up to the schedule interval, never an instant reaction.
Modules

What the Procertif action does

Procertif gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Procertif1

Issue a Certificate

ActionIn the docs only

Issue a Certificate saves you from creating certificates by hand, using the data mapped from earlier modules. It is the only action of the app, so any write to Procertif goes through it.

When to use it
right after the module that tells you a person qualifies, such as a new row, a form answer or a status change in another tool.
Watch out
test with a dummy person first, because the documentation does not describe how a certificate issued by mistake can be undone.
Need help

Need help automating Procertif with Make?

A person reads every message.

FAQ

Procertif and Make: common questions

01Is the Procertif Make integration free?
Yes, on the Make side. Procertif is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift the active scenario limit, allow runs every minute and count usage in credits per month. Your Procertif subscription is a separate matter that this page does not cover.
02What do you need to connect Procertif to Make?
A Procertif account and a Make account. The documentation lists no specific prerequisite, so you follow the generic Make steps: add a Procertif module, click Create a connection, optionally name it, then either authorize Make on the Procertif page or paste the key Procertif provides, and click Save. Because the documentation for this app is marked as limited, ask your Procertif administrator which access your account has if the connection is refused.
03Do Procertif triggers in Make fire in real time?
No. All 3 Procertif triggers are scheduled, which means Make checks Procertif on the scenario's schedule rather than being told the moment something happens. A new scenario runs every 15 minutes by default. On the Free plan that is also the shortest interval; paid plans can go down to 1 minute. One caveat: Make's app directory was unavailable, so these types are deduced from the module names. Check for the clock badge on each trigger when you add it.
04What if the Procertif module you need is missing in Make?
It depends on what you need. Procertif offers 4 modules in Make and no Make an API Call module, so you cannot reach other parts of the Procertif API from inside the app. The documentation is also marked as limited. You can often rework the scenario so the missing step happens in another app, or ask a Make specialist to look at your case and suggest a workable route before you commit to a design.
05Should you use Make or n8n for Procertif?
It depends on your criteria rather than on a winner. In Make, Procertif gives you 3 scheduled triggers and 1 action, usable from the Free plan with the limits of that plan. Whether an equivalent n8n node exists for Procertif is not something this page confirms, so check that first. Then compare the two tools on the points that matter to your team: available modules, how runs are counted and who will maintain the scenario. The n8n vs Make comparison on this site sets out those criteria.