Resources · Zapier integration

Agillic Zapier integrationAutomate Agillic with Zapier.

The Agillic Zapier integration gives you 1 trigger, 6 actions and 2 searches. Most of the value sits on the action side: keeping recipients up to date, logging rows in One-to-Many tables and firing Agillic events from whatever tool captured the data first.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Agillic Zapier integration is good for

It connects Agillic, a customer marketing platform, to Zapier, a tool that chains apps together without code. Zapier can create, update and delete recipients, write to their One-to-Many tables (the per-person tables that hold repeated rows, such as purchases or bookings), trigger Agillic events and look recipients up. One trigger exists, and it is a narrow one.

Profiles that stay current. A lead fills in a form on a landing page. Update or Create Recipient writes the answers into Agillic, and creates the person if the identifier is new. No CSV export, no manual import.

Journeys started from outside Agillic. A SaaS team wants an onboarding flow to start when a trial is activated in another tool. Achieve Event marks the event for that recipient, and whatever the Agillic instance has configured for that event follows.

History kept per customer. An e-commerce manager logs each order as a row with Create/Update a One-To-Many Record, so campaigns can target based on what people actually bought.

What Zapier does not do here: it does not tell you when a recipient changes in Agillic. The only trigger, Get OTM Tables, fetches the One-to-Many tables available in the instance, not the people in them. So Agillic is almost always the destination of a Zap, rarely its starting point. If that one-way setup is a dealbreaker, open the Make vs Zapier and n8n vs Zapier comparisons.

Vocabulary

Zapier vocabulary in one minute

Eight words come back throughout this page. Here they are in plain English.

Zap
A workflow on Zapier made of one trigger followed by one or more actions, which run again every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier keeps an eye out for it.
Action
What the Zap does after it starts: the step that writes, updates or deletes something for you in an app.
Task
What your plan counts and bills: each action that ends in success uses one task, while the trigger and failed actions use none.
Polling vs instant trigger
A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app the moment the event happens.
Filter
A checkpoint step: the data that arrived must meet the condition you set, otherwise the Zap stops right there.
Search step
A step that looks up something already in an app, such as a recipient, so later steps can use what it found.
Connection
Your Agillic account linked to Zapier once, then reused by every step of every Zap that talks to Agillic.
Cost

What an Agillic Zap really costs

Agillic is not a premium app, so it works from the free plan. You pay for actions, not for watching.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • Trigger cost0 tasks
  • Agillic trigger1 polling, 0 instant

The trigger never costs a task, however often Zapier checks. Each action that succeeds counts once, so a Zap that updates a recipient and then achieves an event uses two tasks per run. A failed action is not counted. The free plan gives 100 tasks a month, polling every 15 minutes, and two-step Zaps only. Adding a search step, a filter or a second action turns it into a multi-step Zap, which needs a paid plan. A Zap that looks a recipient up with Find and Get Recipient before writing to them is already one.

Connect

Connect Agillic to Zapier in 3 steps

  1. 01

    Open the connections page

    Start from the Apps page of your Zapier account and click + Add connection. Before that, make sure your Agillic login can read or write the recipients and One-to-Many tables your Zaps are meant to change.

  2. 02

    Pick Agillic

    In the dialog, search for Agillic by name and pick it from the results. Click Add connection: Zapier opens a separate tab where Agillic asks you to sign in.

  3. 03

    Sign in and grant access

    Sign in with your Agillic credentials in that tab, then grant Zapier access to the account. From now on, any Zap step that uses Agillic picks this connection without asking again.

First Zap

Your first Agillic Zap: flag every new One-to-Many table

GoalThe One-to-Many tables available in your Agillic instance reach the marketing team in its shared channel, filtered by your naming rule.

  1. 01

    Build: set the trigger

    Create a Zap, choose Agillic as the app and Get OTM Tables as the event, then pick your connection. It is a polling trigger, so the interval of your plan applies.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent tables of the instance, so the next steps are mapped on a real table instead of a blank sample.

  3. 03

    Add a filter

    Click the plus icon, pick Filter, then set the field, the rule and the value. Only the tables you care about go on. This makes the Zap multi-step: paid plan.

  4. 04

    Add the message step

    Add your team chat app as the action and write the message, inserting the table details that came back from the trigger test.

  5. 05

    Test, then publish

    Test the action once and check the message arrived. Then click Publish. From then on, Zapier checks Agillic at your plan's interval.

Triggers

Agillic trigger

1 event starts a Zap when something happens in Agillic. Zapier checks for them at the interval your plan allows.

1

Get OTM Tables

Polling trigger

In Zapier“Get the Available One-to-many tables from your Agillic instance”

Brings back the One-to-Many tables available in your Agillic instance: the tables themselves, not the recipients and not the rows stored inside them. That makes it a niche starting point, mostly for teams that look after how the instance is organized.

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 marketing ops lead who wants the instance's One-to-Many tables listed in a shared channel.
Watch out
do not expect a new customer or a new purchase to fire it; for those, the trigger has to come from another app.
Actions

Agillic actions

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

1

Achieve Event

Action

In Zapier“Achieves an Agillic Event for a specific Recipient. The event achieved can have various side-effects, configured in your Agillic Instance.”

Marks a named Agillic event as reached for one recipient. What follows depends entirely on how that event is configured in your instance.

When to use it
a signal from another tool, like a demo booked, should start an Agillic flow for that person.
Watch out
three fields are required: the identifier field, its value and the event name.
2

Delete a Recipient

Action

In Zapier“Deletes a Recipient”

Removes a recipient from Agillic, found through a unique identifier field and its value. It is the cleanest way to act on a deletion request coming from another system.

When to use it
a privacy request logged in a helpdesk should erase the person in Agillic too.
Watch out
a wrong identifier value deletes the wrong person, so test the Zap on a dummy recipient first.
3

Create/Update a One-To-Many Record

Action

In Zapier“Create or updates a record in a recipient's One-to-Many Table”

Adds or updates a row in one of a recipient's One-to-Many tables, picked from a list. An option decides whether empty values are sent too.

When to use it
each order, booking or ticket should live as its own line in the customer's history.
Watch out
the table is picked from a list, so it has to exist in your instance before the Zap can write to it.
4

Truncate Recipient OTM Table

Action

In Zapier“Truncate (removes all rows) from a Recipient's One-to-Many Table”

Empties one One-to-Many table for one recipient: every row goes, the table itself stays. Other recipients are not touched.

When to use it
you rebuild a customer's list from scratch, wiping it before writing the fresh rows.
Watch out
the identifier value decides whose rows go. A wrong value empties the wrong person's table.
5

Update or Create Recipient (Limited Fields)

Action

In Zapier“Updates a Recipient in your Agillic Instance for the data fields present. If the Recipient does not exist with the unique identifier provided, one will be created.”

Same update-or-create logic, but driven by numbered field slots: you name each Agillic field, then give its value. Field 1 and Field 11, with their values, are marked required.

When to use it
only when the full version does not suit your instance and you prefer to name fields one by one.
Watch out
every required slot must be filled, or the step will not run.
6

Update or Create Recipient

Action

In Zapier“Updates a Recipient in your Agillic Instance for the data fields present. If the Recipient does not exist with the unique identifier provided, one will be created.”

Writes data onto a recipient and, if no one matches the identifier you give, creates that person. It is the workhorse of most Agillic Zaps.

When to use it
a CRM or form captures a contact and Agillic should hold the same profile without a manual import.
Watch out
a typo in the identifier value creates a duplicate recipient instead of updating the right one.
Searches

Agillic searches

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

A search step looks something up before acting. In the action list, Agillic's two searches sit at the bottom under the SEARCH heading. Some action fields also offer + Add search step, which inserts one just before and wires the result in.

1

Find and Get Recipient

Search

In Zapier“Query Agillic to see if the recipient exists, and return the available Person Data for that recipient if they do.”

Checks whether a recipient exists in Agillic and, if so, returns their Person Data for the next steps. The only required input is the identifier value.

When to use it
before an Achieve Event, to make sure the person is really there and to reuse their profile data.
Watch out
whether the match must be exact is decided by Agillic, not by Zapier.
2

Get OTM Table

Search

In Zapier“Get the rows in a One to many table for a specific recipient.”

