Resources · Zapier integration

Act! Zapier integrationAutomate Act! with Zapier.

The Act! Zapier integration gives you 3 triggers, 7 actions and 2 searches for contacts, opportunities, notes, activities and groups. Every trigger is polled, the app runs on the free plan, and the traps sit in the required fields.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Act! Zapier integration actually does

It links your Act! CRM to the other tools you use, without code. Zapier watches Act! for new contacts, edited contacts and new opportunities, and it can write back into Act!: contacts, notes, activities, history entries, opportunities and groups. You build each link once, and it keeps running on its own.

A scheduled follow-up on every fresh deal. When a sales rep logs an opportunity, New Opportunity starts the Zap and Add Activity books the next call with the contact. Nobody has to remember to put it in the calendar.

A clean contact base fed from outside. A webinar sign-up or a support ticket elsewhere becomes an Act! record through Find or Create Contact, which checks first and only creates when nothing matches. Duplicates stop piling up.

A paper trail other teams can read. Each time a contact is edited, Contact Updated can push that change to a spreadsheet or a chat channel, so finance or support sees what sales changed without logging into the CRM.

What it doesn't do: none of the three triggers is instant, so an event in Act! waits for the next check. There is no trigger on new notes, activities or history entries, no operation to delete anything, and no search for opportunities. If a step you want is missing, you'll need a workaround or another tool. For a side-by-side view of the alternatives, read Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

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

Zap
The automation you set up in Zapier: one starting event, then one or more steps that run every single time that event shows up.
Trigger
The event that starts a Zap, such as a new contact in Act!. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like adding a note in Act!.
Task
The unit Zapier bills. One task is one action that your Zap finished successfully, and your plan counts nothing else.
Polling vs instant
A polling trigger is checked on a timer for anything new. An instant one is pushed by the app itself the moment it happens.
Filter
A step that lets the Zap carry on only when the incoming data meets the condition you chose, and quietly stops it otherwise.
Search step
A step that looks up something already stored in an app, so the following steps can reuse what it found.
Connection
Your Act! account linked to Zapier one time, then reused by every step in every Zap that touches Act!.
Cost

What an Act! Zap really costs

Act! isn't a premium app, so it works on the free Zapier plan. Your bill is counted in tasks, and the trigger never costs one.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • BilledEach successful action
  • Not billedTriggers, checks, failed actions

Checking Act! for new records is free, however often it happens. Each action that succeeds counts as one task, and a failed one counts for nothing. A Zap with three actions uses three times what a single-action Zap uses. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a search or a second action and you have a multi-step Zap, which needs a paid plan.

Connect

Connect your Act! account to Zapier

  1. 01

    Open the Apps page

    From your Zapier account, go to Apps and click + Add connection. You need an Act! login first, plus rights on any record you don't own and want the Zap to touch.

  2. 02

    Pick Act! and confirm

    Type Act! in the search box of the dialog that appears, select it, then click Add connection. A new browser tab opens on the Act! side, ready for the sign-in.

  3. 03

    Sign in and grant access

    Log into Act! in that tab and allow Zapier to use the account. The connection then appears in your list, and every future Act! step in any Zap reuses it.

First Zap

Your first Zap: book a call on qualified deals

GoalWhen a sales rep logs a new opportunity in Act!, a filter keeps only the ones worth chasing, a search finds the contact, and Act! gets a scheduled call with them.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Act! as the starting app and New Opportunity as the event. Then select the Act! connection made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent opportunities from your account, so pick a real one to map the next steps on.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field, the rule and the value. Mind the type: a text rule never matches a number.

  4. 04

    Find the contact

    Add Find or Create Contact, choose the field to search by and map the value from the opportunity. Its result feeds the Schedule With box.

  5. 05

    Schedule the activity

    Add Add Activity, set the activity type, the start and end times, and the contact from the search. Test the step and check the result in Act!.

  6. 06

    Publish

    Click Publish to switch the Zap on. This one has four steps, so it needs a paid plan. On the free plan, keep the trigger and the activity only.

Triggers

Act! triggers: 3 events that start a Zap

3 events start a Zap when something happens in Act!. Zapier checks for them at the interval your plan allows.

