Resources · Zapier integration

Acquire Zapier integrationAutomate Acquire with Zapier.

The Acquire Zapier integration gives you 6 triggers, 6 actions and 0 searches. Four triggers are instant, two are checked on a timer. Below: what each one does, what it costs on your plan, and the spots where a Zap built on Acquire usually breaks.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Acquire Zapier integration actually does for your team

Hooking Acquire up to Zapier lets a case, a contact or a company moving in Acquire start work in another tool, and lets other tools create or edit those same records in Acquire. Acquire is a customer communication platform where sales and support share the customer. Zapier is the layer that carries its events out and pushes data back in, with nobody retyping anything.

Three results show up again and again on support and sales teams. First, a case for every unhappy customer: Feedback Rating starts the Zap when a chat gets rated, a filter keeps only the ratings you care about, and Create Case opens a case so a support lead follows up. Second, company records that stay current: when an account changes in your CRM or billing tool, Update Company writes the change into Acquire, so the agent on the chat sees the right plan. Third, sales hears when support is done: Close Case starts a Zap that posts a short message in the channel an account manager actually reads.

Now the part the app page skips. Acquire exposes no search step on Zapier, so a Zap cannot look up an existing contact or company before it writes; it only works with what the trigger brought in. There is no delete action either, and nothing reaches back into history: a Zap only sees what happens after it is switched on.

No dedicated Acquire page exists on the Make or n8n side of this site. If you are still picking a platform, the Make vs Zapier and n8n vs Zapier comparisons lay out the criteria (price model, hosting, how much logic you need).

Vocabulary

Zapier words in one minute

Eight terms come back on every line of this page. Here they are in plain words, once.

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, like a new case in Acquire. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that creates, edits or sends something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling trigger
A trigger Zapier checks on a timer. It asks the app for its latest items at a fixed interval and keeps only the ones it has not seen.
Instant trigger
A trigger the app reports itself: Acquire calls Zapier the moment the event happens, so nothing waits for the next check.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it quietly otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
Cost

What an Acquire Zap really costs

Acquire is not a premium app on Zapier, so it works from the free plan. The bill is counted in tasks, and only actions make tasks.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks per month
  • Free plan Zap size2 steps: 1 trigger, 1 action
  • Premium appNo, free plan works

The trigger never costs a task, and neither does Zapier checking Acquire for new items, however often it looks. Each action that goes through counts once; an action that fails is not billed. A Zap with three actions therefore eats three times what a one-action Zap eats. The free plan gives you 100 tasks a month, as many Zaps as you like, but only two steps per Zap: the moment you add a filter or a second action, you need a paid plan. Polling triggers are checked on the interval of your plan, below; instant triggers skip that grid completely.

Connect

Connect your Acquire account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Acquire account linked once, then reused by every Zap step that touches Acquire.

  2. 02

    Find Acquire and confirm

    Type Acquire in the search box of the dialog, pick it from the list, then click Add connection. A new browser tab opens on the Acquire side, ready for your login.

  3. 03

    Sign in and grant access

    Log in to Acquire in that tab and allow Zapier to reach the account. You need an Acquire account of your own, plus read or write access on any record you do not own and want the Zap to touch.

First Zap

Your first Zap: turn a poor chat rating into a case

GoalEach time a chat gets a rating that matches your condition, open a case in Acquire so someone follows up.

  1. 01

    Create the Zap

    Start a new Zap. Pick Acquire as the trigger app and Feedback Rating as the event, and choose the connection you just added.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent ratings from your account, so you map the next steps on a real one instead of a guess.

  3. 03

    Add the filter

    From the plus icon, add Filter. Set the field to look at, the rule and the value. Pick a number rule for a score, a text rule for text, or the filter never passes.

  4. 04

    Add Create Case

    Add the action step, choose Acquire and Create Case, then map the details of the rated chat into the case so the person who picks it up has context.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the case shows up in Acquire, click Publish. This Zap has three steps, so it needs a paid plan.

Triggers

Acquire triggers: 4 instant, 2 on a timer

6 events start a Zap when something happens in Acquire, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Close Case

Instant trigger

In Zapier“Triggers when a case closed.”

This one fires when an agent marks a case as closed in Acquire, which makes it the natural end-of-story signal for anything that should follow a resolved conversation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an account manager wants to know a key customer's issue is settled before calling them, so the Zap posts a note in the sales channel.
Watch out
a case closed before the Zap was published never shows up; only closings that happen afterwards start a run.
2

Contact Update

Instant trigger

In Zapier“Trigger when a contact fields is updated.”

Edit any field on a contact in Acquire and this trigger starts the Zap with the updated record, so other tools hear about the change without someone forwarding it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a support agent corrects a customer's details during a chat and your CRM should get the corrected version too.
Watch out
never pair it with Update Contact on the same records; the action edits the contact, which fires the trigger again, and the loop drains your tasks.
3

Feedback Rating

Instant trigger

In Zapier“Triggers when a new Chat feedback is available.”

Customers who rate a chat in Acquire produce a new piece of feedback, and that rating is what starts the Zap here. It is the cleanest way to get the voice of the customer out of the chat tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a head of support wants every rating logged in a shared sheet, or only the bad ones turned into cases.
Watch out
keeping only some ratings means adding a filter, and a filter makes the Zap multi-step, so it needs a paid plan.
4

New Case

Instant trigger

In Zapier“Triggers when a new case is available.”

Every case created in Acquire, whoever opened it, kicks off the Zap with that new case. Think of it as the doorbell for incoming support work.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a team lead wants new cases mirrored into the project tool where engineers track bugs, without waiting on a manual hand-off.
Watch out
a Zap that answers New Case with Create Case writes where its own trigger listens and sets itself off again and again.
5

New Company

Polling trigger

In Zapier“Triggers when a new company is created.”

When a company record is added to Acquire, Zapier picks it up on its next check and passes it to the steps that follow. Good for anything that should happen once per new account.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a customer success manager wants each new account added to the onboarding tracker the team already uses.
Watch out
a bulk import of companies can return a huge batch at once, and Zapier's flood protection may hold it back.
6

New Contact

Polling trigger

In Zapier“Triggers when a new contact is created.”

Fresh contacts in Acquire are collected by Zapier on its regular check, and each one it has not seen before starts its own run of the Zap. Zapier remembers what it already passed on, so one contact does not fire twice.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a marketer wants new chat contacts added to the newsletter tool, where a short delay changes nothing.
Watch out
contacts already in Acquire before the Zap went live are not picked up.
Actions

Acquire actions: create records, then keep them current

Acquire gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Case

Action

In Zapier“Create Case in Acquire.”

Opens a new case in Acquire from data another step brought in, so the request lands in the support queue like any other.

When to use it
a form on your site collects bug reports and each one should become a case an agent owns.
2

Create Company

Action

In Zapier“Create Company in Acquire.”

Adds a company record to Acquire, which gives every chat with that account a home before the first conversation even starts.

When to use it
a deal is marked won in your CRM and the account should exist in Acquire before onboarding begins.
3

Create Contact

Action

In Zapier“Create Contact in Acquire.”

Puts a new person into Acquire, so agents recognise them on their first message instead of starting from an anonymous visitor.

When to use it
someone signs up for a webinar and the sales team wants them known in the chat tool.
Watch out
with no search step on Acquire, the Zap cannot check whether that person already exists first.
4

Update Case

Action

In Zapier“Update an existing Case Fields.”

Edits the fields of a case that already exists in Acquire, keeping it in step with what happened somewhere else.

When to use it
engineering ships the fix in the bug tracker and the matching case should reflect it.
Watch out
the Zap needs to know which case to edit, and only an earlier step can hand it that.
5

Update Company

Action

In Zapier“Update an existing Company Fields.”

Rewrites the fields of an existing company in Acquire, so the account details agents see match your system of record.

When to use it
finance moves a customer to another plan in the billing tool and support should see the new one during the next chat.
6

Update Contact

Action

In Zapier“Update an existing Contact Fields.”

