Resources · Make integration

BoondManager Make integrationAutomate BoondManager with Make.

Can Make keep your BoondManager records up to date without copy and paste? Yes. The BoondManager Make integration gives you 31 modules: 25 actions and 6 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the BoondManager integration on MakeSee the 31 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the BoondManager Make integration do?

It lets Make read and write your BoondManager data for you. You build a scenario (the automation you assemble in Make) out of modules, each one a single brick: create a candidate, update an opportunity, search your contacts. Make runs the chain on a schedule or when another app hands it new data.

Candidates that file themselves. When someone applies through the form tool you already use, Create a Candidate adds them to BoondManager, so your recruiters stop retyping CVs by hand.

A sales pipeline that stays in sync. A deal marked as won in another tool can trigger Search Opportunities to find the matching record, then Update an Opportunity to move it forward.

Clean company records. Before creating anything, Search Companies checks whether the client already exists, and Create a Company only runs when it does not.

What Make will not do here: BoondManager has no trigger module in Make, so nothing starts on its own when a record changes in BoondManager. Your scenario starts from a schedule or from another app. When a listed module falls short, Make an API Call reaches any other endpoint with the same connection. Curious how n8n handles the same kind of job? Read n8n vs Make, and if you would rather have a hand building it, see Make training.

Connect

How do you connect BoondManager to Make?

  1. 01

    Log in to BoondManager

    Open your BoondManager account in a browser tab and check that your login and password work. Make asks for those exact credentials in the next step, so keep them close.

  2. 02

    Add a module and a connection

    In your Make scenario, insert any BoondManager module and click Add next to the Connection field. A connection is your BoondManager account linked to Make once. Type a clear label in Connection name.

  3. 03

    Enter your credentials and save

    Fill in the Login and Password fields with your BoondManager credentials, then click Save. The module can now list the records your account reaches, and every other BoondManager module reuses this link.

First scenario

Build your first scenario with BoondManager

GoalWhen a prospect fills in your contact form, Make finds their company in BoondManager and adds them as a new contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the form tool you already use as the first module: its new answer is what starts everything.

  2. 02

    Look up the company

    Click the + on the right, search for BoondManager and choose Search Companies. Create the connection when asked, then map the company name from the form answer.

  3. 03

    Add the contact

    Add Create a Contact after the search. Fill its fields by mapping data from the form and the company found. Each item passed along is a bundle: here, one company.

  4. 04

    Test with Run once

    Send a test answer through your form, then click Run once. Open each module's bubble to read the bundles it received and confirm the new contact landed in BoondManager.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, the minimum on the Free plan) and switch the scenario on. From then on, new answers become contacts without you.

Modules

What can BoondManager do in Make?

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

BoondManager1

Create a Candidate

Action

In Make“Creates a new candidate.”

Adds a new person to your recruiting pool in BoondManager, filled with the data your scenario maps in. You get a candidate record without anyone retyping an application.

When to use it
right after a job form or a careers inbox receives a new applicant.
Watch out
run Search Candidates first if the same person might apply twice.
BoondManager2

Create a Company

Action

In Make“Creates a new company.”

Opens a fresh company record in BoondManager from data coming out of a previous module. Your client list grows on its own when a new account shows up elsewhere.

When to use it
a signed quote or a new client in your billing tool.
Watch out
put Search Companies in front, otherwise every run can add a duplicate.
BoondManager3

Create a Contact

Action

In Make“Creates a new contact.”

Saves a new person in BoondManager as a contact, ready to be tied to a company. It spares your sales team the manual entry after every meeting or form.

When to use it
a lead arrives from a website form or an event sign-up.
Watch out
map the company found by an earlier search so the contact does not end up orphaned.
BoondManager4

Create an Action

Action

In Make“Creates a new action.”

Logs a new action in BoondManager, so the history of a record shows what happened outside the app too. Think of it as an automatic note on the timeline.

When to use it
an email was sent or a call was booked in another tool and you want the trace in BoondManager.
Watch out
map the record it belongs to, or the action floats without context.
BoondManager5

Create an Opportunity

Action

In Make“Creates a new opportunity.”

Starts a new opportunity in BoondManager from incoming data, so a deal exists in your pipeline the moment the request lands. Nobody has to remember to open it by hand.

When to use it
a client request comes in through a form or a shared inbox.
Watch out
link it to an existing company found with Search Companies to keep reports tidy.
BoondManager6

Create a Resource

Action

In Make“Creates a new resource.”

Registers a new resource in BoondManager, the record for a person your firm staffs or employs. Onboarding data then lives in one place instead of scattered spreadsheets.

When to use it
a candidate is hired and your HR tool confirms the start.
Watch out
check with Search Resources that the person is not already on file.
BoondManager7

Delete a Company

Action

In Make“Deletes the selected company.”

Removes the selected company from BoondManager for good. It keeps your client base clean when an account is closed or was created by mistake.

When to use it
a cleanup scenario that retires test or duplicate companies you have already reviewed.
Watch out
the module list offers no way to restore a record, so test on a dummy record with Run once first.
BoondManager8

Delete a Contact

Action

In Make“Deletes the selected contact.”

Erases one contact from BoondManager. Handy when a person asks to be removed and you want every tool to follow the same request.

When to use it
an unsubscribe or removal request recorded in another app should reach BoondManager too.
Watch out
feed it the exact contact from a search, never a guess, since no module in the list can restore it.
BoondManager9

Delete an Action

Action

In Make“Deletes the selected action.”

Drops a logged action from BoondManager. Use it to undo notes your own scenario created in error, so timelines stay readable.

When to use it
after a faulty run wrote actions twice and Search Actions has listed the extras.
Watch out
permanent, so filter the search results carefully before this module receives them.
BoondManager10

Delete an Opportunity

Action

In Make“Deletes the selected opportunity.”

Removes an opportunity from BoondManager entirely. It suits pipelines that collect dead or duplicate deals and need a regular sweep based on a clear rule.

When to use it
a deal was opened twice by two different sources and you keep only one.
Watch out
to close a deal, Update an Opportunity is enough; keep deletion for true duplicates.
BoondManager11

Delete a Resource

Action

In Make“Deletes the selected resource.”

Takes a resource record out of BoondManager. It is the last step when a person should no longer appear anywhere in your staffing data.

When to use it
a resource was created by a test scenario or entered twice.
Watch out
there is no matching module for candidates in this list, and no undo for resources either, so double check before switching it on.
BoondManager12

Get a Candidate

Action

In Make“Returns information about the selected candidate.”

Fetches the full record of one candidate you point it to. The next modules can then use any detail of that profile, for a message or a document.

When to use it
a previous module handed you the candidate and you need the rest of their data.
Watch out
it reads one record only; to find candidates by criteria, use Search Candidates.
BoondManager13

Get a Company

Action

In Make“Returns information about the selected company.”

Reads everything BoondManager holds on one selected company. You get a single bundle, one item passed to the next module, with the company data to reuse.

When to use it
an opportunity points to a company and you need its details for an invoice or a welcome email.
Watch out
without the right record selected, the module has nothing to return.
BoondManager14

Get a Contact

Action

In Make“Returns information about the selected contact.”

Pulls up the details of one contact so the rest of the scenario can greet, notify or sync that person elsewhere. One record in, one bundle out.

When to use it
you already know which contact is concerned, for example from an action or an opportunity.
Watch out
when you only know a name, start with Search Contacts instead.
BoondManager15

Get an Action

Action

In Make“Returns information about the selected action.”

Retrieves one logged action with its content. Useful to copy what happened on a record into a chat message, a report or another tool.

When to use it
a search returned an action and you need its complete details before passing them on.
Watch out
each Get counts as one operation, a single run of a module that Make bills to your plan.
BoondManager16

Get an Opportunity

Action

In Make“Returns information about the selected opportunity.”

Loads one opportunity with everything BoondManager knows about it. The next module can then build a proposal, alert a manager or update a sheet.

When to use it
a deal changed status in another tool and you want its BoondManager side before acting.
Watch out
it needs the opportunity to be selected or mapped from an earlier step.
BoondManager17

Get a Resource

Action

In Make“Returns information about the selected resource.”

Returns the full profile of one resource, ready to feed a staffing sheet, a contract template or a notification. No need to open BoondManager to copy it.

When to use it
a mission starts and the next step needs the consultant's details.
Watch out
for a list of resources matching a skill or a status, reach for Search Resources.
BoondManager18

Import file

Action

In Make“Performs an arbitrary authorized API call.”

Sends a file into BoondManager from your scenario, according to its name in Make. The public listing gives it the same one line description as Make an API Call and says nothing else.

When to use it
a document produced or received upstream should end up in BoondManager.
Watch out
check what it expects on a test record with Run once before building on it.
BoondManager19

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the BoondManager API with the connection you already set up. It covers whatever the listed modules leave out, without new credentials.

When to use it
you need an object or a filter that no listed module handles.
Watch out
you write the request yourself, so keep the BoondManager API documentation open next to Make.
BoondManager20

Update a Candidate

Action

In Make“Updates the selected candidate.”

Changes an existing candidate record with fresh data from your scenario. The profile stays current as the hiring process moves on in other tools.

When to use it
an interview was scheduled or a test was completed somewhere else.
Watch out
find the right record first with Search Candidates, then map only what should change.
BoondManager21

Update a Company

Action

In Make“Updates the selected company.”

Edits a company already in BoondManager. Your accounts keep the same details as your billing or signature tool without a manual pass.

When to use it
a client changed address or legal details in another system you trust.
Watch out
find the right company first with Search Companies, otherwise the edit lands on nothing or on the wrong record.
BoondManager22

Update a Contact

Action

In Make“Updates the selected contact.”

Refreshes one contact in BoondManager, so a new job title or phone number spreads without anyone copying it over. It closes the gap between your forms and your CRM data.

When to use it
a contact edits their details in a form or a newsletter tool.
Watch out
match on a reliable key from a search before updating.
BoondManager23

