Resources · Make integration

CompanyHub Make integrationAutomate CompanyHub with Make.

Can Make keep your CompanyHub pipeline moving on its own? The CompanyHub Make integration gives you 49 modules: 8 triggers, 33 actions and 8 searches. This guide is for sales and ops people who know CompanyHub and want to link their account, build a first scenario and pick the right module.

Try the CompanyHub integration on MakeSee the 49 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the CompanyHub Make integration let you automate?

The CompanyHub Make integration links your CompanyHub account to Make so a scenario, the automation you build in Make as a chain of modules, can read and write your companies, contacts, deals, quotes and sales orders. You set it up once with an API key and never write code.

Quotes that follow the deal. Watch New Deal spots a fresh opportunity, Create a Quote opens the quote, and Add a Product on a Quote fills in the lines. The rep checks it instead of retyping it.

A contact list without duplicates. Before you add anyone, Search Contacts looks for the person. If a match comes back, Update a Contact refreshes it; if not, Create a Contact adds it. A web form or a spreadsheet from another app can feed that flow.

Orders passed on to the rest of the stack. Watch New Sales Order hands each order to Make, and Search Sales Orders Products reads its lines so another tool (billing, shipping, a team chat) receives exactly what was sold.

Know the limits before you start. All 8 triggers are scheduled: Make checks CompanyHub on the scenario's schedule, every 15 minutes by default, and nothing is pushed instantly. When a listed module does not cover your case, Make an API Call reaches the rest of the CompanyHub API with the same connection. If you are still choosing a platform, read n8n vs Make, and check Make pricing to see what each plan allows.

Connect

How do you connect CompanyHub to Make?

  1. 01

    Copy your subdomain and API key

    In CompanyHub, open Settings, then Integrations. That page shows two values Make needs: your subdomain and your API key. Copy both somewhere safe for the next step.

  2. 02

    Add a CompanyHub module in Make

    In your scenario, add any CompanyHub module and click Create a connection. A connection is your CompanyHub account linked to Make once and reused by every CompanyHub module afterward. The Connection name field is optional, but a clear name helps when you have several accounts.

  3. 03

    Paste the credentials and save

    Enter the subdomain and API key you copied, or follow the instructions Make shows on screen, then save. Make can now list your CompanyHub data in the module fields.

First scenario

Build your first CompanyHub scenario

GoalWhen a new deal lands in CompanyHub, Make creates a quote for it in CompanyHub.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to add the first module.

  2. 02

    Add the Watch New Deal trigger

    Search for CompanyHub, pick Watch New Deal and select the connection you created earlier, or click Create a connection if you skipped that part.

  3. 03

    Add Create a Quote

    Click the + on the right of the trigger, choose Create a Quote, then map the deal data from the first module into the quote fields Make lists for you.

  4. 04

    Test with Run once

    Add a test deal in CompanyHub, then click Run once. Open each module's bubble to read the bundle it received and confirm the quote appeared in CompanyHub.

  5. 05

    Set the schedule and switch it on

    Click the clock on Watch New Deal to set how often Make checks for deals (every 15 minutes by default), then switch the scenario on.

Triggers

The 8 CompanyHub triggers in Make

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

CompanyHub1Watch New Company

Watch New Company

triggerIn the docs only

Each company added to CompanyHub can start a scenario with this trigger. Make receives the account as a bundle, one item passed on to the next module, so you can alert the account owner or copy the company into another tool.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a new company shows up at the next check.
When to use it
your team creates accounts by hand and a second system has to hear about each one.
Watch out
on the Free plan two checks are at least 15 minutes apart; paid plans go down to 1 minute.
CompanyHub2Watch New Contact

Watch New Contact

triggerIn the docs only

People matter more than accounts in many sales teams, and Watch New Contact turns every person saved in CompanyHub into the starting point of a scenario. The following modules can welcome them, tag them or copy them into your mailing tool.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up the contacts created since the last check.
When to use it
a rep keys in a lead met at a trade fair and marketing should get it too.
Watch out
click Run once with a test contact and read the bundle before you switch the scenario on.
CompanyHub3Watch New Deal

Watch New Deal

triggerIn the docs only

This is the trigger most pipelines start with: a deal appears in CompanyHub and your scenario gets its details right after Make's next check. Pair it with Create a Quote or a message to the sales channel.

How it fires
scheduled. Make checks the app on the scenario's schedule, which you set with the clock on the module.
When to use it
a new opportunity should trigger paperwork or a heads up without anyone copying data.
Watch out
a scenario only runs while it is switched on, and the Free plan allows 2 active scenarios, so plan which ones deserve a slot.
CompanyHub4Watch New Quote