Changes the fields of a person already stored in Acquire, which keeps titles, emails and owners from drifting apart across tools.

When to use it
a lead changes jobs in your CRM and the chat record should follow.
Watch out
fed by Contact Update on the same contact, it loops forever.
When it breaks

When an Acquire Zap breaks

Zapier lists no help article and no rate limit of its own for Acquire. What breaks here are the general rules of Zapier, and four of them bite on this app.

None of these shows up as an error message. The Zap simply does less, or much more, than you expected. If a run fails and you cannot see why, the Zapier troubleshooting guide walks through the usual checks.

  • Old records are never picked up

    A Zap only reacts to what happens after you publish it. Cases, contacts and companies already in Acquire stay where they are; moving that backlog is a separate job.

  • A Zap that keeps setting itself off

    Contact Update feeding Update Contact, or New Case feeding Create Case: the Zap writes where its own trigger listens, fires again, and burns through tasks fast.

  • A bulk import that stalls

    Import hundreds of contacts or companies at once and the polling triggers return a huge batch. Zapier's flood protection can hold that batch back.

  • Duplicates that do not happen

    On New Contact and New Company, Zapier tracks what it already saw, so the same record never starts the Zap twice. A missing run is rarely a double one.
Need help

Need help automating Acquire with Zapier?

A person reads every message.

FAQ

Acquire Zapier integration: the questions people ask

01Is the Acquire Zapier integration free?
Yes, up to a point. Acquire is not a premium app on Zapier, so you can connect it on the free plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps, one trigger and one action. A Zap that only logs new contacts somewhere else fits inside that. As soon as you add a filter, a second action, or chain Create Company and Create Contact in one Zap, it becomes multi-step and needs a paid plan.
02How many tasks does an Acquire Zap use?
One task per action that succeeds, and nothing for the trigger. Zapier checking Acquire for new companies or contacts is free too, however often it looks. So a Zap that answers Close Case with a message in your chat tool costs one task per closed case. Add a second action, say Update Contact after the message, and every closed case now costs two. An action that fails is not counted against your plan.
03Does Acquire trigger Zaps in real time?
Four of its six triggers do: Close Case, Contact Update, Feedback Rating and New Case are instant, so Acquire tells Zapier the moment the event happens, whatever your plan. New Company and New Contact are polling triggers: Zapier checks on a timer, every 15 minutes on the free plan, 2 on Professional, 1 on Team and Enterprise. That type is set by Acquire itself and cannot be changed from the Zap editor.
04What does it take to connect Acquire to Zapier?
An Acquire account and a Zapier account, nothing more for records you own. In Zapier, open Apps, click + Add connection, search Acquire, click Add connection, then sign in to Acquire in the tab that opens and grant access. If the Zap should touch cases, contacts or companies owned by someone else, your Acquire account also needs read or write access on them. The connection is then reused by every Zap step that uses Acquire.
05Why does an Acquire Zap run over and over?
Because it writes where its own trigger is listening. The classic case on Acquire is Contact Update starting a Zap whose action is Update Contact on the same person: the edit counts as a new update, the trigger fires again, and the loop eats your monthly tasks. The fix is to point the action at a different record type or a different tool, or to stop the loop with a filter, which then needs a paid plan.
06What if the Acquire action you need is not there?
Then Zapier simply does not offer it today. The integration has six actions, all about creating or updating cases, companies and contacts, with no delete action and no search step. Deleting a record, or looking one up before writing, has to be done in Acquire itself or through another route. Check the list on the app page from time to time, since the operations follow the version Acquire publishes on Zapier.
07Zapier, Make or n8n for Acquire?
It depends on your criteria rather than on a winner. Zapier has a ready-made Acquire app with four instant triggers, which is the shortest path if you want something running today without code. Billing per task matters if you plan many actions per event. If you need lookups before writing, a self-hosted setup, or a different pricing model, compare what Make and n8n offer for Acquire before you commit, and check whether a ready app exists there.
Same platform

Other docs you might need on this stack.

Browse all integrations