Resources · Make integration

Recruspace Make integrationAutomate Recruspace with Make.

What if every new candidate in Recruspace set off the next step on its own? The Recruspace Make integration gives you 12 modules: 5 triggers, 6 actions and 1 search. This page is for recruiters and ops leads, and it walks you from the API key to a first working scenario.

Try the Recruspace integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Recruspace Make integration do for your hiring?

The Recruspace Make integration links your Recruspace account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Recruspace events start the scenario, and Recruspace actions update candidates, notes, tags and talent pools without you touching the app.

A sorted pipeline from day one. Watch Candidate Created picks up each new applicant, and Add Tag to Candidate labels the profile so your team sees at a glance where it came from. Search Candidate by Email helps you check first whether the person is already in your base.

Replies that never sit unread. Watch Candidate Replied to Email notices when a candidate answers, and Add Note to Candidate records the fact on the profile, so the next recruiter who opens it knows the conversation moved.

Clean follow-up when a stage changes. Watch Candidate Stage Changed reacts to a move in your pipeline; pair it with Create Talent Pool to keep strong profiles you did not hire for a later role. Watch New Job Posted and Job Closed cover the other end: the life of the position itself.

Keep the limits in mind. The Make docs list the five Recruspace triggers without their type; as Watch modules they are treated as scheduled, so Make checks for news on the scenario's schedule instead of hearing about it instantly. The clock badge on the module confirms it. The Make documentation for Recruspace lists the modules without describing them, and says its own page is AI-generated and may contain mistakes, so test each module with a sample before trusting it. For anything the list does not cover, Make an API call reaches the Recruspace API with the same connection. If you hesitate between tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains plans, and the Make training helps if Make is new to you.

Connect

How do you connect Recruspace to Make?

  1. 01

    Generate an API key in Recruspace

    In Recruspace, click your profile picture at the top right and choose Settings. Open the Career section on the left, click Generate Key under Career Page Integration, give the key a clear name, confirm, then copy the key shown on screen.

  2. 02

    Add a Recruspace module in Make

    In your Make scenario, add any Recruspace module and click Create a connection. A connection is your Recruspace account linked to Make once, then reused by every Recruspace module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Recruspace into the credentials field, or follow the instructions Make shows on screen, then save. Make can now read and write in your account, and the module fields show your Recruspace data.

First scenario

Your first scenario: tag every new Recruspace candidate

GoalWhen a candidate is created in Recruspace, Make adds a tag to that candidate's profile.

  1. 01

    Create a new scenario

    From the Scenarios page in Make, create a new scenario and click the big + in the middle of the editor to add your first module.

  2. 02

    Add the trigger and its connection

    Search for Recruspace, pick Watch Candidate Created and click Create a connection if you have not linked your account yet. This module starts the scenario each time it finds a new candidate.

  3. 03

    Add the tagging action

    Click the + on the right of the trigger, add Add Tag to Candidate and map the candidate from the first module, so the tag lands on the right profile. Fill the remaining fields Make shows you.

  4. 04

    Test with Run once

    Create a test candidate in Recruspace, then click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along, here one candidate.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module to set how often Make checks Recruspace; a new scenario runs every 15 minutes by default. Then switch the scenario on, and new candidates get tagged without you.

Triggers

Which Recruspace events can start a scenario?

5 modules start a scenario when something happens in Recruspace. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Recruspace as soon as it happens.

Recruspace1Watch Bulk Import Completed

Watch Bulk Import Completed

triggerIn the docs only

Tells your scenario that a bulk import has finished in Recruspace, so the follow-up work starts once all the imported profiles are in place rather than halfway through. Make lists this trigger without a description, so check the bundle it returns with Run once.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
after loading a batch of candidates, to alert the hiring team or start sorting the new arrivals.
Watch out
the scenario reacts to the finished import as a whole, so read what the bundle holds before mapping candidates from it.
Recruspace2Watch Candidate Created

Watch Candidate Created

triggerIn the docs only

Starts your scenario with each new candidate that appears in Recruspace, one bundle per profile, which makes it the natural entry point for any intake automation.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when every applicant should get the same first treatment, such as a tag, a note or a message to the recruiter in charge.
Watch out
it waits for the next scheduled check, so a candidate created just after a check is picked up at the following one. Each candidate handled counts operations, one per module it passes through.
Recruspace3Watch Candidate Replied to Email

Watch Candidate Replied to Email

triggerIn the docs only

Brings a candidate's email reply into your scenario, so an answer turns into a visible next step instead of waiting in an inbox that nobody opened.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when replies must reach the right recruiter or be logged on the profile with Add Note to Candidate.
Watch out
this is not a live alert, the reply surfaces at the next check. Run it once on a real reply to see which details the bundle carries before you build on them.
Recruspace4Watch Candidate Stage Changed

Watch Candidate Stage Changed

triggerIn the docs only

