Sertifier + Make Integration

This guide walks you through setting up an integration between Sertifier and Make to automate your credentialing workflows.

This integration is especially useful if you want to:

• Automate credential issuance based on events in other apps (e.g., form submissions, course completions, or CRM updates).

• Sync recipient data between Sertifier and tools like Google Sheets, HubSpot, or Airtable.

• Save time by running your credentialing process end-to-end through one automated workflow.

1. Prerequisites

Before you begin, you will need two items from your Sertifier account:

1. Your API Key: You can find this in your Sertifier dashboard under Settings > API & Integrations.
2. Your Campaign ID: This is the unique ID for the specific campaign you want to use for issuing certificates.

2. Configuration in Make

1. Set Your Trigger: In your new Make scenario, set up the trigger that will start the workflow (e.g., a new row in Google Sheets, a form submission, etc.). This step should provide the recipient's name and email.
2. Add the HTTP Module: Add a new module to your scenario, search for HTTP, and select the "Make a request" action.
3. Configure the HTTP Module: Fill in the fields with the following details:
   • URL: https://b2b.sertifier.com/campaign/addCredentials
   • Method: POST
   • Headers: Add three separate headers:
     • Content-Type | application/json
     • api-version | 3.3
     • secretKey | Paste your Sertifier API Key here
   • Body type: Raw
   • Content type: JSON (application/json)
   • Request content: Copy and paste the JSON structure below. Be sure to replace "YOUR_CAMPAIGN_ID" with your actual Campaign ID and map the name and email values from your trigger module.

JSON

{

    "campaignId": "YOUR_CAMPAIGN_ID",

    "credentials": [

        {

            "name": "map_name_from_trigger",

            "email": "map_email_from_trigger",

            "quickPublish": true

        }

    ]

}

3. One-time prep inside Sertifier

• If you already have a fixed catalog (course ↔ campaign), just reference the stored campaignId for each course.
• If your catalog is dynamic, you can create the campaign on the fly (using AddCampaign) and then immediately call Campaign/AddCredentials with the returned campaignId.