Make Integration Guide

CertFusion is available as an app inside Make. Connect it once with an API token, then combine it with any other Make module to add recipients, issue certificates, and react to issued certificates automatically. This guide walks you through connecting the app, the modules it provides, a few ready-to-build scenarios, and how to fix common errors.

1. Overview

The CertFusion app for Make gives you two kinds of modules:

• Instant triggers start a scenario the moment something happens in CertFusion. Watch New Recipients fires when a recipient is added to one of your lists, and Watch Issued Certificates fires when a certificate has been generated and emailed. Both use webhooks, so there is no polling delay.
• Actions let a scenario do things in CertFusion: Create Recipient, Create Recipients (Bulk), Issue Certificate, Issue Certificates (Bulk), Get Recipient, Search Recipients, List Recipients, Delete Recipient, Get Quota, and a universal Make an API Call module for anything not covered by a dedicated action.

A typical scenario takes data from a form, spreadsheet, CRM, or LMS, creates a recipient on one of your certificate lists, and issues the certificate — all without opening CertFusion. Everything the app does is scoped to the account that owns the API token, and issuing certificates uses the same monthly quota as issuing from the dashboard.

2. How to Connect

1. In CertFusion, go to your account menu → API Token (or open the API tokens page directly). Click Generate new token, give it a name such as "Make", and copy the token. It is shown only once — if you lose it, generate a new one.
2. In Make, open the CertFusion app. While the app is in review, use the invite link https://www.make.com/en/hq/app-invitation/… — the full link is provided on request from our support page. Once the app is public it appears in Make's app list when you search for CertFusion, and no invite link is needed.
3. Add a CertFusion module to a scenario, click Add next to Connection, paste the token, and save. Make validates the token against CertFusion and the connection shows your account email when it is valid.

The connection is reused across all your scenarios. Revoking the token on the API tokens page immediately disconnects every scenario that uses it.

3. Modules

Module	Type	What it does	Returns
Watch New Recipients	Instant trigger	Fires when a recipient is added to a list (from the dashboard, an import, an integration, or the API).	The recipient, including list and design IDs, name, email, status, and custom fields.
Watch Issued Certificates	Instant trigger	Fires once a certificate has been generated and emailed.	The recipient with download_link, verify_link, and the issued timestamp.
Create Recipient	Action	Adds one draft recipient to a list. Custom fields for the selected list's design are loaded dynamically.	The created recipient and its ID.
Create Recipients (Bulk)	Action	Adds many draft recipients to a list in one call — ideal after an aggregator.	The created recipients and a count.
Issue Certificate	Action	Queues certificate generation and email delivery for a draft recipient.	The recipient with status processing.
Issue Certificates (Bulk)	Action	Queues issuance for a set of recipient IDs, or for every draft recipient on a list.	The recipients queued and a count.
Get Recipient	Action	Fetches a single recipient by ID — use it to poll for the issued status.	The recipient, with download and verify links once issued.
Search Recipients	Action	Finds recipients by email or name across your lists.	A bundle per matching recipient.
List Recipients	Action	Lists recipients on a list, optionally filtered by status, with pagination.	A bundle per recipient.
Delete Recipient	Action	Removes a recipient and its certificate.	A confirmation with the deleted ID.
Get Quota	Action	Reads your plan, monthly limit, certificates used, and remaining quota.	Quota figures you can branch on with a filter.
Make an API Call	Action	Calls any CertFusion API endpoint with your connection's token.	The raw HTTP response.

Every module that takes a list lets you pick it from a dropdown of your designs and lists, and the custom fields available for that list's design are shown as separate inputs.

4. Scenario Examples

A. Form response → certificate

Issue a certificate as soon as someone completes a quiz or feedback form in Typeform, Google Forms, or any other form app supported by Make.

1. Add the form app's trigger, for example Typeform → Watch Responses or Google Forms → Watch Responses.
2. Add CertFusion → Create Recipient. Choose the design and list, then map the form's name and email answers onto the Name and Email inputs. Map any other answers onto the design's custom fields (for example "Course" or "Score").
3. Add CertFusion → Issue Certificate and map the recipient ID from the previous module.
4. Optional: add a filter between steps 1 and 2 so that only passing scores continue.

B. Google Sheets rows → bulk issuance

Keep a spreadsheet of participants and let Make issue certificates for new rows in batches.

1. Add Google Sheets → Watch Rows on the sheet that holds your participants.
2. Add an Array Aggregator (Flow Control) and aggregate the rows into one bundle, selecting the name, email, and custom-field columns.
3. Add CertFusion → Create Recipients (Bulk), choose the list, and map the aggregated array onto the Recipients input.
4. Add CertFusion → Issue Certificates (Bulk) and map the recipient IDs returned by the previous module.
5. Schedule the scenario (for example every 15 minutes) so new rows are picked up automatically.

C. Issued certificate → Slack or email

Notify your team, or send your own follow-up email, whenever a certificate goes out.

1. Add CertFusion → Watch Issued Certificates as the trigger. Turning it on registers a webhook automatically (see Webhooks).
2. Add Slack → Create a Message and compose a message using the recipient's name, download_link, and verify_link from the trigger output — or add Gmail → Send an Email to the recipient's email with the same links.
3. Optional: add a Google Sheets → Add a Row module to keep an issuance log.

5. Webhooks

The instant triggers are powered by webhooks. Here is what happens behind the scenes:

• When you turn on Watch New Recipients or Watch Issued Certificates, Make registers a webhook subscription with CertFusion. You can see it under your account menu → API Token → Webhook subscriptions, along with its status and last delivery.
• Each delivery is signed. CertFusion sends an X-CertFusion-Signature header containing an HMAC-SHA256 of the raw request body, prefixed with sha256=, computed with the subscription's secret (returned once when the subscription is created). The Make app relies on its private webhook URL, so it does not check the header; if you point the same webhook events at your own endpoint, verify the signature before trusting the payload.
• If Make's endpoint answers with a server error, CertFusion retries the delivery with an increasing backoff.
• A subscription is disabled automatically after repeated failures, or straight away when Make responds with 410 Gone (which it does once the webhook is deleted on Make's side).
• Deleting the trigger — or the webhook in Make's Webhooks section — removes the subscription from CertFusion. Re-adding the trigger creates a fresh one.

6. Troubleshooting

401 Unauthorized

• The token was revoked on the API tokens page, or was pasted incompletely. Generate a new token and update the connection in Make.

422 "custom field not available"

• The custom field name must match one of the design's custom fields exactly. Use the dynamic field inputs shown in the module rather than typing field names by hand, and add the [custom.your_field] placeholder to the design first if it is missing.

422 quota, trial, or subscription errors

• The response includes a reason value explaining why issuance was refused — monthly quota exhausted, trial limits reached, or no active subscription. Check Get Quota or your billing page, then re-run the scenario.

409 already issued

• Issue Certificate only works on recipients in draft status. The recipient has already been issued or is being processed; use Get Recipient to see its current state.

Status is "processing"

• Issuance is asynchronous: the certificate is generated and emailed by a background job. Either wait for Watch Issued Certificates to fire, or poll Get Recipient until the status becomes issued and the download link is present.

No webhook received

• Check that the subscription is Active on the API tokens page. If it has been disabled after failures, delete the trigger in Make and add it again to create a new subscription.
• Make sure the scenario is switched on — a scenario that is off still owns its webhook but does not run.

---

Need help? Reach us from our support page.