Resources · Make integration

Okta Make integrationAutomate Okta with Make.

Can Make handle your Okta user admin without a line of code? The Okta Make integration gives you 6 modules: 1 instant trigger, 4 actions and 1 search, all centered on users. This guide is for IT and ops people who know Okta well and want a first working scenario.

Try the Okta integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Okta Make integration do for you?

The Okta Make integration links your Okta org to Make, a visual automation tool. You build a scenario (the automation itself, a chain of bricks called modules) that reacts to Okta events or reads, creates and updates Okta users for you. No code, just boxes you connect and fill in.

Onboarding without retyping. A new hire shows up in your HR form or spreadsheet, and Create a User opens the matching Okta account. The person arrives on day one with a login ready, and nobody copied a name by hand.

Profiles that stay current. When someone changes team or title elsewhere, Search Users finds them in Okta and Update a User writes the change. Both tools tell the same story.

Reacting to what happens in Okta. Watch New Events starts a scenario the moment Okta reports an event, so you can alert a channel or log it in a sheet. Run it once first to see what an event carries before you decide what comes next.

Keep the scope in mind: the Make app covers users. Groups, apps and policies have no dedicated module; if the Okta API offers what you need, Make an API Call reaches it with the same connection. If you are still judging the tool itself, the Make review gives the broader picture. Okta also has a node in n8n, described on the Okta n8n integration page, and n8n vs Make lays out the criteria to pick between the two.

Connect

How do you connect your Okta account to Make?

  1. 01

    Create an API token in Okta

    Log in to Okta and open Security > API > Token > Create a Token. Give the token a name you will recognize later, such as the scenario it serves, then click Create Token.

  2. 02

    Copy the token right away

    Copy the token to your clipboard, then click Ok, got it. Keep it at hand: the next step pastes it into Make.

  3. 03

    Fill in the connection in Make

    In any Okta module, click Create a connection. Type a Connection name, paste the token into API Token, enter your org name in Host, then click Continue. The connection is reused by every Okta module.

First scenario

Your first scenario: an Okta event, then a fresh look at your users

GoalEach time Okta reports a new event, Make runs Search Users and hands you the current list of your Okta users, one bundle per person.

  1. 01

    Start a blank scenario

    On the Scenarios page, create a new scenario. The editor opens on an empty canvas with a big +: click it to place the first module, the one that starts everything.

  2. 02

    Add Watch New Events

    Search for Okta, pick Watch New Events and click Create a connection, or pick the connection you already made. This is an instant trigger: Okta calls Make as soon as an event happens.

  3. 03

    Chain Search Users

    Click the + on the right of the trigger and add Okta Search Users and ask it to list all users. It needs nothing from the event, so the chain works whatever Okta sends.

  4. 04

    Test with Run once

    Click Run once, then cause an event in Okta. Open the bubble above each module to read the bundle it received (one bundle is one item passed along): the event on the trigger, one bundle per user on Search Users.

  5. 05

    Switch it on

    Once the test looks right, turn the scenario on. From then on each Okta event runs it. Every module that processes a bundle counts as one operation, the unit Make bills on your plan.

Triggers

What starts an Okta scenario

1 module starts a scenario when something happens in Okta. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Okta as soon as it happens.

Okta1Watch New Events

Watch New Events

Instant trigger

In Make“Triggers when a new event has occured.”

Watch New Events is the only Okta trigger in Make, and it puts your scenario on standby until Okta reports that something new occurred. Each event arrives as one bundle that the next modules can read.

How it fires
instant, Okta calls Make through a webhook as soon as the event happens, with no polling in between.
When to use it
when an Okta activity should set off a follow-up, like a message to the IT channel or a line added to an audit sheet.
Watch out
the Make documentation does not detail which event types reach it, so run a test with Run once and look at what arrives before building filters.
Modules

Everything Okta can do in a scenario

Okta gives you 5 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Users

4 modules
Okta1

Search Users

Search

In Make“Searches for users or lists them all.”

Search Users looks through your Okta directory and returns the people who match, or the whole list if you ask for it. Each person comes out as a separate bundle, so the modules after it run once per user.

When to use it
you only know a name or email from another tool and need the matching Okta account.
Watch out
a search can return zero, one or many users; add a filter if the next step must touch a single person.
Okta2

Get a User

Action

In Make“Gets a single user's info.”

Get a User fetches the complete record of one Okta user you already have a reference for. Think of it as opening a single profile card rather than browsing the directory.

When to use it
after Search Users hands you a user, and the next step needs more than what came along, for example the full profile for a ticket.
Watch out
it expects one precise user; to find someone by a loose criterion, run Search Users first.
Okta3

Create a User

Action

In Make“Creates a new user.”

Create a User opens a brand new account in your Okta org from data your scenario already holds. A signed offer in the HR tool, a row in the onboarding sheet: each one can become an Okta account without anyone logging in to the admin console.

When to use it
at the moment a hire is confirmed in the tool that holds their details.
Watch out
run Search Users before it when the same person might come through twice, so you do not end up with a duplicate.
Okta4

Update a User

Action

In Make“Updates user's profile and credentials.”

Update a User changes an existing Okta account, both the profile and the credentials. It keeps Okta aligned with whatever system holds the truth about a person, their title, their team, their details.

When to use it
when a change is recorded in your HR tool or CRM and Okta should mirror it without a manual edit.
Watch out
the module writes to one known user, so place Search Users or Get a User in front of it to pick the right account.

Other

1 module
Okta5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call sends any authorized request to the Okta API, using the connection you already set up. It is the escape hatch for what the user modules leave out, such as groups or apps, as long as the Okta API offers it.

When to use it
the action you need has no module of its own in the list above.
Watch out
here you write the request yourself from the Okta API reference, so test it with Run once before letting it touch real accounts.
Need help

Need help automating Okta with Make?

A person reads every message.

FAQ

Okta and Make: common questions

01Is the Okta Make integration free to use?
Yes, Okta is a standard app, so it works from the Make Free plan. The Free plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes per run. Usage counts in operations, one per module per bundle. Okta itself needs its own account, which Make does not provide.
02What does it take to connect Okta to Make?
You need an Okta account with access to the Security menu, because the connection relies on an API token. Create it under Security, API, Token, give it a name, and copy the value before closing the window. In Make, the connection asks for three things: a connection name, the API token and the host. The host is only your org name: for www.xyz.okta.com, type xyz. After that, every Okta module in your scenarios reuses that single connection.
03Does the Okta trigger in Make react in real time?
Yes. Watch New Events is an instant trigger: Okta calls Make through a webhook as soon as the event happens, instead of Make checking at intervals. That is why the module carries a lightning badge in the editor rather than a clock. Your scenario runs once per incoming event, and each run uses operations for every module that processes the bundle. The other five Okta modules are not triggers, they act when a scenario reaches them.
04What if the Okta module you need is missing?
It depends on the task, but there is usually a way. The Okta app in Make centers on users: search, get, create and update. Groups or apps have no module of their own. Make an API Call calls any endpoint of the Okta API with the connection you already have, so if the API offers it, you reach it without a second connection. The Okta documentation for Make lists no numeric limit, so the practical constraints are the ones of your Make plan.
05Make or n8n for Okta: which one fits?
It depends on how you prefer to build, since Okta is available in both. In Make, you get 6 Okta modules: one instant trigger on new events, one search, and four actions: three on users plus Make an API Call for everything else. n8n also offers an Okta node, with its own set of operations. The honest test is to list the Okta actions your process needs, check which tool covers them natively, and pick the editor your team is comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations