Resources · Zapier integration

AgencyComp Zapier integrationAutomate AgencyComp with Zapier.

The AgencyComp Zapier integration gives you 0 triggers, 5 actions and 5 searches. It writes agents, carriers, clients and policies into your commission tool and looks them up first, but something else has to start each run.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the AgencyComp Zapier integration actually does

AgencyComp is a commission tool for insurance: it calculates, projects and tracks what each product pays. The Zapier integration lets other apps write into it. It can create five kinds of records and find the same five kinds, but it cannot start an automation on its own, because it has no trigger.

Three results people build with it. A clean carrier list: a broker adds a new insurer to a shared sheet, and Create Carrier files it in AgencyComp under the same name, so nobody retypes it. Policies that land on the right client: an onboarding form comes in, Find Individual Client checks whether the person already exists, and Create Policy writes the policy with its client type and comp plan type. No duplicate agents: when a new producer signs on in your HR tool, the find-or-create version of Find Agent looks for that first and last name and only adds the agent if it is missing.

What Zapier does not do here matters just as much. There is no AgencyComp trigger, so nothing that happens inside AgencyComp (a new policy, a changed commission) can kick off a Zap. Every flow starts in another app and ends in AgencyComp. There is also no update or delete action: the integration creates and finds, and that is the full list.

If you are weighing other tools for the same job, the Make vs Zapier comparison sets the criteria side by side, and the Zapier review covers the platform itself.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on this page. Here they are once, in plain English.

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 on, Zapier waits for it. AgencyComp has none, so it comes from another app.
Action
What the Zap does once started: the step that writes, sends or moves something for you, like creating a policy in AgencyComp.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already in an app, such as an existing agent, so the steps after it can use what it found.
Cost

What an AgencyComp Zap really costs

Zapier bills tasks, and only successful actions count. The trigger in the other app costs nothing, however often Zapier checks it.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • BilledEach successful action
  • Not billedTriggers, checks, failed actions

Each AgencyComp record created is one task, and the free plan gives you 100 of them a month. A Zap that searches and then creates runs more than one step, so it becomes a multi-step Zap, the same as any Zap with a filter or a second action, and the free plan does not build those. An action that fails is not counted. AgencyComp is not a premium app, so a plain two-step Zap, one trigger and one action, works on the free plan.

Connect

Connect AgencyComp to Zapier in three steps

  1. 01

    Open your connections

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

  2. 02

    Pick AgencyComp

    Type AgencyComp in the search box of the dialog, select it, then click Add connection. You need an existing AgencyComp account; the integration does not create one for you.

  3. 03

    Sign in and grant access

    A new tab opens. Sign in to AgencyComp there and allow Zapier to reach the account. If you plan to write into records you do not own, make sure your user already has write access to them.

First Zap

Your first AgencyComp Zap: a policy from a sheet row

GoalWhen a new row lands in a policy sheet, find the carrier in AgencyComp, then create the policy.

  1. 01

    Build: start in the other app

    Create a Zap and pick the app and event that start it, here a new sheet row. AgencyComp has no trigger, so the start always lives elsewhere.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent rows of the connected sheet, so you map fields on a real one instead of a guess.

  3. 03

    Add the carrier search

    Add Find Carrier and map the sheet column holding the insurer into Carrier Name. This makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the policy action

    Add Create Policy. Fill Client Type with INDIVIDUAL, GROUP or WORKSITE, and Comp Plan Type with one of the five plan types AgencyComp lists.

  5. 05

    Test each step

    Run the search and the action once and read what came back. A search that finds nothing stops the Zap by default, which is easier to catch now than later.

  6. 06

    Publish

    Click Publish to switch the Zap on. From then on, every new row added to the sheet produces one policy in AgencyComp, tied to the carrier it found.

Actions

AgencyComp actions on Zapier

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

1

Create Agent

Action

In Zapier“Creates an Agent in AgencyComp.”