Watch New Quote

triggerIn the docs only

Sent quotes often need a second life outside the CRM. Watch New Quote hands Make every quote created in CompanyHub, so you can archive it, notify a manager or open a follow-up task somewhere else.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes unless you change it.
When to use it
a manager wants to follow every quote without logging into CompanyHub.
Watch out
if your first scenario already creates quotes, do not feed this trigger's output back into Create a Quote, or each run adds one more quote.
CompanyHub5Watch New Quote Product

Watch New Quote Product

triggerIn the docs only

Instead of the quote as a whole, this trigger follows the products placed on quotes. Each new line becomes its own bundle, which helps when what you sell matters more than the document it sits on.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the product lines added since the previous check.
When to use it
the purchasing team must know when a given product is being quoted, before the order exists.
Watch out
a quote with several products returns several bundles, and every module after the trigger runs once per bundle, which counts operations on your plan.
CompanyHub6Watch New Record

Watch New Record

triggerIn the docs only

Watch New Record covers the records that do not have a dedicated watcher among the other CompanyHub triggers. When one is created, Make passes it to the rest of the scenario as a bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, not at the moment the record is saved.
When to use it
you track something in CompanyHub beyond companies, contacts, deals, quotes and orders, and another app needs to follow it.
Watch out
run the scenario once with Run once and look at the bundle to see exactly which data this trigger brings back before mapping anything.
CompanyHub7Watch New Sales Order

Watch New Sales Order

triggerIn the docs only

A signed order is where fulfilment starts, and this trigger gives Make each sales order created in CompanyHub. The next modules can pass it to billing, warn the warehouse or post a win in the team chat.

How it fires
scheduled. Make checks the app on the scenario's schedule; set a shorter interval on a paid plan if orders need to move faster.
When to use it
operations should start preparing an order without waiting for someone from sales to pass it on.
Watch out
the items of an order have their own modules in Make; add Search Sales Orders Products after the trigger when the next app needs them.
CompanyHub8Watch New Sales Order Product

Watch New Sales Order Product

triggerIn the docs only

Some flows care about the items rather than the order. Watch New Sales Order Product sends Make each product line added to a sales order in CompanyHub, one bundle per line, ready to adjust stock or feed a production list.

How it fires
scheduled. Make checks the app on the scenario's schedule and collects the lines created since the last run.
When to use it
a workshop or warehouse works item by item, not order by order.
Watch out
a large order means many bundles in a single run, and each following module spends one operation per bundle.
Modules

Every CompanyHub action and search in Make

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

CompanyHub1

Add a Product on a Quote

ActionIn the docs only

Fills an existing quote with a product line, so a quote created by your scenario does not stay empty.

When to use it
right after Create a Quote, to add the products the customer asked for in the deal.
Watch out
the module needs a quote to attach to; map the quote from the previous module rather than typing it, or the line lands on the wrong quote.
CompanyHub2

Add a Product on a Sales Order

ActionIn the docs only

Puts a product line on a sales order that already exists in CompanyHub, which completes an order your scenario has just opened.

When to use it
a webshop or form sends the items one by one and each must end up on the same order.
Watch out
if the items come as a list, each one is a separate bundle and a separate operation, so check the count after Run once.
CompanyHub3

Create a Company

ActionIn the docs only

Adds a new company to CompanyHub from data collected elsewhere, a signup, a spreadsheet row or an enrichment tool.

When to use it
a prospect fills in your demo form and the sales team should find the account ready in CompanyHub.
Watch out
the module creates without checking; put Search Companies before it if the same company can arrive twice.
CompanyHub4

Create a Contact

ActionIn the docs only

Saves a new person in CompanyHub, so leads captured by other apps land in the CRM without anyone retyping names or emails.

When to use it
a newsletter signup or a meeting booked in another tool should produce a contact for the sales team.
Watch out
run Search Contacts first and route to Update a Contact when the person already exists, otherwise duplicates pile up.
CompanyHub5

Create a Deal

ActionIn the docs only

Puts a fresh deal into CompanyHub from an outside signal, which puts the opportunity in the pipeline as soon as the scenario runs.

When to use it
a quote request arrives through your website form and should become a deal assigned to sales.
Watch out
a deal usually belongs to a company or a contact; create or find them earlier in the scenario so you can map them in.
CompanyHub6

Create a Quote

ActionIn the docs only

Produces a new quote in CompanyHub, the step that turns a deal into a document your rep can review and send.

When to use it
after Watch New Deal, when every opportunity should come with a draft quote.
Watch out
this module creates the quote itself; products go on with Add a Product on a Quote in a following module.
CompanyHub7

Create a Record

ActionIn the docs only

Writes a new record in CompanyHub for data that has no dedicated create module on this list, which keeps the rest of your CRM inside the same scenario.

When to use it
you log items beyond companies, contacts, deals, quotes and orders, and another app produces them.
Watch out
test with Run once and open the record in CompanyHub to confirm it landed where you expect.
CompanyHub8

Create a Sales Order

ActionIn the docs only

Opens a sales order in CompanyHub, so an accepted quote or an online purchase becomes an order the team can process.

When to use it
a payment confirmed in another app means the deal is won and the order must exist in the CRM.
Watch out
items have their own module, so follow it with Add a Product on a Sales Order for each line the order must carry.
CompanyHub9

Delete a Company

ActionIn the docs only

Removes a company from CompanyHub, handy for cleaning out test accounts or entries that another system marks as closed.

When to use it
a scenario detects a duplicate account and the extra one should disappear.
Watch out
a deletion cannot be undone from Make; add a filter before the module and test with a dummy company first.
CompanyHub10

Delete a Contact

ActionIn the docs only

Erases a person from CompanyHub, useful when someone asks to be forgotten or when a contact turns out to be spam.

When to use it
a deletion request arrives through a form and the CRM must follow.
Watch out
Make does not bring a deleted contact back; find the exact contact with Search Contacts and check the match before this step.
CompanyHub11

Delete a Deal

ActionIn the docs only

Takes a deal out of CompanyHub, which keeps the pipeline free of opportunities created by mistake or by a test.

When to use it
while building scenarios, to clear the test deals your runs created.
Watch out
once the scenario is live, a wrong mapping could remove a real deal; protect the module with a filter and there is no undo.
CompanyHub12

Delete a Quote

ActionIn the docs only

Clears a quote out of CompanyHub, so drafts that nobody will send do not clutter the list of open quotes.

When to use it
a deal is lost or cancelled and its unsent quote has no reason to stay.
Watch out
the quote is gone for good; if a manager might still want it, archive a copy with Get a Quote before deleting.
CompanyHub13

Delete a Quote Product

ActionIn the docs only

Strips one product line from a quote while leaving the rest of the quote intact.

When to use it
a product is discontinued and the scenario must pull it from open quotes found with Search Quote Products.
Watch out
the search can return several lines, and the delete then runs on each of them; review the bundles with Run once before activating.
CompanyHub14

Delete a Record

ActionIn the docs only

Removes a record from CompanyHub for the data types that do not have their own delete module on this list.

When to use it
records created by an import or a test need to be cleared out.
Watch out
Make cannot restore what this module erases; map the record from Search Records or Get a Record rather than typing it by hand.
CompanyHub15

Delete a Sales Order

ActionIn the docs only

Deletes an entire sales order from CompanyHub, the cleanest way to undo an order your scenario created in error.

When to use it
a payment fails in your billing app and the order opened for it should vanish.
Watch out
orders often matter to accounting; add a filter so only the right case triggers the delete, because it is final.
CompanyHub16

Delete a Sales Order Product

ActionIn the docs only

Pulls one item off a sales order, which keeps the order but corrects what it contains.

When to use it
a customer drops a single item after ordering and the rest of the order still ships.
Watch out
make sure you map the line, not the whole order; test on a dummy order since the removal cannot be reversed.
CompanyHub17

Get a Company

ActionIn the docs only

Reads one company from CompanyHub when you already know which one you want, and gives its details to the next modules.

When to use it
a deal arrives with a company attached and your message or document needs the company's details.
Watch out
Get a Company fetches a single known company; if you only have a name, use Search Companies instead.
CompanyHub18

Get a Contact

ActionIn the docs only

Pulls the full details of one contact so later modules can greet the person, route them or copy them elsewhere.

When to use it
a trigger gives you a contact reference and the next step needs more than that reference.
Watch out
this module needs to know which contact; when you start from an email or a name, Search Contacts is the right pick.
CompanyHub19

Get a Deal

ActionIn the docs only

Loads one deal from CompanyHub, handy when a quote or an order points to a deal and your scenario needs its details.

When to use it
a new quote comes in and the notification should mention the deal it belongs to.
Watch out
each Get runs once per bundle it receives, so a trigger returning many items multiplies the operations.
CompanyHub20

Get a Quote

ActionIn the docs only

Retrieves one quote so its content can travel to another app, a document template or an approval step.

When to use it
a manager approves quotes in a chat tool and needs the quote details in the message.
Watch out
the product lines are a separate object; add Search Quote Products if the message must list what is being sold.
CompanyHub21

Get a Quote Product

ActionIn the docs only

Zooms in on one product line of a quote, which gives the next module the exact item rather than the whole quote.

When to use it
Watch New Quote Product has spotted a line and you need its full details before passing it to purchasing.
Watch out
to read every line of a quote at once, Search Quote Products fits better than several Get calls.
CompanyHub22

Get a Record

ActionIn the docs only

Fetches one record from CompanyHub, the counterpart of Get a Company or Get a Deal for data kept as records.

When to use it
Watch New Record fired and the next module needs the record's complete details.
Watch out
run it once with Run once and read the bundle, since this page cannot tell you which data a record holds in your account.
CompanyHub23

Get a Sales Order

ActionIn the docs only

Opens one sales order and hands its details to the scenario, ready for an invoice, a delivery note or a message.

When to use it
a product line was added and the next step needs the order it belongs to.
Watch out
the order and its items are read separately; pair this module with Search Sales Orders Products when you need both.
CompanyHub24

Get a Sales Order Product

ActionIn the docs only

Returns one item of a sales order, which is what a warehouse or production tool usually needs to act on.

When to use it
Watch New Sales Order Product fired and you want the full line before creating a picking task.
Watch out
the module reads a single known line; to list every item of an order, use Search Sales Orders Products.
CompanyHub25

Make an API Call

ActionIn the docs only

Reaches any endpoint of the CompanyHub API from your scenario, with the connection you already set up, so you are not stuck when a listed module is missing.

When to use it
you need an operation that none of the 49 modules offers.
Watch out
you write the request yourself, so keep CompanyHub's API documentation open and test with Run once.
CompanyHub26

Search Companies

SearchIn the docs only

Looks up companies in CompanyHub and returns zero, one or several matches, so your scenario can decide whether an account already exists.

When to use it
before Create a Company, to avoid adding a firm your team already tracks.
Watch out
each match is a separate bundle and the next module runs for every one; add a filter if you expect only one.
CompanyHub27

Search Contacts

SearchIn the docs only

Finds contacts in CompanyHub and gives back every match, which is the check that keeps your address book clean.

When to use it
a new lead comes in from a form and you want to know if the person is already in the CRM.
Watch out
no result is a valid answer too; plan a route for zero bundles, often Create a Contact.
CompanyHub28

Search Deals

SearchIn the docs only

Pulls up the deals that match your search, which lets a scenario act on a batch of opportunities rather than a single one.

When to use it
a customer emails and you want the open deals tied to that customer before replying.
Watch out
a broad search can return many deals, and each one consumes operations in the modules that follow.
CompanyHub29

Search Quote Products

SearchIn the docs only

Collects the product lines of quotes that match your search, one bundle per line, ready to count, compare or copy.

When to use it
you need every line of a quote to build a document or a summary in another app.
Watch out
if the next app expects one message with all lines, add an aggregator after this search so the lines are grouped first.
CompanyHub30

Search Quotes

SearchIn the docs only

Brings back the quotes that match your criteria, which lets a scenario review or update several quotes in one pass.

When to use it
a company changes its contact person and all its open quotes should be checked.
Watch out
the result can be empty; test with Run once and decide what the scenario does when no quote comes back.
CompanyHub31

Search Records

SearchIn the docs only

Finds records in CompanyHub and returns each match as a bundle, the search tool for data kept outside the dedicated modules.

When to use it
before Create a Record, to check whether the same entry already exists.
Watch out
several matches mean several runs of the next module; add a filter if only the first one should count.
CompanyHub32

Search Sales Orders

SearchIn the docs only

Lists the sales orders that match your search, so a scenario can follow up on a group of orders at once.

When to use it
a customer calls support and the agent needs that customer's orders pulled into the ticket.
Watch out
each order returned is its own bundle, so the operations add up quickly on a broad search.
CompanyHub33

Search Sales Orders Products

SearchIn the docs only

Returns the items of sales orders that match your criteria, one bundle per line, which is how you read everything an order contains.

When to use it
after Watch New Sales Order, to send the full list of items to your warehouse app.
Watch out
group the lines with an aggregator if the destination expects a single message rather than one per item.
CompanyHub34

Update a Company

ActionIn the docs only

Changes the details of a company already in CompanyHub, which keeps accounts current when the truth lives in another tool.

When to use it
your billing app gets a new address for a customer and the CRM should reflect it.
Watch out
the module needs the right company; find it with Search Companies first and check the match on a test run.
CompanyHub35

Update a Contact

ActionIn the docs only

Edits a contact that already exists, so a new job title or phone number reaches CompanyHub without manual work.

When to use it
Search Contacts found the person and the incoming data is fresher than what the CRM holds.
Watch out
an empty mapped value can overwrite good data; test with Run once on a dummy contact.
CompanyHub36

Update a Deal

ActionIn the docs only

Moves a deal forward in CompanyHub by changing its details from the scenario, whatever event happened elsewhere.

When to use it
a contract is signed in your e-signature tool and the matching deal should reflect the win.
Watch out
map the deal from Search Deals or from the trigger; a deal typed by hand is the quickest way to update the wrong opportunity.
CompanyHub37

Update a Quote

ActionIn the docs only

Changes a quote that is already in CompanyHub, which keeps it in step with approvals or feedback gathered outside the CRM.

When to use it
a manager approves a quote in a chat app and the quote in CompanyHub should record it.
Watch out
product lines have their own module; to change a single item, pick Update a Quote Product instead.
CompanyHub38

Update a Quote Product

ActionIn the docs only

Adjusts one product line on a quote without rebuilding the quote, a clean way to fix a single item.

When to use it
the customer asks for a different quantity on one item and the rest of the quote stays the same.
Watch out
map the line from Search Quote Products or Get a Quote Product so the change lands on the right item.
CompanyHub39

Update a Record

ActionIn the docs only

Edits an existing record in CompanyHub, the update step for data that the company, contact, deal, quote and order modules do not handle.

When to use it
another app changes an entry you mirror as a record and CompanyHub should stay aligned.
Watch out
locate the record with Search Records first, then test the scenario with Run once before switching it on.
CompanyHub40

Update a Sales Order

ActionIn the docs only

Modifies a sales order already in CompanyHub, so shipping or payment news from other tools shows up on the order.

When to use it
your carrier confirms delivery and the order in the CRM should say so.
Watch out
to change one item rather than the order, pick Update a Sales Order Product, which targets a single line.
CompanyHub41

Update a Sales Order Product

ActionIn the docs only

Edits a product line already on a CompanyHub sales order, so the order stays accurate without anyone reopening it by hand.

When to use it
a customer changes a confirmed order and the new details reach your scenario from a form or another app.
Watch out
place Search Sales Orders Products first to find the line; a search can return several bundles, and each one runs its own update.
Need help

Need help automating CompanyHub with Make?

A person reads every message.

FAQ

CompanyHub and Make: frequent questions

01Is the CompanyHub Make integration free?
Yes, you can start on Make's Free plan, because CompanyHub is a standard app available on every plan. 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 and remove the cap on active scenarios. You also need an active CompanyHub account, which CompanyHub bills on its own terms.
02What do you need to connect CompanyHub to Make?
You need an active CompanyHub account and two values from it: your subdomain and your API key. Both are on the Integrations page, which you reach from Settings in CompanyHub. In Make, add any CompanyHub module, click Create a connection, give the connection a name if you like, paste the two values and save. That one connection then serves every CompanyHub module in all your scenarios, so you never enter the key twice. If CompanyHub rejects it, copy both values again from the Integrations page.
03Do the CompanyHub triggers in Make fire instantly?
No. Judging by the module list (Make does not publish their type, it is inferred from their names), all 8 CompanyHub triggers are scheduled: Make checks CompanyHub on the scenario's schedule, every 15 minutes by default, and runs the scenario for whatever is new. There is no instant trigger for this app. On the Free plan the shortest interval is 15 minutes; paid plans allow checks down to 1 minute apart. You set the interval with the clock on the first module of the scenario, and Run once lets you test at any moment without waiting for the next check.
04What if the CompanyHub module you need is missing in Make?
Use Make an API Call. The CompanyHub app in Make includes this module, and it reaches any endpoint of the CompanyHub API with the connection you already set up. It asks you to write the request yourself, so keep the CompanyHub API documentation at hand and test each call with Run once. Also keep in mind that the Make documentation for CompanyHub is marked as AI-generated from the vendor's docs, so check important details with CompanyHub directly.
05Should you use Make or n8n for CompanyHub?
It depends on the criteria you care about, not on a single winner. On Make, CompanyHub comes with 49 modules, 8 scheduled triggers and Make an API Call for the rest, and it runs on the Free plan within that plan's limits. The same app often has an n8n node too, so compare the modules each side offers for your use case, the way each tool counts usage and which editor your team prefers. The n8n vs Make comparison linked above walks through those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations