Resources · Make integration

KnowBe4 Make integrationAutomate KnowBe4 with Make.

Security awareness gets easier when KnowBe4 follows your HR tool on its own. The KnowBe4 Make integration gives you 36 action modules for users, groups, training and phishing campaigns. This guide shows IT and security teams how to connect the account and build a first working scenario.

Try the KnowBe4 integration on MakeSee the 36 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the KnowBe4 Make integration do for you?

The KnowBe4 Make integration links your KnowBe4 account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as an action on one app. Here, those bricks create users, sort them into groups and drive training or phishing campaigns, based on what happens in your other tools.

Onboarding without a checklist. A new row in your HR app starts the scenario, Get a User by Email checks the account, Create a User fills the gap, and Add User to Training Campaign enrolls the person.

Clean offboarding. When a departure is recorded, Archive User(s) and Remove User(s) from Group take the person out of the active setup, so the user list matches reality.

Reporting outside the console. Get a list of phishing campaign runs and Get a list of training enrollments send their data to a spreadsheet or a chat channel that managers already read.

One limit shapes every scenario: KnowBe4 has no trigger module in Make. The flow starts from another app, or from the schedule you set on the first module. If you are new to the editor, the Make training walks through these basics, and Make pricing explains how operations are counted. The same app often has an n8n node too; the n8n vs Make comparison helps you pick a tool on your own criteria.

Connect

How do you connect KnowBe4 to Make?

  1. 01

    Create a Reporting API token

    In KnowBe4, click your email address at the top right, open Account Settings, then Account Integrations and API. Switch on Report API Access under Reporting API, open the Reporting API subtab and click Create New API Token.

  2. 02

    Name, enable and copy the token

    Give the token a descriptive name in the Name field, make sure Status is set to enabled, then click Create Token. Copy the key shown in the Reporting API Token pop-up before closing it.

  3. 03

    Add the connection in Make

    Add any KnowBe4 module to your scenario and click Create a connection. A connection is your KnowBe4 account linked to Make once, then reused by every KnowBe4 module. Name it if you like, paste the key and save.

First scenario

Build your first scenario with KnowBe4

GoalWhen a new hire appears in your HR app, Make finds that person in KnowBe4 and enrolls them in a training campaign.

  1. 01

    Start from the app that knows first

    On the Scenarios page, create a new scenario and click the +. Pick the module of the HR app or form where new employees are recorded, since KnowBe4 has no trigger of its own.

  2. 02

    Look the person up

    Click the + on the right, search KnowBe4 and choose Get a User by Email. Create the connection, then map the email address from the previous module into it.

  3. 03

    Enroll them in training

    Add Add User to Training Campaign next. Once the connection exists, Make lists what it can read in your account, so pick the campaign and map the user returned by the lookup.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module to read the bundles it received, a bundle being one item passed along, here one person.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What the 36 KnowBe4 modules do

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

KnowBe41

Add User to Training Campaign

ActionIn the docs only

Puts one person into a KnowBe4 training campaign straight from your scenario, so nobody has to open the console to enroll them by hand.

When to use it
a new employee record appears in your HR app and security awareness training should start at once.
Watch out
look the person up first with Get a User by Email so this module receives the right account.
KnowBe42

Add User(s) to Group(s)

ActionIn the docs only

Drops one or several users into one or several KnowBe4 groups in a single step, which keeps group membership aligned with the rest of your stack.

When to use it
someone changes department in your directory and should inherit that team's campaigns.
Watch out
several users and several groups can meet here, so check the mapping with Run once before it touches many accounts.
KnowBe43

Archive Group(s)

ActionIn the docs only

Takes groups you no longer use out of your active KnowBe4 setup, so reports and targeting lists stay readable.

When to use it
a project team or an office closes and its group should stop showing up among current teams.
Watch out
Archive and Delete are two separate modules; if you are not sure the group is gone for good, pick this one over Delete Group(s).
KnowBe44

Archive User(s)

ActionIn the docs only

Moves departed people out of your active KnowBe4 user list, so the list reflects who actually works for you today.

When to use it
an offboarding event in your HR tool marks the last day of an employee.
Watch out
archive the account you found with Get a User by Email, not a name typed by hand, to avoid hitting the wrong person.
KnowBe45

Close a Training Campaign

ActionIn the docs only

Ends a KnowBe4 training campaign from a scenario once its purpose is served, without a trip to the console.

When to use it
the audit or onboarding wave the campaign was built for is signed off in your project tool.
Watch out
closing and deleting are different modules, so decide which one you mean before you map the campaign.
KnowBe46

Create a Group

ActionIn the docs only

Creates a new KnowBe4 group from data another app already holds, so your groups follow your org chart instead of lagging behind it.

When to use it
a new team, site or client account is created in your CRM or directory.
Watch out
if your scenario can fire twice for the same team, check Get a Group List first so you do not end up with two groups under one name.
KnowBe47

Create a Phishing Campaign

ActionIn the docs only

Sets up a new KnowBe4 phishing simulation campaign from a scenario, handy when campaign creation follows an event elsewhere.

When to use it
a new group has just been created and should get its own simulated phishing program.
Watch out
a phishing campaign is aimed at real colleagues, so try the scenario on a small test group before mapping real ones.
KnowBe48

Create a Training Campaign

ActionIn the docs only

Opens a new KnowBe4 training campaign without leaving your scenario, so the course assignment starts from the event that justifies it.

When to use it
a compliance project or a new client contract calls for a dedicated awareness program.
Watch out
build it once with Run once and look at the result in KnowBe4 before switching the scenario on.
KnowBe49

Create a User

ActionIn the docs only

Adds a person to KnowBe4 from the app where they first appear, so new hires are covered without a manual import.

When to use it
a signed offer or a new row in your HR tool marks an arrival.
Watch out
check with Get a User by Email first; if the address already exists, route the scenario to Edit a User instead of creating a duplicate.
KnowBe410

Deactivate a Phishing Campaign

ActionIn the docs only

Turns a KnowBe4 phishing campaign off from a scenario, the move to make when simulations should pause.

When to use it
a real security incident is being handled and a simulated email would only add noise.
Watch out
this is not Stop a Phishing Campaign Run, which targets one run of a campaign; pick the module that matches what you want to halt.
KnowBe411

Delete Group(s)

ActionIn the docs only

Removes one or several KnowBe4 groups, the cleanup step for structures that no longer mean anything.

When to use it
a merger or a reorganization retires teams, and their groups only clutter the console.
Watch out
plan as if a deletion cannot be undone, and test it with Run once on a throwaway group before mapping real ones.
KnowBe412

Delete Training Campaign(s)

ActionIn the docs only

Clears one or several training campaigns out of KnowBe4, so your campaign list only shows programs people still follow.

When to use it
test campaigns created while you built the scenario need to disappear.
Watch out
treat it as final; if you only want a campaign to end, Close a Training Campaign is the module to look at first.
KnowBe413

Delete a Phishing Campaign Run

ActionIn the docs only

Erases a single run of a phishing campaign rather than the campaign itself, which helps when one send went out wrong.

When to use it
a run was launched against the wrong group and its results would mislead your follow-up.
Watch out
get the right run first with Get a list of phishing campaign runs, and assume the deletion is permanent.
KnowBe414

Edit a Phishing Campaign

ActionIn the docs only

Updates an existing KnowBe4 phishing campaign from outside the console, so it keeps up with changes made elsewhere.

When to use it
a team is renamed or merged and the campaign built for it should reflect the new setup.
Watch out
fetch the campaign with Get a Phishing Campaign before editing, so you change the one you meant to change.
KnowBe415

Edit a Training Campaign

ActionIn the docs only

Changes a training campaign that already exists, which saves rebuilding it when the scope moves.

When to use it
a policy update in your document tool means the current awareness campaign needs adjusting.
Watch out
run Get a list of training campaigns first when several campaigns look alike, then map the exact one into this module.
KnowBe416

Edit a User

ActionIn the docs only

Keeps a KnowBe4 user record in step with your source of truth, such as an HR tool or a directory.

When to use it
a person changes team or name, and the change should reach KnowBe4 without anyone retyping it.
Watch out
find the account first with Get a User or Get a User by Email, since editing needs to know which user you mean.
KnowBe417

Get a Enrollment

ActionIn the docs only

Reads one training enrollment, meaning one person's place in one training campaign, so a later module can act on it.

When to use it
a manager asks about one employee's training and your scenario posts the answer in a chat channel.
Watch out
this reads a single enrollment; for many at once, Get a list of training enrollments fits better.
KnowBe418

Get a Group

ActionIn the docs only

Fetches one KnowBe4 group so its details can feed the next modules of your scenario.

When to use it
before adding users or launching a campaign, you want to confirm the group exists and reuse its exact data.
Watch out
it targets one group only; to browse all of them and pick one, start with Get a Group List.
KnowBe419

Get a Group List

ActionIn the docs only

Brings back the groups of your KnowBe4 account, the starting point for any scenario that goes through teams one by one.

When to use it
you want a spreadsheet with every group, refreshed each time the scenario runs.
Watch out
every module run counts as an operation on your Make plan, so keep the steps after a list lean.
KnowBe420

Get a Phishing Campaign

ActionIn the docs only

Pulls the details of one phishing campaign into your scenario, ready to be mapped or sent elsewhere.

When to use it
a security lead wants a campaign summary pushed into a ticket or a team channel.
Watch out
to see which campaigns exist in the first place, run Get a list of phishing campaigns and pass along the one you need.
KnowBe421

Get a Phishing Campaign Run

ActionIn the docs only

Reads one run of a phishing campaign rather than the whole campaign, so you can report on that specific send.

When to use it
a run has ended and its data should land in the sheet your security committee reviews.
Watch out
a campaign and a run are different things; this module works on the run, Get a Phishing Campaign on the campaign.
KnowBe422

Get a Training Campaign

ActionIn the docs only

Returns one training campaign so its data can drive the rest of the scenario.

When to use it
an auditor asks about a given program and you want its details copied into a shared document.
Watch out
pair it with Get a list of training enrollments when the question is about people rather than about the campaign itself.
KnowBe423

Get a User

ActionIn the docs only

Looks up one KnowBe4 user so the modules that follow work on a known account.

When to use it
a ticket in your help desk mentions a colleague and you want their KnowBe4 record attached to it.
Watch out
when all you have is an email address, Get a User by Email is the more direct route to the same person.
KnowBe424

Get a User by Email

ActionIn the docs only

Finds a KnowBe4 user from an email address, the key almost every other business app shares.

When to use it
in most scenarios that start in an HR, CRM or ticketing tool, right before editing, archiving or enrolling someone.
Watch out
plan for the case where no user matches the address, otherwise the next module receives nothing to work on.
KnowBe425

Get a list of phishing campaign recipients for a campaign run

ActionIn the docs only

Shows who received a given phishing campaign run, which turns a run into a person-by-person view.

When to use it
people who got the simulation should receive a follow-up message or a short refresher.
Watch out
it works on one run, so place Get a list of phishing campaign runs or Get a Phishing Campaign Run before it.
KnowBe426

Get a list of phishing campaign runs

ActionIn the docs only

Returns the runs of your phishing campaigns, handy for spotting the one you want to read, stop or delete.

When to use it
a scenario feeds a dashboard that should list every run KnowBe4 holds.
Watch out
a list can bring back many items, so test with Run once and count the bundles before adding extra steps.
KnowBe427

Get a list of phishing campaigns

ActionIn the docs only

Gives you the phishing campaigns of the account, the entry point when a scenario has to go through them one by one.

When to use it
you are building a reporting sheet that mirrors every campaign in KnowBe4.
Watch out
add Get a Phishing Campaign after it only if the list lacks the data you need, since each extra module costs operations.
KnowBe428

Get a list of store purchases

ActionIn the docs only

Retrieves what your account has bought in the KnowBe4 store, so your content inventory can live outside the console.

When to use it
the training lead wants a sheet of purchased content to plan the next campaigns with.
Watch out
this module reads data; it buys nothing and changes nothing, so it is safe to test with Run once.
KnowBe429

Get a list of template topics

ActionIn the docs only

Reads the template topics available to you, useful to see which themes your campaigns can draw on.

When to use it
you are planning a campaign around a theme and want the options in a shared doc where the team can comment.
Watch out
it returns topics, not ready campaigns; keep it for planning rather than for launching anything.
KnowBe430

Get a list of training campaigns

ActionIn the docs only

Brings every training campaign into the scenario, so you can go through them or copy them into another tool.