Adds a producer to AgencyComp so commissions can be tied to a real person from day one.

When to use it
a new hire is entered in your HR tool and should appear in the commission tool the same day.
Watch out
both First Name and Last Name are required, so a source that stores one full-name field needs splitting first.
2

Create Carrier

Action

In Zapier“Creates a Carrier in AgencyComp.”

Registers an insurance company in AgencyComp by name, ready for policies to point at it.

When to use it
your team keeps a running list of appointed insurers in a sheet and wants it mirrored.
Watch out
Carrier Name is the only required field, so spelling differences create near-duplicates.
3

Create Group Client

Action

In Zapier“Creates a Group Client in AgencyComp.”

Opens a group account in AgencyComp, the company or association that buys cover for its members.

When to use it
a signed employer contract in your CRM should become a group client without retyping.
Watch out
Group Name is mandatory; run Find Group Client first if the same employer may come back.
4

Create Individual Client

Action

In Zapier“Creates a Individual Client in AgencyComp.”

Records a single policyholder with a first and last name, so a personal policy has someone to attach to.

When to use it
a quote request form is completed and the prospect turns into a client.
Watch out
two people can share a name, so pair it with a search when your book is large.
5

Create Policy

Action

In Zapier“Creates a Policy in AgencyComp.”

Writes a policy into AgencyComp with the client type and the compensation plan type that drive the commission math.

When to use it
a bound policy in your agency system should start counting toward commission tracking.
Watch out
Client Type accepts INDIVIDUAL, GROUP or WORKSITE, and Comp Plan Type accepts FEE, GRADED, MA_PDP, PERCENTAGE_OF_PREMIUM or TARGET_PREMIUM; any other value fails.
Searches

AgencyComp searches, and the find-or-create switch

5 search steps look for data that already exists in AgencyComp, so a later step can use it.

Searches sit at the bottom of the Action event list, under SEARCH. Each one also shows a find-or-create line in the editor; that is the same search with a box ticked, not an extra operation. Some action fields also offer + Add search step, which inserts the lookup for you.

1

Find Agent

SearchFind or create

In Zapier“Finds an Agent in AgencyComp.”

Looks up a producer by first and last name and hands the match to later steps.

When to use it
before crediting a policy, confirm the selling agent already exists.
Watch out
the editor also lists Find or Create Agent; it is this search with creation switched on, and it adds the agent when no match turns up.
2

Find Carrier

SearchFind or create

In Zapier“Finds a Carrier in AgencyComp.”

Checks AgencyComp for an insurer by its carrier name, so a policy never points at a missing company.

When to use it
the incoming record names a carrier and the policy step needs it confirmed first.
Watch out
Find or Create Carrier is the same lookup with the create box ticked, handy when new insurers show up often.
3

Find Group Client

SearchFind or create

In Zapier“Finds an Group Client in AgencyComp.”

Searches group accounts by name so an employer is never opened twice.

When to use it
a renewal arrives for a company you may already serve.
Watch out
the variant Find or Create Group Client reuses this search and creates the group only when the name is not found.
4

Find Individual Client

SearchFind or create

In Zapier“Finds an Individual Client in AgencyComp.”

Finds a policyholder from first and last name, both required.

When to use it
a family member buys a second product and should land on the existing record.
Watch out
with common names, set the multiple-results rule on purpose; Find or Create Individual Client is this search plus automatic creation.
5

Find Policy

SearchFind or create

In Zapier“Finds a Policy in AgencyComp.”

Retrieves a policy from its policy number, the one field it needs.

When to use it
an endorsement email quotes a number and a later step needs the matching policy.
Watch out
Find or Create Policy is not a separate operation; with creation on, it also wants the client type and comp plan type.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on without the match.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into find-or-create: the setting above 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.
When it breaks

When an AgencyComp Zap breaks

Zapier links no help article to AgencyComp, so the failures below are the general ones. They still bite hard on a write-only integration.

