Resources · Make integration

coreBos Make integrationAutomate coreBos with Make.

The coreBos Make integration lets other tools write into coreBos for you. It offers 7 modules: 6 actions and 1 search. This guide is for teams who run coreBos and are new to Make, and it walks you from the connection to a first working scenario.

Try the coreBos integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the coreBos Make integration do for you?

The integration links your coreBos account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as an action or a search. With coreBos, those bricks create, look up, change, link and remove objects in your account, so data coming from elsewhere lands in coreBos without anyone typing it.

New entries stop being retyped. A sign-up from a web form or a paid order from a shop can flow straight into Create Object, and the record exists in coreBos as soon as the scenario runs.

Records stay tidy. Put Search Object first to find what already exists, then Update Object it instead of creating a duplicate. Relate Objects then ties the record to another one, for example an order to the account it belongs to.

Other tools read coreBos too. Retrieve Object pulls one record so its data can feed an email, a spreadsheet row or a chat message in the next module.

Know the limits before you start. coreBos has no trigger in Make, so a scenario starts from another app or from a schedule, and there is no Make an API Call module to reach what the 7 modules do not cover. The official documentation also warns that its coreBos page is AI-generated and may contain mistakes, so test every module on a sample record. If you are still weighing tools, read our Make review and the n8n vs Make comparison; when a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect coreBos to Make?

  1. 01

    Grab your access key

    Log in to coreBos with an active account, click your username or profile icon, then open My Preferences. The access key shown there is what Make needs, so copy it and keep it at hand.

  2. 02

    Open a coreBos module

    In your Make scenario, add any coreBos module and click Create a connection. A connection is your coreBos account linked to Make once, then reused by every coreBos module you add later.

  3. 03

    Enter your credentials

    Give it a clear label in Connection name if you like; this field is optional. Then paste the credentials copied from coreBos, or follow the on-screen instructions to create the connection.

First scenario

Build your first scenario with coreBos

GoalWhen a new entry appears in another app, Make creates the matching object in coreBos.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since coreBos has no trigger, pick the app where new entries come from, such as your form tool.

  2. 02

    Add Create Object

    Click the + on the right of that first module, search for coreBos and choose Create Object. Link your account with Create a connection if you have not done it yet.

  3. 03

    Map the data

    Fill the module fields. Once the connection exists, Make lists what it can read in coreBos, and you drag values from the first module into each field, like the name from the form.

  4. 04

    Test with Run once

    Click Run once and send one sample entry. Each module shows the bundles it received, a bundle being one item passed along, so you can confirm the record really exists in coreBos.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Modules

What each coreBos module does

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

coreBos1

Create Object

ActionIn the docs only

Adds a brand new record to coreBos from data that arrives in the scenario, so nobody has to type it in again.

When to use it
a lead fills a form or a customer places an order, and that person or sale must exist in coreBos right away.
Watch out
it creates a record on every run. If the same entry might come twice, put Search Object in front of it.
coreBos2

Delete Object

ActionIn the docs only

Removes a record from coreBos, which keeps your data clean when something is cancelled or turns out to be a mistake elsewhere.

When to use it
an order is voided in your shop and the matching record should disappear from coreBos too.
Watch out
the record is really removed, so try it with Run once on a throwaway record before switching the scenario on.
coreBos3

Relate Objects

ActionIn the docs only

Ties two existing records together, so the link between them is visible in coreBos instead of living in someone's head.

When to use it
a contact was just created. Attach it to the company it works for, found earlier in the same scenario.
Watch out
both records must already exist; add Create Object or Search Object upstream so this module receives what it needs to link.
coreBos4

Retrieve Object

ActionIn the docs only

Fetches one specific record so its details can travel to the next modules, for instance into an email, a sheet or a message.

When to use it
you already know which record you want, often because a previous module passed it along, and you only need its data.
Watch out
it reads a single known record; when you only know a name or a value, start with Search Object.
coreBos5

Revise Object

ActionIn the docs only

Changes an existing record in coreBos without creating a new one, which is useful when details evolve after the first entry.

When to use it
a customer updates their address in another tool and coreBos should reflect it.
Watch out
the documentation does not say how it differs from Update Object, so compare both with Run once on a test record before relying on either.
coreBos6

Search Object

SearchIn the docs only

Looks up records in coreBos and hands back whatever matches, so the scenario can decide what to do next based on what it found.

When to use it
before creating a contact, check whether that email address is already in coreBos.
Watch out
a search can return zero, one or several bundles, and every bundle runs the following modules once, which also counts operations on your plan.
coreBos7

Update Object

ActionIn the docs only

Writes new values onto a record that already sits in coreBos, keeping one clean version of it rather than a pile of copies.

When to use it
Search Object has just found the matching customer and the latest status from your shop needs to replace the old one.
Watch out
Revise Object sounds close; test both on a sample record and keep the one whose result matches what you expect.
Need help

Need help automating coreBos with Make?

A person reads every message.

FAQ

coreBos and Make: common questions

01Is the coreBos Make integration free?
Yes, on the Make side. coreBos is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans go down to a 1 minute interval and allow unlimited active scenarios. Usage is counted in operations, one operation being one module running on one bundle. You still need your own active coreBos account, which is billed by coreBos.
02What do you need to connect coreBos to Make?
An active coreBos account with valid user credentials, and a Make account. In coreBos, click your username or profile icon, open your preferences section and copy the access key shown there. In Make, add a coreBos module, click Create a connection, optionally name it, then paste the credentials or follow the on-screen instructions. The connection is created once and every coreBos module in your scenarios reuses it, so you will not repeat these steps.
03Does coreBos trigger Make scenarios in real time?
No, because coreBos has no trigger module in Make at all. A scenario that uses coreBos starts in one of two ways. Either another app opens it, such as a form or a shop whose trigger reacts to a new entry, or you let Make run it on a schedule, every 15 minutes by default, and down to 1 minute on paid plans. In both cases, coreBos only comes in as an action or a search further down the scenario.
04What if a coreBos module is missing in Make?
It depends on what you need. The integration has 7 modules covering create, retrieve, search, update, revise, relate and delete, but no Make an API Call module to reach anything beyond them. When a need falls outside these modules, look for another app in Make that already covers the task, or ask the team for help designing a workaround. Keep in mind the official coreBos documentation is flagged as AI-generated, so check behaviour with Run once.
05Make or n8n for coreBos?
It depends on your criteria. On Make, coreBos comes with 7 modules, no trigger and no universal API module, and it runs on the Free plan within its limits. If the same app exists as an n8n node, compare which one covers the actions you need and which interface your team is ready to maintain. Neither tool is ranked here: list the actions you cannot do without first, then test them on the tool you lean toward before building the full workflow.
Same platform

Other docs you might need on this stack.

Browse all integrations