Update an Action

Action

In Make“Updates the selected action”

Modifies an action that already exists, for instance to complete it once the related task is done elsewhere. The record timeline then tells the true story.

When to use it
a meeting logged earlier took place and its outcome comes back from your calendar or call tool.
Watch out
find the right action first with Search Actions, or the update lands on the wrong record.
BoondManager24

Update an Opportunity

Action

In Make“Updates the selected opportunity.”

Moves an opportunity forward by writing new values on it. Your pipeline reflects signatures, rejections or new amounts as soon as the scenario runs.

When to use it
a quote gets signed in your e-signature tool and the deal should change stage.
Watch out
pair it with Search Opportunities when the other tool does not store the BoondManager record.
BoondManager25

Update a Resource

Action

In Make“Updates the selected resource.”

Updates a resource profile, so it matches what the rest of your stack says about that person. Staffing decisions then rely on current data.

When to use it
your HR tool records a change for someone already in BoondManager.
Watch out
one update per resource per run; a search that returns many will update each of them.
BoondManager26

Search Actions

Search

In Make“Searches for actions or lists them.”

Lists the actions that match your criteria, or all of them. Each result leaves the module as its own bundle, so later modules handle them one by one.

When to use it
to build a summary of recent activity or to spot duplicates before a cleanup.
Watch out
a search can return zero, one or many items, and each item costs operations further down.
BoondManager27

Search Candidates

Search

In Make“Searches for candidates or lists them.”

Finds candidates in BoondManager, or lists them, so your scenario can check before it creates. It is the guard that keeps your talent pool free of doubles.

When to use it
in front of Create a Candidate, with the applicant's name or email mapped in.
Watch out
add a filter after it so an empty result leads to creation and a match leads to an update.
BoondManager28

Search Companies

Search

In Make“Searches for companies or lists them.”

Looks up companies in your BoondManager base and returns the matches. Your scenario learns whether a client exists before it writes anything new.

When to use it
any time outside data mentions a company name, like a form, a quote or an invoice.
Watch out
an empty result is normal for a new client; add a filter so Create a Company runs only then.
BoondManager29

Search Contacts

Search

In Make“Searches for contacts or lists them.”

Searches your contacts and hands back each one it finds. It turns an email address or a name coming from elsewhere into a BoondManager record you can act on.

When to use it
before Update a Contact or Create an Action, to attach the change to the right person.
Watch out
loose criteria can return many bundles; narrow them to avoid a flood of updates.
BoondManager30

Search Opportunities

Search

In Make“Searches for opportunities or lists them.”

Pulls a list of opportunities matching what you ask for. It is the natural starting point for a scheduled scenario that reports on or tidies your pipeline.

When to use it
as the first module of a scenario that runs on a schedule, since BoondManager has no trigger.
Watch out
without a filter, every run returns the same deals again.
BoondManager31

Search Resources

Search

In Make“Searches for resources or lists them.”

Finds the resources that fit your criteria and passes them on one by one. Staffing questions such as who is free or who has a skill become an automated list.

When to use it
to fill a planning sheet or alert a manager when a mission needs someone.
Watch out
each resource returned runs through the next modules, which multiplies operations.
Need help

Need help automating BoondManager with Make?

A person reads every message.

FAQ

BoondManager and Make: common questions

01Is the BoondManager Make integration free?
Yes, as far as Make goes. BoondManager is a standard app, available from the Free plan like the other 3,000+ standard apps. The Free plan has 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your BoondManager subscription is a separate matter this page does not cover.
02What is needed to connect BoondManager to Make?
A working BoondManager account and its credentials. The official documentation lists no other prerequisite. You log in to BoondManager, insert any BoondManager module in a scenario, click Add next to the Connection field, name the connection, then type your Login and Password and click Save. That single connection is then reused by all 31 BoondManager modules, so you set it up once per account. Pick a connection name that shows which account it belongs to, so the right one is easy to spot in every scenario.
03Does BoondManager trigger Make scenarios in real time?
No. BoondManager has no trigger module in Make, neither scheduled nor instant, so a change in BoondManager does not start a scenario by itself. You have two ways to start anyway. Put a search module such as Search Opportunities first and let Make run it on the scenario's schedule, every 15 minutes by default. Or start with a trigger from another app, for example a form or an email tool, then use BoondManager modules as the next steps.
04What if a BoondManager module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the BoondManager API through the connection you already have, so it covers objects and filters the listed modules do not. You write the request yourself, which means reading the BoondManager API documentation. The Make documentation gives no numeric limit for this app. If you would rather not touch the API, another app in your stack may already hold the data you need.
05Should BoondManager be automated with Make or n8n?
It depends on where you already work. Make offers BoondManager as a ready app with 31 modules and one connection shared by all of them, which suits someone who wants to build visually from a list of actions and searches. Many apps also exist as n8n nodes, so check the n8n side for BoondManager before choosing. Base the decision on the tool your team already uses and the modules each side offers for your use case, not on a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations