Resources · Make integration

OAD Make integrationAutomate OAD with Make.

Can Make pull your OAD data into the rest of your stack? The OAD Make integration gives you 5 modules: 3 searches, 2 actions. This page shows who it suits, how to link your account with an API key, and how to build a first scenario step by step.

Try the OAD integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OAD Make integration do for you?

The OAD Make integration lets Make read your OAD account: it finds candidates, teams and team members, reports your billing credits, and calls the OAD API for anything else. A scenario (the automation you build in Make) chains these modules with other apps, without a line of code.

A candidate lookup on demand. Another app sends a name or an email, Search Candidates finds the matching records in OAD, and the next module passes them to your spreadsheet or chat tool. Each record arrives as a bundle, one item flowing from module to module.

A team directory that stays in sync. Search Teams returns your teams, Search Team Members returns the people, and a later module copies both into the tool your managers already open.

A credit check before you spend. Get Billing Credits reads the credits left on your account, so a scenario can warn someone in time. When a need falls outside these modules, Make an API call reaches the rest of the OAD API with the same connection.

Two limits to know. OAD has no trigger in Make, so a scenario starts on a schedule or on another app's event, never on something that happens in OAD. And Make's documentation page for OAD states it was generated by AI from OAD's docs, so double-check any detail that matters. Deciding between tools? Read n8n vs Make, or get help from our Make agency. To learn the editor properly, the Make training covers it.

Connect

How do you connect OAD to Make?

  1. 01

    Generate your OAD API key

    In OAD, open Settings, then Integration, and click Generate Token. Copy the API key that appears on screen and keep it at hand, since Make will ask for it in the next step. You need an active OAD account for this.

  2. 02

    Add an OAD module to a scenario

    In Make, open a scenario, click the +, search for OAD and pick any of its modules. Click Create a connection. The connection is your OAD account linked to Make once, then reused by every OAD module.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the instructions Make shows, and save. The module can now read your OAD data.

First scenario

Build your first scenario with OAD

GoalWhen the schedule runs, Make finds your OAD teams, then fetches the members of each one.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since OAD has no trigger, your first module will be an OAD search that runs on a schedule.

  2. 02

    Add Search Teams

    Search for OAD, pick Search Teams and select the connection you made earlier. Fill the fields Make shows; once connected, it lists what it can read in your account.

  3. 03

    Chain Search Team Members

    Click the + on the right of the first module and add Search Team Members. Map data from the team bundle into its fields where they fit, so each team leads to its people.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received. Open them to confirm teams and members came back as you expected.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule (every 15 minutes by default, 15 minutes minimum on the Free plan). Then switch the scenario on and let it run.

Modules

What each OAD module does

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

OAD1

Get Billing Credits

ActionIn the docs only

This action reads the billing credits of your OAD account and hands them to the next module as data you can compare, log or send.

When to use it
ahead of a batch of work in OAD, to alert the person who manages the subscription when credits look low.
Watch out
it reports the credits and changes nothing, so the alert or the decision has to come from a later module.
OAD2

Make an API call

ActionIn the docs only

Here is your way out when the four ready-made modules stop short: it calls any endpoint of the OAD API with the connection you already set up, so there is no second key to manage.

When to use it
a request that Search Candidates or Search Teams cannot express, whatever else OAD's API documentation offers.
Watch out
you write the request yourself, so keep OAD's API documentation open while you build it.
OAD3

Search Candidates

SearchIn the docs only

Need a candidate's OAD record without opening OAD? This search finds it and passes each match on as its own bundle.

When to use it
another app hands over a name or an email and you want the matching OAD profile before the next step.
Watch out
a search can return zero, one or several candidates, and every following module runs once per result, so filter early.
OAD4

Search Team Members

SearchIn the docs only

You get the people behind your OAD teams, one bundle per member, ready to copy into a directory, a sheet or a chat channel.

When to use it
right after Search Teams, when a manager needs the current list of who belongs where.
Watch out
a large result multiplies operations, the unit Make counts on your plan (one module run on one bundle), so narrow the search when you can.
OAD5

Search Teams

SearchIn the docs only

Your team structure in OAD comes out as data: every team found becomes a bundle that the rest of the scenario can loop through.

When to use it
as the opening move of a sync, before fetching members or matching teams against another tool.
Watch out
if nothing matches, the search returns zero bundles and the modules after it simply do not run, which looks like a silent failure during tests.
Need help

Need help automating OAD with Make?

A person reads every message.

FAQ

OAD and Make: frequent questions

01Is the OAD Make integration free?
Yes, on the Make side. OAD is a standard app, so it is available from the Free plan. That plan gives you 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans bring the interval down to 1 minute and remove the cap on active scenarios. Your OAD subscription is separate: Make needs an active OAD account, and OAD's own pricing page covers what that costs.
02What do you need to connect OAD to Make?
An active OAD account and an API key. In OAD, go to Settings, then Integration, click Generate Token and copy the key displayed. In Make, add any OAD module, click Create a connection, give it a name if you like and paste the key. That single connection is then reused by all 5 OAD modules, including Make an API call, so you only do this once per account. With several OAD accounts, repeat these steps for each one, with its own key.
03Can OAD start a Make scenario by itself?
No. OAD has no trigger module in Make, so nothing in OAD can launch a scenario on its own. There are two ways around it. Put an OAD search first and let Make run it on a schedule, every 15 minutes by default. Or start the scenario with a trigger from another app, for example a form or a spreadsheet, and use the OAD modules after it to look up candidates, teams or members.
04What if the OAD module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the OAD API through the connection you already have, so anything OAD's API offers beyond the four other modules is within reach. You build the request yourself from OAD's API documentation. Also keep in mind that Make's documentation for OAD says it was generated by AI from OAD's docs, so confirm important details with OAD directly before you rely on them.
05Should you use Make or n8n for OAD?
It depends on the tool you already run. In Make, OAD comes with 5 modules and a generic API call, and the editor lets you test each step with Run once before you switch anything on. If your team already builds in n8n, check whether an OAD node exists there before moving. Pick the tool where your other automations live, since chaining OAD with those apps is where the value is. Neither choice changes what the OAD API allows.
Same platform

Other docs you might need on this stack.

Browse all integrations