Returns the rows of one One-to-Many table for a given recipient. You set the identifier, its value and the table.

When to use it
a support tool needs a customer's past bookings before a reply goes out.
Watch out
an empty table stops the Zap on default settings; switch on the first setting above if that is normal for some people.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on default, a search that finds no one stops the Zap and the dependent steps are skipped. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Agillic exposes no such variant on Zapier; creating is the job of Update or Create Recipient.
  3. If multiple search results are found?
    Three ways out: keep the first match (the default), stop the Zap, or pass all of them on at once.
When it breaks

When an Agillic Zap breaks

No Zapier help article covers Agillic specifically. What follows are Zapier's general limits, seen through recipients and One-to-Many tables.

Four cases account for most broken Agillic Zaps. Read them before publishing, and if a run still fails, open the Zapier troubleshooting page.

  • Existing contacts are never synced

    A Zap reacts only to what happens after it is switched on. Contacts already in your other tools need a separate one-off import into Agillic.

  • A self-feeding loop

    A Zap that writes into the very place its trigger watches sets itself off again and again, and the task count drains fast.

  • Big imports held back

    When a trigger suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold the runs back.

  • A filter that never passes

    Each filter rule has a type. Comparing a number with a text rule, or the reverse, means the condition is never met and no run gets through.
Need help

Need help automating Agillic with Zapier?

A person reads every message.

FAQ

Agillic Zapier integration: FAQ

01Is the Agillic Zapier integration free?
Yes, Agillic is not a premium app, so it works on the free Zapier plan. That plan includes 100 tasks a month and unlimited Zaps, but each Zap is capped at two steps: one trigger and one action. A form answer feeding Update or Create Recipient fits. Add a search step, a filter or a second action and the Zap becomes multi-step, which requires a paid plan. No price appears here because plan grids change too often to publish.
02How many tasks does an Agillic Zap use?
One per successful action, nothing for the trigger or for searching. A Zap that adds a One-to-Many row for each order uses one task per order. If it also achieved an event, each run would cost two tasks. Failed actions are not counted, and Zapier checking for new data is free however often it happens. A few apps and actions take more than one task, so watch the task history after the first runs.
03Does the Agillic trigger work in real time?
No. Get OTM Tables is a polling trigger: Zapier asks Agillic for its One-to-Many tables at a fixed interval, every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. That type is set by the app and cannot be changed in the editor. On paid plans, the check can also be run by hand. Keep in mind this trigger reads tables, not recipients, so most Agillic Zaps start in another app anyway.
04What does it take to connect Agillic to Zapier?
An Agillic account with read or write access to the recipients and tables your Zap will change, if someone else owns them. The connection is made once, from the Apps page of Zapier: + Add connection, search for Agillic, Add connection, then sign in to Agillic in the new tab and grant access. Every Agillic step of every Zap then reuses it, so there is nothing to reconnect when you build a second Zap.
05Why does Agillic ask for a Unique Recipient Identifier Field?
Because Agillic finds people through a unique field, not through a name. Achieve Event, Delete a Recipient, both update actions and the One-to-Many actions all require you to pick that field, then map its value from an earlier step. The field has to be one of the Unique Person Data fields of your instance. If the value sent does not match anyone, the update actions create a new recipient instead, which is how duplicates appear.
06What if the Agillic operation you need is not on Zapier?
Then Zapier alone cannot run it. The integration covers recipients, One-to-Many tables, events and two searches, with a single trigger that reads tables. There is no trigger for a changed recipient or a new row, for instance. In that case, check what other automation tools offer for Agillic before building a workaround, or reshape the process so another app starts the Zap and Agillic receives the result, through Update or Create Recipient or Achieve Event.
07Zapier, Make or n8n for Agillic?
It depends on your criteria rather than on a winner. On Zapier, Agillic is mostly a destination: six actions and two searches, but a single polling trigger that reads tables, not recipients. If your process must start when a recipient changes in Agillic, check whether Make or n8n expose such a starting point before choosing. Then weigh the operations you need, how many tasks your Zaps will burn, and whether they fit in two steps or need a paid plan.
Same platform

Other docs you might need on this stack.

Browse all integrations