1

New Contact

Polling trigger

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

Fires on each contact freshly created in Act!, whoever entered it: a rep typing a business card, an import, or another Zap. It hands the new record to the following steps so you can greet, tag or copy it elsewhere.

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
you want every new lead in the CRM to land in your mailing tool or your support desk without a manual export.
Watch out
contacts that existed before you published the Zap are never picked up.
2

Contact Updated

Polling trigger

In Zapier“Triggers when a Contact is updated.”

Reacts when an existing Act! contact is edited, not when one is added. It's the right starting point for keeping a second tool in step with the CRM after someone corrects a phone number or a company name.

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
your billing sheet or helpdesk must reflect contact changes made by the sales team.
Watch out
pairing it with Update Contact on the same record makes the Zap restart itself in a loop and eat tasks fast.
3

New Opportunity

Polling trigger

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

Starts a Zap whenever a deal is opened in Act!. This is the trigger to reach for when the pipeline, not the address book, should drive the next move: alert a manager, prepare a quote, or schedule a first call.

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
each new deal should create a follow-up activity on the contact it belongs to.
Watch out
there is no Act! trigger for a deal changing stage, only for a new one.
Actions

Act! actions: what a Zap can write into your CRM

Act! gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Activity

Action

In Zapier“Adds an activity to a contact.”

Puts a scheduled activity on a contact's calendar in Act!: you set its type, who it is scheduled with, and a start and end time, all four required. A private flag is optional.

When to use it
a demo booked on your website should become a call slot for the rep.
Watch out
both times are mandatory, even for a short call.
2

Add Note

Action

In Zapier“Adds a note to a contact.”

Attaches a written note to a contact, with the contact and the text both required. Notes are public by default and can be marked private.

When to use it
a survey answer or a chat transcript should be readable on the contact sheet.
Watch out
a private note is visible to the connected user only.
3

Add Opportunity

Action

In Zapier“Creates a new opportunity.”

Opens a deal in Act!, tied to a contact and to an estimated close date, both of which are required.

When to use it
a signed quote or an accepted proposal in another tool should show up in the Act! pipeline.
Watch out
without a date the step fails, so map one or compute it before.
4

Add Contact

Action

In Zapier“Creates a new contact.”

Creates a brand-new contact record in Act! from data captured somewhere else.

When to use it
a form, a booking tool or an event list should fill the CRM without retyping.
Watch out
it creates blindly, so the same person can appear twice; Find or Create Contact avoids that.
5

Add History

Action

In Zapier“Adds a history to a contact.”

Logs something that already happened on a contact's history in Act!. It needs a type, the contact, a start time and an end time; a private option exists too.

When to use it
a call made in your phone system should leave a trace in the CRM after the fact.
6

Add Group

Action

In Zapier“Creates a new group.”

Makes a new group in Act! from a single required field: its name, which must be unique.

When to use it
each new event, campaign or territory created elsewhere deserves its own group of contacts in the CRM.
Watch out
a name already in use clashes, so run Find Group first.
7

Update Contact

Action

In Zapier“Updates a new contact.”

Changes an existing Act! contact instead of making a new one. The only required field is the contact to edit, which a search step usually provides.

When to use it
a customer changes details in your billing tool and the CRM must follow.
Watch out
never feed it from Contact Updated on the same record.
Searches

Act! searches: look up before you write

2 search steps look for data that already exists in Act!, so a later step can use it.

A search step finds a record that already exists so the next steps can use it. In the editor, Act! searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result isn't a clean single match.

1

Find or Create Contact

SearchFind or create

In Zapier“Finds or creates a contact.”

Looks for a contact using a field you choose and the value you map into it, both required. The editor also lists a find-or-create line under the same name: same search, box ticked, no extra operation.

When to use it
before Add Note or Add Activity, so the contact field always has a match.
2

Find Group

SearchFind or create

In Zapier“Looks up groups in Act!”

Checks whether a group already exists in Act!, then hands it to the steps after it. The editor shows Find Group twice: the second line is the find-or-create version of this same search, not an extra operation.

When to use it
before Add Group, to check the name isn't taken already.
Watch out
whether the match must be exact is decided by Act!, not by Zapier.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap right there and the dependent steps are skipped. Switch it on and the Zap goes on with nothing in hand.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the previous setting disappears and Zapier asks for the fields needed to create the missing record.
  3. If multiple search results are found?
    Three exits when several records match: keep the first one (the default), stop the Zap, or pass all of them on together.
When it breaks

When an Act! Zap breaks

Zapier publishes no help article dedicated to Act!, so the failures below are the general ones that hit CRM Zaps hardest.

Most broken Act! Zaps come from four causes. None of them shows up as an error on day one; they appear once real data flows. If a Zap still won't behave, the Zapier troubleshooting page is the next stop.

  • The old contacts never arrive

    A Zap only reacts to what happens after you switch it on. The contacts and deals already in Act! are ignored, and moving that backlog is a separate job.
  • The Zap keeps restarting itself

    Contact Updated followed by Update Contact on the same record writes where the trigger watches. Each run sets off the next one and the task count drains quickly.
  • A bulk import stalls

    After a mass import into Act!, a trigger can suddenly return a huge batch. Zapier's flood protection can hold that batch back instead of running it all.
  • No duplicate runs, by design

    On a polling trigger, Zapier remembers what it has already seen, so the same contact or deal never starts the Zap twice. Edits go through Contact Updated.
Need help

Need help automating Act! with Zapier?

A person reads every message.

FAQ

Act! Zapier integration: frequently asked questions

01Is the Act! Zapier integration free?
Yes, as long as your Zap stays at two steps. Act! is not a premium app, so the free Zapier plan accepts it, with 100 tasks a month and unlimited Zaps. The free plan stops at one trigger plus one action, though. As soon as you add a filter, a search such as Find or Create Contact, or a second action, the Zap becomes multi-step and needs a paid plan. Plan for that early if your contacts come from outside the CRM.
02How many tasks does an Act! Zap use?
One per action that succeeds, and nothing else. The trigger is free, the regular checks for new contacts or opportunities are free, and an action that fails is not counted. A Zap that adds a contact, then a note, then an activity uses three tasks per run. Watch the loop case: Contact Updated paired with Update Contact on the same record restarts the Zap again and again, and each restart bills its actions.
03Does Act! send data to Zapier in real time?
No. All three Act! triggers are polling triggers, so Zapier checks the account on a timer rather than being told the moment something changes. On the free plan the check runs every 15 minutes; on Professional it drops to 2 minutes, and on Team and Enterprise to 1 minute. Paid plans can also adjust the timing and run a check by hand from the editor. The trigger type comes from Act! itself and cannot be switched.
04What does it take to connect Act! to Zapier?
An Act! account you can sign in to, and read or write rights on any record you don't own but want the Zap to touch. The link itself happens from the Apps page of Zapier with + Add connection, a search for Act!, a click on Add connection, then a sign-in in the tab that opens and an approval. After that, every Act! step in every Zap reuses the same connection.
05Why does an Add Activity or Add Note step fail?
Usually because the Contact field is empty or points to someone who doesn't exist in the connected account. Add Activity requires the contact it is scheduled with, a type, and both start and end times; Add Note needs the contact and the note text. When your data starts in another app, put Find or Create Contact in front of the action so it always receives a valid contact. That search makes the Zap multi-step, which means a paid plan.
06What if the Act! operation needed isn't listed?
Then it doesn't exist on Zapier today. The integration has three triggers, seven actions and two searches, and nothing to delete records, follow a deal through its stages, or search opportunities. Two existing steps sometimes cover the gap: Find or Create Contact followed by Update Contact edits a record coming from another tool. Otherwise, another platform may reach Act! differently. Compare the options before committing, because rebuilding a pipeline of Zaps later costs more than choosing well at the start.
07Zapier, Make or n8n for Act!?
It depends on your criteria rather than on a winner. Zapier wins when you want the quickest setup with the operations listed here and a free plan that already accepts Act!. It loses ground if you need instant triggers, delete operations or many steps per run on a tight budget, since every successful action is billed. Check which platform covers the exact Act! events you rely on, then weigh pricing model, hosting and how much logic each Zap carries.