Resources · Make integration

onboard Make integrationAutomate onboard with Make.

New applicants can land in onboard without anyone retyping them. The onboard Make integration offers 2 action modules and no trigger. This guide is for HR and ops teams: link your account, then build a first scenario that creates a candidate.

Try the onboard integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the onboard Make integration do for you?

The onboard Make integration links your onboard account, an HR management app, to Make, a no-code tool. In Make you build a scenario, which is the automation itself. A scenario is a chain of modules, and each module is one brick that does one job. Here you get two bricks: one that creates a candidate in onboard, and one that calls any other part of the onboard API.

Applicants flow in from your forms. Put the form tool you already use at the start of the scenario, then add Create a Candidate. Every submission becomes a candidate record in onboard, so recruiters stop copying names from one tab to another.

A shortlist becomes a pipeline. Keep a spreadsheet of people you plan to hire? A spreadsheet module reads each row, and Create a Candidate turns it into a candidate. Each row travels as a bundle, the item passed from one module to the next.

Everything the list does not cover. Make an API Call reaches any other endpoint of the onboard API with the same connection. It asks for more care, since you write the request yourself.

Know the limit before you start: Make itself says its documentation for onboard is incomplete, because little public information exists about the app. Expect to test with Run once rather than follow a detailed guide. If a step blocks you, the Make troubleshooting page covers the usual errors, and the Make pricing page explains how operations are counted. Weighing another tool? Read n8n vs Make.

Connect

How do you connect onboard to Make?

  1. 01

    Add an onboard module

    In your scenario, click the +, search for onboard and pick Create a Candidate. Inside the module, click Create a connection. A connection is your onboard account linked to Make once, then reused everywhere.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, handy when you work with several onboard accounts. Then either approve Make on the onboard page that opens, or paste the key onboard gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. Make can now read your onboard account and list the objects it can reach inside the module. From here on, every onboard module in any scenario can pick this same connection from a menu.

First scenario

Your first scenario: turn form entries into onboard candidates

GoalWhen someone submits your application form, Make creates the matching candidate in onboard.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module comes from your form app, since onboard has no trigger of its own.

  2. 02

    Add Create a Candidate

    Click the + on the right of the form module, search for onboard, choose Create a Candidate and select the connection you created earlier.

  3. 03

    Map the form answers

    Fill the module fields by picking values from the form module: Make shows what the previous module returned, so you click the answer instead of typing it.

  4. 04

    Test with Run once

    Submit a test entry, then click Run once. Open each module to read the bundles it received and check that a candidate appeared in onboard.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, or keep it instant if the form app calls Make through a webhook. Then switch the scenario on.

Modules

What each onboard module does

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

onboard1

Create a Candidate

ActionIn the docs only

Adds a new candidate to your onboard account from data that arrives in the scenario, so a person never has to type an applicant in by hand.

When to use it
right after a form, a spreadsheet row or another app hands you the details of someone you want to follow in onboard.
Watch out
it runs once per bundle, so ten rows create ten candidates and cost ten operations, the unit Make counts on your plan; filter test data before you switch the scenario on.
onboard2

Make an API Call

ActionIn the docs only

Opens the rest of the onboard API to your scenario, reusing the same connection, for whatever Create a Candidate does not cover.

When to use it
you need an onboard action that has no module of its own and you know which endpoint handles it.
Watch out
Make has little public documentation on onboard, so you write the request yourself; test it with Run once on a harmless call before relying on it.
Need help

Need help automating onboard with Make?

A person reads every message.

FAQ

Common questions about onboard and Make

01Is the onboard Make integration free?
Yes, onboard is a standard app, so its modules work on the Make Free plan. That plan has its 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) lift those caps, with a 1 minute minimum interval and unlimited active scenarios, and count usage in credits each month. Every run of Create a Candidate on one bundle uses one operation.
02What do you need to connect onboard to Make?
An onboard account and a Make account are enough, since the Make documentation lists no other prerequisite. You add an onboard module, click Create a connection, give it a name if you wish, then authorize Make on the onboard page or paste the key onboard provides, and save. That connection is then shared by both modules. Because the documentation for this app is limited, check the result with Run once right after connecting.
03Can onboard start a Make scenario on its own?
No, the onboard app in Make has no trigger module, so nothing in onboard can launch a scenario. You start it another way. Either put the instant trigger of another app first, such as a form that calls Make through a webhook the moment someone submits it, or let Make run the scenario on its schedule, every 15 minutes by default. Onboard then comes in as the action, with Create a Candidate adding the person.
04What if the onboard module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the onboard API from your scenario, with the connection you already have, so you are not stuck with the two listed modules. Keep in mind that Make itself says its documentation for onboard is incomplete for lack of public information, so you build the request without a detailed guide. Try it on a harmless request first, read the bundle it returns, and only then plug it into a live scenario.
05Should you use Make or n8n for onboard?
It depends on where your automations already run. On Make, onboard gives you 2 modules, Create a Candidate and Make an API Call, and it works on the Free plan. Many apps also have an n8n node, so check whether onboard does before choosing. Neither tool is ranked here: compare what each offers for this app, the tool your team already knows, and where your other scenarios live, then pick the one you will keep maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations