- Home
- Resources
- Integrations
- CompanyHub
CompanyHub Zapier integrationAutomate CompanyHub with Zapier.
The CompanyHub Zapier integration gives you 8 triggers, 9 actions and 1 search. Below: what each one does, what it costs on your plan, how to link the account and the traps worth knowing before your first CRM automation goes live.
Verified Trustpilot reviews · AI, automation & growth agency
What the CompanyHub Zapier integration actually does
CompanyHub is a CRM you shape to your own sales process, with custom tables and your own logic. Hooking it to Zapier means letting another tool react when something lands in it (a company, a deal, a quote), or letting another tool write into it without anyone copying data by hand.
Three outcomes cover most of what sales teams build here. No deal without a next step: New Deal starts the Zap and Create Task puts a dated to-do on a named owner, so a fresh opportunity never sits untouched. Paperwork that writes itself: a deal or a form elsewhere feeds Create Quote or Create Sales Order, line items included, instead of someone retyping product and quantity. A clean record trail: Create Note pins context onto any record, and Find Record checks a table before a duplicate gets created.
Now the limits. Every trigger here is checked on a timer, so on the free plan a new deal can wait up to 15 minutes before the Zap notices it. There is no delete action, so cleanup stays manual. Only one search exists, and it looks inside a table you name, not across the whole CRM. And nothing that happened before you switch the Zap on gets picked up later.
If you are weighing other tools, the CompanyHub Make integration covers the same CRM from Make, and n8n vs Zapier sets the two side by side.
Zapier words, in plain English
Seven terms come back on every line of this page. Read them once and the rest goes fast.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it to happen.
- Action
- What the Zap does once started: the step that writes, sends or moves something in an app on your behalf.
- Task
- The unit Zapier bills you for: one action your Zap completes successfully. Your plan allowance counts those, nothing else.
- Polling vs instant
- A polling trigger is checked on a timer, Zapier asking the app for new items. An instant one is pushed by the app the moment it happens.
- Filter
- A step that lets the Zap continue only when the incoming item meets a condition you set, and quietly stops it otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps after it can use what it found.
What a CompanyHub Zap costs you
CompanyHub is not a premium app on Zapier, so it works from the free plan. What you pay for is tasks.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps only
- Trigger checksFree, whatever the interval
- Failed actionNot counted
The trigger never costs a task, and neither does Zapier checking CompanyHub for new records, however often it looks. Each action that succeeds counts as one task; one that fails costs nothing. A Zap with three actions burns three times what a one-action Zap does. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a second action, a filter or a search and you have a multi-step Zap, which needs a paid plan.
Connect CompanyHub to Zapier in three steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A connection is your CompanyHub account linked once, then reused by every Zap that touches it.
- 02
Pick CompanyHub
Type CompanyHub in the search box of the dialog, select it, then click Add connection. You need an existing CompanyHub account for this; Zapier does not create one for you.
- 03
Sign in and allow access
Log in to CompanyHub in the tab that opens and grant Zapier access. If the Zap will touch tables or records you do not own, make sure your user has read or write rights on them first.
Your first Zap: every new deal gets a task and a note
GoalWhen a deal is created, assign a follow-up task to a sales rep and leave a note on the deal saying the task exists.
- 01
Start the build
Create a Zap and pick CompanyHub with the New Deal event as the starting point. Choose your connection, the one you added above.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent deals from your account, so you map fields on a real one instead of guessing.
- 03
Add the task
Add CompanyHub Create Task. Write a task title that names the deal, then pick the owner, a category, a due date and a status.
- 04
Attach the note
Add Create Note, point it at the deals table and the deal from step one, and write a short line saying a follow-up was scheduled.
- 05
Test, then publish
Test each action once and check the result in CompanyHub. Then Publish. Two actions make this a multi-step Zap, so it needs a paid plan.
CompanyHub triggers on Zapier
8 events start a Zap when something happens in CompanyHub. Zapier checks for them at the interval your plan allows.
New Company
Polling triggerIn Zapier“Triggers when a new company is created.”
Starts your Zap each time a company record is created in CompanyHub. You get the new account to hand to the next step.
New Contact
Polling triggerIn Zapier“Triggers when a contact is created.”
Fires on every person added to CompanyHub. It is the hook for anything that should happen to a human the moment they enter your CRM: a welcome sequence, a heads-up to the owner, a row in a sheet.
New Deal
Polling triggerIn Zapier“Triggers when a new deal is created.”
Watches the pipeline and reacts when an opportunity is opened. This is the trigger behind most follow-up automations: the deal exists, so somebody should now do something about it.
New Quote
Polling triggerIn Zapier“Triggers when a new quote is created.”
Kicks off when someone drafts a quote in CompanyHub. Useful when the quote is the moment finance, legal or a manager needs to know a number has gone out.
New Record (Custom Table)
Polling triggerIn Zapier“Triggers when a new record is created in a specified custom table.”
CompanyHub lets you build your own tables, for contracts, assets, tickets or anything else. This trigger listens to one of them and fires on each new row there.
New Sales Order
Polling triggerIn Zapier“Triggers when a new Sales Order is created.”
Goes off once an order is booked in CompanyHub. This is where sales hands over to operations, so it is the natural start for invoicing, shipping or stock steps.
New Task
Polling triggerIn Zapier“Triggers when a new task is created.”
Reacts to each task created in CompanyHub. It lets you mirror the CRM to-do list somewhere your team actually looks during the day.
Record Updated
Polling triggerIn Zapier“Triggers when an existing record is updated.”
The only trigger here that looks at changes rather than new entries. Pick a table and the Zap fires whenever an existing record in it is edited.
CompanyHub actions on Zapier
CompanyHub gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Company
ActionIn Zapier“Creates a new company.”
Adds an account to CompanyHub from wherever it first shows up, a signup form, a billing tool, a spreadsheet.
Create Contact
ActionIn Zapier“Creates a new contact.”
Drops a person into CompanyHub with whatever details the previous step carried, so leads stop living in inboxes.
Create Deal
ActionIn Zapier“Creates a new deal.”
Opens an opportunity in your pipeline from an outside signal, so a hot request is tracked from the first minute.
Create Note
ActionIn Zapier“Creates a note for a record of specified table.”
Attaches a written note to any record in a table you choose, which keeps context next to the deal or contact it belongs to.
Create Quote
ActionIn Zapier“Creates a quote with line items.”
Builds a quote with line items in CompanyHub. A company, a status, a bill-to name, a product and a quantity are all mandatory.
Create a Record (Custom Table)
ActionIn Zapier“Creates a new record in custom table.”
Writes a new row into one of your own CompanyHub tables, the ones you designed for your business.
Create Sales Order
ActionIn Zapier“Creates a new Sales Order with line Items.”
Turns incoming data into a booked order with line items, covering company, subject, status, bill-to name, product and quantity.
Create Task
ActionIn Zapier“Creates a new task.”
Puts a to-do on someone's plate in CompanyHub, with an owner, a category, a deadline and a status all required.
Update Record
ActionIn Zapier“Updates a record in specified table.”
Edits an existing record in the table you pick, rather than adding a new one.
Finding a CompanyHub record before you write
1 search step looks for data that already exists in CompanyHub, so a later step can use it.
A search step looks up something that already exists, so the actions after it can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Some fields also offer + Add search step, which slots one in just before and wires the result for you. How exact the match must be is up to CompanyHub, not Zapier.
Find Record
SearchFind or createIn Zapier“Finds an existing record in specified table that matches your search query.”
Looks inside one CompanyHub table you name and returns the record matching your search value. Both the table and the search query are required.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps relying on it are skipped. Switch it on and the Zap carries on with empty values.
- Create X if it doesn't exist yet?Ticking this box turns the search into a find-or-create: the setting above disappears and Zapier asks for the fields needed to create the missing item.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When a CompanyHub Zap breaks
Zapier lists no help article and no app-specific limit for CompanyHub. What goes wrong here is what goes wrong on any CRM Zap.
Four cases are worth knowing before you publish. If a Zap fails anyway, the Zapier troubleshooting page is the place to start.
The old records never show up
A Zap only reacts to what happens after it is switched on. The deals and contacts already in CompanyHub are not sent; moving that backlog is a separate job.The Zap keeps firing itself
Record Updated plus Update Record on the same table, or New Contact plus Create Contact: the Zap writes where its trigger watches and burns tasks in a loop.A bulk import gets held back
After a migration or a large import, the trigger suddenly sees a huge batch. Zapier's flood protection can pause it rather than run everything at once.Duplicates that are not duplicates
Zapier remembers what it already saw on a polling trigger, so one record never starts the Zap twice. A double usually comes from two Zaps, or a Create without a Find.
Need help automating CompanyHub with Zapier?
A person reads every message.



