Resources · Make integration

Issue Badge Make integrationAutomate Issue Badge with Make.

Can a badge go out without anyone clicking a button? The Issue Badge Make integration gives you 2 action modules, and this guide shows how to plug them into the apps you already run, connect your account and test a first scenario.

Try the Issue Badge integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Issue Badge Make integration do for you?

The Issue Badge Make integration lets a Make scenario (the automation you build, a chain of steps) hand a badge to a member for you. Something happens in another tool, Make picks it up, and the badge is issued without a manual step. There are 2 modules, both actions, so another app or a schedule always starts the flow.

Badges that follow a finished course. A training team can let its course platform start the scenario, then use Issue a Badge to a Member so the learner is rewarded once the course is marked done, as soon as your trigger picks it up.

Recognition tied to a form. An event organizer can start from a check-in form in another app and issue the attendance badge right after, with no spreadsheet to reconcile later.

Anything the listed module does not cover. When you need another part of the Issue Badge API, Make an API Call reuses the same connection, so you stay in one scenario.

Be aware of one limit: Make says its own documentation for Issue Badge is incomplete, because little public information exists about the app. Test each module with care. If a run fails, the Make troubleshooting guide covers the usual causes, and the n8n vs Make comparison helps if you are still choosing a tool. For a guided start, see our Make training.

Connect

How do you connect Issue Badge to Make?

  1. 01

    Add an Issue Badge module

    In your scenario, add Issue a Badge to a Member, then click Create a connection. A connection is your Issue Badge account linked to Make once and reused by every Issue Badge module.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as the workspace or team it belongs to. This step is optional, but it helps when several people share the same Make organization.

  3. 03

    Authorize and save

    Depending on what Issue Badge asks for, either approve Make on the Issue Badge page or paste the key the app gives you. Then click Save and the module is ready to fill.

First scenario

Your first scenario with Issue Badge

GoalWhen a member completes something in another app, Make issues them a badge in Issue Badge.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. That first spot goes to the app where the event happens.

  2. 02

    Pick the starting app

    Search for the app that knows when a member earns the badge, choose its trigger and connect it. Issue Badge has no trigger of its own, so this module starts the flow.

  3. 03

    Add the badge module

    Click the + on the right of the first module, search for Issue Badge and pick Issue a Badge to a Member. Connect your account as shown above.

  4. 04

    Map the member

    Fill the module fields using data from the first module. Each bundle (one item passed along, here one member) gets its own badge, and Make lists the options it can read once connected.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and confirm the right member got the badge.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on it runs without you watching.

Modules

What the Issue Badge modules do

Issue Badge gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Issue Badge1

Issue a Badge to a Member

ActionIn the docs only

You get a badge in a member's hands without opening Issue Badge: this action takes the member sent by the previous step and issues the badge to them.

When to use it
right after the moment that earns recognition, such as a course marked complete or an attendance confirmed in another app.
Watch out
an action works on one bundle at a time, so a list of ten members means ten badges and ten operations counted on your plan.
Issue Badge2

Make an API Call

ActionIn the docs only

This module opens the rest of the Issue Badge API to your scenario, using the connection you already created, so you are not limited to the single badge action.

When to use it
when you need an operation that Issue a Badge to a Member does not offer.
Watch out
Make's documentation for Issue Badge is incomplete, so check the endpoint on the Issue Badge side and test the call with Run once before activating.
Need help

Need help automating Issue Badge with Make?

A person reads every message.

FAQ

Questions about Issue Badge and Make

01Is the Issue Badge Make integration free?
Yes, Issue Badge is a standard app in Make, so it works on the Free plan. That plan has real limits: 2 active scenarios, at least 15 minutes between two 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) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, one operation per module run on one bundle. Any price Issue Badge itself charges is a separate matter that this page does not cover.
02What do you need to connect Issue Badge to Make?
An Issue Badge account and a Make account. Make does not publish any specific prerequisites for this app, so the generic flow applies: add an Issue Badge module, click Create a connection, optionally give it a name, then either authorize Make on the Issue Badge page or paste the key the app provides, and save. The connection is created once and reused by both modules. Since Make itself says its documentation for Issue Badge is limited, ask Issue Badge which credentials to use if the authorization step is unclear.
03Can Issue Badge start a Make scenario by itself?
No, not with the modules listed today. Issue Badge has no trigger in Make, only 2 actions, so something else has to launch the scenario. Two options work. Put a trigger from another app first, for example the tool where members complete a course or register. Or run the scenario on a schedule set on its first module, every 15 minutes by default and never more often than every 15 minutes on the Free plan. The badge is then issued during that run, not the instant the event happens in the other app.
04What if a module you need is missing from Issue Badge on Make?
Use Make an API Call. This module can reach any endpoint of the Issue Badge API from your scenario with the connection you already set up, so it covers what Issue a Badge to a Member does not. The catch is documentation: Make states it cannot provide complete guides for Issue Badge because too little public information exists. Look up the endpoint on the Issue Badge side, send one test with Run once, and read the returned bundle before switching the scenario on.
05Should you use Make or n8n for Issue Badge?
It depends on where the rest of your automations already live. Make gives you 2 ready modules for Issue Badge plus the API call, and the editor lets you chain them with thousands of other standard apps without writing code. If your team already builds its workflows in n8n, check whether an Issue Badge node exists there before switching tools. Neither choice is wrong by default: pick the platform your team maintains every day, so your badge flows sit next to the automations that feed them.
Same platform

Other docs you might need on this stack.

Browse all integrations