Most surprises come from timing and volume rather than from AgencyComp itself. When a Zap misbehaves, the Zapier troubleshooting guide walks through the editor checks.

  • Old records are not imported

    A Zap reacts only to what happens after you publish it. Agents and policies already in your sheet stay where they are; moving that backlog is a separate job.

  • A loop that eats your tasks

    If the Zap writes into the very sheet or app its trigger watches, each write starts it again, and the task count drains fast.

  • A bulk import gets held back

    When the trigger app suddenly returns a huge batch, after a migration for instance, Zapier's flood protection can hold those items instead of creating them all.

  • Duplicates that are not Zapier's fault

    Zapier remembers what a polling trigger already saw, so one row never fires twice. Duplicate clients usually mean a missing search step before the create.
Need help

Need help automating AgencyComp with Zapier?

A person reads every message.

FAQ

AgencyComp Zapier integration: questions people ask

01Is the AgencyComp Zapier integration free?
Yes, for simple Zaps. AgencyComp is not reserved to paid plans, so the free plan can run it with its 100 tasks a month and unlimited Zaps. The catch is size: on the free plan a Zap holds exactly two steps, one trigger and one action. Since AgencyComp has no trigger, that means one event in another app and one AgencyComp action. As soon as you add a search before creating a record, or a filter, the Zap becomes multi-step and needs a paid plan. You also need an AgencyComp account of your own.
02How many tasks does an AgencyComp Zap use?
One task per AgencyComp action that succeeds. A Zap that creates an agent costs one task each time it runs. A Zap that searches for a carrier and then creates a policy completes two steps, so plan on two. The trigger in the other app is free, and so are the checks Zapier makes to look for new items. An action that fails is not counted against your plan. If a Zap writes back into the place its trigger watches, it can restart itself and burn through tasks quickly.
03Does AgencyComp sync with Zapier in real time?
It depends entirely on the app that starts the Zap, because AgencyComp has no trigger. If that app offers an instant trigger, it tells Zapier the moment something happens and the Zap runs straight away, on any plan. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. The AgencyComp action itself runs as soon as the Zap reaches it.
04What does it take to connect AgencyComp to Zapier?
An active AgencyComp account and a few clicks. From the Apps page in Zapier, click + Add connection, search for AgencyComp, then click Add connection. A tab opens where you sign in to AgencyComp and allow Zapier in. The connection is reused by every step afterwards. If the Zap will write into records owned by colleagues, your user needs write access to them. Test with a record you own before pointing the Zap at shared data.
05Why does Create Policy keep failing?
Almost always because of its two required fields. Client Type only accepts INDIVIDUAL, GROUP or WORKSITE, and Comp Plan Type only accepts FEE, GRADED, MA_PDP, PERCENTAGE_OF_PREMIUM or TARGET_PREMIUM. If your form or sheet sends something like Employer or Commission percent, the action rejects it. Map a fixed value in the editor, or clean the source column so it carries one of those exact words. A failed action does not cost a task, but the policy is not written either.
06What if the AgencyComp operation you need is not there?
Then the integration cannot do it today. The list is short: five create actions and five searches, with no trigger, no update and no delete. Changing a commission or reacting to a new policy inside AgencyComp is out of reach from Zapier. A workable pattern is to keep the source of truth in the other app and let AgencyComp receive. Before you plan around a missing update, look again at the AgencyComp page on zapier.com, which carries the live list.
07Zapier, Make or n8n for AgencyComp?
Judge on criteria, not on brand. On Zapier, AgencyComp has a ready connector with ten operations and needs no code, which suits a team that wants to start quickly. Whether Make or n8n carry a ready AgencyComp module is worth checking on their own sites before you compare. The useful questions are how many records you push into AgencyComp each month, whether each create needs a search first, and who on the team fixes a Zap when a policy is rejected.
Same platform

Other docs you might need on this stack.

Browse all integrations