When to use it
your compliance tracker should mirror which awareness programs exist in KnowBe4.
Watch out
to act on one campaign, pass it to Edit a Training Campaign or Close a Training Campaign rather than rebuilding the lookup.
KnowBe431

Get a list of training enrollments

ActionIn the docs only

Pulls training enrollments in bulk, the source for any report on who has been assigned which course.

When to use it
managers want a sheet of their team's enrollments ahead of an audit.
Watch out
a large account can return many bundles, and each module that processes them adds operations, so test with Run once first.
KnowBe432

Get a list of users

ActionIn the docs only

Returns the users of your KnowBe4 account, the base for syncing or comparing them with your directory.

When to use it
you want to spot accounts that exist in KnowBe4 but no longer exist in your HR tool.
Watch out
comparing two lists usually needs more modules downstream, so sketch the whole flow before building it.
KnowBe433

Make an API call

ActionIn the docs only

Calls any endpoint of the KnowBe4 API with the connection you already set up, for everything the dedicated modules do not cover.

When to use it
you need a KnowBe4 feature that has no module of its own in Make.
Watch out
you work with the API directly here, so keep the KnowBe4 API documentation open while you fill in the request.
KnowBe434

Remove User(s) from Group

ActionIn the docs only

Takes one or several users out of a KnowBe4 group, the mirror of Add User(s) to Group(s).

When to use it
someone leaves a team in your directory and should stop inheriting that team's campaigns.
Watch out
map the users from a lookup module rather than typed names, so the right people leave the group.
KnowBe435

Remove a User from a Training Campaign

ActionIn the docs only

Withdraws one person from a training campaign without touching the campaign for everyone else.

When to use it
an employee goes on leave, or was enrolled in the wrong program by mistake.
Watch out
if the person leaves the company for good, Archive User(s) may be the step you actually want.
KnowBe436

Stop a Phishing Campaign Run

ActionIn the docs only

Halts a phishing campaign run that is underway, the emergency brake when a send goes wrong.

When to use it
your help desk sees a wave of people treating the simulation as a real attack and you want it to stop.
Watch out
it stops one run; to switch off the campaign as a whole, use Deactivate a Phishing Campaign.
Need help

Need help automating KnowBe4 with Make?

A person reads every message.

FAQ

KnowBe4 and Make: frequent questions

01Is the KnowBe4 Make integration free?
Yes, on the Make side. KnowBe4 is a standard app, so it works from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits per month. You still need an active KnowBe4 account; its subscription is set by KnowBe4 on its own pricing page, not by Make.
02What do you need to connect KnowBe4 to Make?
An active KnowBe4 account and a Reporting API token. In KnowBe4, open Account Settings, then Account Integrations and API, switch on Report API Access, and create a new token from the Reporting API subtab with its Status set to enabled. Copy the key from the pop-up. In Make, add any KnowBe4 module, click Create a connection, give it a name if you want and paste the key. Every KnowBe4 module then reuses that same connection.
03Can the KnowBe4 Make integration react in real time?
Not on its own. KnowBe4 has no trigger module in Make, scheduled or instant, so the scenario has to start somewhere else. Two options: open the scenario with the trigger of another app, such as the HR tool where new hires are recorded, or run it on the schedule of the first module, every 15 minutes by default and never under 15 minutes on the Free plan. The speed then depends on that first module, not on KnowBe4.
04What if a KnowBe4 module is missing in Make?
Use Make an API call. It reaches any endpoint of the KnowBe4 API with the connection you already created, so a feature without a dedicated module is still within reach of your scenario. Keep in mind that the Make documentation for this app states it was generated with AI from the official KnowBe4 documentation and may contain mistakes, so check anything important against the KnowBe4 documentation itself, or ask KnowBe4 directly when a detail matters.
05Should you use Make or n8n for KnowBe4?
It depends on the tool your team already runs. In Make, KnowBe4 comes with 36 action modules, Make an API call included, all sharing one connection, and scenarios start from another app or from a schedule because there is no KnowBe4 trigger. The same app often has an n8n node as well. Compare the modules each tool offers against the jobs you need done, such as onboarding, offboarding or reporting, and pick the one that covers them.
Same platform

Other docs you might need on this stack.

Browse all integrations