Follows candidates as they move through your hiring pipeline and hands each move to your scenario, which lets one stage change set off everything that should come with it.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when reaching a given stage should add a tag, write a note or place the profile in a talent pool.
Watch out
it catches every stage change, so the modules that follow run for every move, not only the one you care about; check the stage in the bundle before building on it.
Recruspace5Watch New Job Posted

Watch New Job Posted

triggerIn the docs only

Picks up each new job you post in Recruspace, so the rest of your stack learns about an opening at the same moment your team publishes it.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
to share a fresh opening with other tools, notify a hiring manager or prepare a talent pool dedicated to the role.
Watch out
the job reaches Make at the next scheduled check, not the second it goes live. Run the scenario once with a test posting to see which job details you can map.
Modules

What can Make do in Recruspace?

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

Recruspace1

Add Candidate

ActionIn the docs only

Creates a candidate profile in Recruspace from data that lives elsewhere, a form, a spreadsheet or another app, so nobody retypes applications by hand.

When to use it
when applicants arrive through a channel outside Recruspace and should land in your pipeline.
Watch out
run Search Candidate by Email first, or the same person may end up with two profiles.
Recruspace2

Add Note to Candidate

ActionIn the docs only

Writes a note on a candidate's profile, which keeps the story of each application in one place where every recruiter can read it.

When to use it
to log an email reply, a stage change or a message received in another tool.
Watch out
it needs the right candidate, so map the candidate from the trigger or a search instead of typing it.
Recruspace3

Add Tag to Candidate

ActionIn the docs only

Puts a tag on a candidate so profiles sort themselves by source, skill or priority, and your team filters them in Recruspace without extra effort.

When to use it
right after Watch Candidate Created, to label where each applicant came from.
Watch out
keep your tag names consistent across scenarios, or you will end up with near duplicates that split the same group.
Recruspace4

Create Talent Pool

ActionIn the docs only

Opens a new talent pool in Recruspace, a place to keep good profiles you want to contact again later rather than losing them once a role closes.

When to use it
when a new job is posted and you want a pool ready for it, or when a role closes and runners-up deserve a home.
Watch out
each run creates a pool, so do not leave it on a trigger that fires often.
Recruspace5

Job Closed

ActionIn the docs only

Handles the closing of a job in Recruspace from your scenario, so a position filled elsewhere stops attracting applications without a manual trip into the app.

When to use it
when a hire is confirmed in another tool and the opening should follow.
Watch out
Make gives no description of this module; test it with Run once on a test job before pointing it at a live posting.
Recruspace6

Make an API call

ActionIn the docs only

Reaches any endpoint of the Recruspace API from your scenario with the connection you already set up, which covers the needs the listed modules leave out.

When to use it
when you need a Recruspace feature that has no module of its own in Make.
Watch out
you write the request yourself, so keep the Recruspace API documentation open.
Recruspace7

Search Candidate by Email

SearchIn the docs only

Looks up candidates by email address and returns what it finds, which tells your scenario whether a person is already known before it does anything else.

When to use it
before Add Candidate, or to find the profile a reply or a form belongs to.
Watch out
a search can return zero, one or several bundles; decide what the scenario should do when nothing comes back.
Need help

Need help automating Recruspace with Make?

A person reads every message.

FAQ

Recruspace and Make: common questions

01Is the Recruspace Make integration free?
Yes, on the Make side. Recruspace is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your Recruspace subscription is a separate matter: the Recruspace pricing page covers it.
02What do you need to connect Recruspace to Make?
You need an active Recruspace account and an API key. You create the key in Recruspace under Settings, in the Career section, with the Generate Key button of the Career Page Integration area. In Make, add a Recruspace module, click Create a connection, give it a name if you like, and paste the key. The connection is then reused by every Recruspace module in your scenarios, so you only do this once.
03Do Recruspace triggers in Make react in real time?
Most likely not. The Make docs do not state their type, but all five are Watch modules, treated as scheduled (the clock badge on the module confirms it): Make checks Recruspace on the scenario's schedule and processes what changed since the last check. A new scenario runs every 15 minutes by default, and on the Free plan 15 minutes is also the shortest interval. Paid plans can go down to 1 minute. For a hiring pipeline, that means a new candidate or a reply shows up in your scenario at the next check, not the moment it happens.
04What if a Recruspace module is missing in Make?
Use Make an API call. It reaches any endpoint of the Recruspace API with the connection you already have, so a feature without its own module is still in reach. You write the request yourself, which means reading the Recruspace API documentation. Also note that the Make page for Recruspace is flagged as AI-generated and may contain mistakes, so test any module with Run once and confirm details with Recruspace when something looks off.
05Should you use Make or n8n for Recruspace?
It depends on the tool you already work in. Recruspace has 12 modules in Make, with triggers, actions, a search and Make an API call to fill the gaps. The same app often has an n8n node as well, so check what exists there before choosing. Look at which events you need to catch and which actions you need, and pick the tool where your team already builds. The comparison page linked above sets out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations