Resources · Zapier integration

Agile CRM Zapier integrationAutomate Agile CRM with Zapier.

The Agile CRM Zapier integration gives you 9 triggers, 11 actions and 0 searches: contacts, deals, tickets, tasks and campaigns, wired to the rest of your tools. Here is what each one does, what it costs and where it breaks.

See the 20 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Agile CRM Zapier integration is for

Agile CRM is a sales and marketing CRM: contacts, deals, a help desk, campaigns. Zapier links it to your other apps without code. Something happens in Agile CRM and another tool reacts, or something happens elsewhere and Agile CRM gets updated, with 20 visible operations to pick from.

Three results come up again and again. A contact base that fills itself: a form or a sign-up elsewhere ends in Create or Update Contact, matched on the email, with no duplicate typing. A pipeline that drives the team: a deal reaches a stage and Create Task or a message to the team follows. A support desk that stays in sync: New Ticket feeds the tool where your team actually talks.

The single most useful tip on this page: out of 9 triggers, Changing Any Deal Milestone is the only instant one. It reacts at once, even on the free plan, while the other 8 wait for your plan's check. Neither zapier.com nor the help center says so. If speed on deals matters, build on that one first.

What Zapier does not do for Agile CRM matters too. There is no search step, so a Zap cannot look a contact or a deal up before acting; matching happens through the email inside the actions. There is no delete action either. And a Zap never processes records created before it was switched on.

For the same tool on other platforms, see the Agile CRM n8n integration and the Agile CRM Make integration.

Vocabulary

Zapier vocabulary in one minute

The words you will meet in the editor, explained once and then used as is.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, like a new deal in Agile CRM. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that creates a contact, adds a tag or opens a ticket for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan is a monthly count of those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a set interval and keeps only what it has not seen.
Instant trigger
A trigger the app reports itself, the moment the event happens, so nothing waits for the next check. It shows a lightning bolt.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What an Agile CRM Zap really costs

Three rules decide your bill, and the third one surprises most people.

  • Free plan100 tasks a month, unlimited Zaps
  • Steps on freeTwo: one trigger, one action
  • Premium appNo, Agile CRM works on the free plan
  • Instant triggers1 out of 9

The trigger never costs a task, and neither does Zapier checking Agile CRM, however often it looks. Each action that succeeds counts as one task; one that fails is not counted. In a Zap with several actions, each success counts on its own: a contact created then tagged costs two tasks. The free plan stops at one trigger and one action, so a filter or a second action means a paid plan. Agile CRM is not a premium app and works from the free plan.

Connect

Connect your Agile CRM account to Zapier

  1. 01

    Open Apps and add a connection

    In Zapier, go to Apps, click + Add connection, type Agile CRM in the dialog and pick it. You need an Agile CRM account, with access to the contacts, deals and tickets the Zap will touch.

  2. 02

    Sign in to Agile CRM

    Click Add connection. A tab opens on the Agile CRM side. Sign in with the Agile CRM account whose data the Zap should use. Anything that account does not own, such as a colleague's deals or tickets, needs read or write access before the Zap can touch it.

  3. 03

    Grant access and reuse it

    Grant Zapier access to the account. That is the connection: your Agile CRM account linked once, then reused by every Agile CRM step of every Zap instead of asking you again.

First Zap

Your first Agile CRM Zap, step by step

GoalWhen a deal changes milestone, create a follow-up task, but only for deals marked as won.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose Agile CRM, then Changing Any Deal Milestone. It is the one instant trigger of the app, so the Zap reacts as soon as a deal moves.

  2. 02

    Test the trigger

    Pick your connection and run the test. Zapier brings back the three most recent items of the account, so you map the next steps on a real deal rather than a guess.

  3. 03

    Add a filter on the milestone

    Add a filter that lets only won deals through. A text rule must compare text: pick the wrong rule type and the filter never passes. The filter needs a paid plan.

  4. 04

    Add Create Task

    Add the action Agile CRM, Create Task. Fill in the subject, the task type and the priority, all three required, and map the deal name into the subject.

  5. 05

    Test, then publish

    Test the action once and check the task in Agile CRM. Then publish the Zap to switch it on. Only deals that move after this moment will be picked up.

Triggers

The 9 Agile CRM triggers

9 events start a Zap when something happens in Agile CRM, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Changed Deal Milestone

Polling trigger

In Zapier“Triggers when a Deal reaches a specific milestone you choose.”

Starts the Zap when a deal lands on one milestone you pick in advance, on one track of your pipeline. Useful when only one stage deserves a reaction, like proposal sent.

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 single stage, such as a signed deal, should open an onboarding task or a message to finance.
Watch out
the track and the milestone are required, so the pipeline must already exist in Agile CRM before you set the trigger.
2

Changing Any Deal Milestone

Instant trigger

In Zapier“Changing any milestone in Agile CRM should be triggered.”

Fires whenever a deal moves to another milestone, whichever one it is. The Zap receives the deal, and a filter placed after it can then keep only the stages you care about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team needs to hear about pipeline movement at once, for example to alert a manager when a large deal advances.
Watch out
every stage change starts a run, so a busy pipeline burns tasks fast if the actions are not filtered.
3

New Case

Polling trigger

In Zapier“Triggers when a new case is added in Agile CRM.”

Picks up each new case recorded in Agile CRM, so whatever follows the case can begin without someone copying it by hand into another tool.

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 case opened by an account manager should also appear in the board or channel where the delivery team works.
Watch out
only cases created after the Zap goes live are seen; the ones already open stay where they are.
4

New Contact

Polling trigger

In Zapier“Triggers when a new contact is add in AgileCRM.”

Hands each freshly added contact to the rest of your stack: each new record becomes values you can map into another app.

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 new contact must also land in your mailing tool or in a shared sheet the sales team works from.
Watch out
if a Zap of yours also creates contacts in Agile CRM, chaining both can loop and eat your task count.
5

New Deal

Polling trigger

In Zapier“Triggers when a new Deal is added in AgileCRM.”

Reacts when someone opens a new deal, before it has moved anywhere in the pipeline. Whatever the deal carries can then be mapped into the steps that follow.

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
every new opportunity should be logged in a reporting sheet or announced to the team without anyone retyping it.
Watch out
this trigger sees creation only; a deal that later changes stage needs one of the milestone triggers instead.
6

New Event

Polling trigger

In Zapier“Triggers when a new event is created in Agile CRM.”

Each event someone creates in Agile CRM starts the Zap, so a booking made in the CRM does not stay locked inside it.

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
meetings booked in the CRM should be mirrored in the calendar or the chat tool the rest of the company uses.
Watch out
if another Zap writes events into Agile CRM with Add Event, chaining it with this trigger can set it off again and again.
7

New Ticket

Polling trigger

In Zapier“Triggers when a new ticket is added in Agile CRM.”

Brings each new help desk ticket out of Agile CRM, so support requests reach the people who handle them wherever they work.

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
urgent tickets should ping a support channel instead of waiting for someone to open the help desk.
Watch out
Ticket Filter is a required field, so the trigger cannot be saved until you pick one.
8

New Task

Polling trigger

In Zapier“Triggers when a new task is added in the Agile CRM.”

Detects each task added in Agile CRM and passes it on, which keeps to-do lists aligned when part of the team lives in another tool.

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
tasks assigned in the CRM should show up in the project tool where people actually tick things off.
Watch out
pairing this trigger with Create Task in the same account makes a Zap that keeps starting itself.
9

New Tag to Contact

Polling trigger

In Zapier“Triggers when a tag is added to contact in AgileCRM.”

Waits for one specific tag to be put on a contact, then runs the Zap for that contact. The tag becomes a switch that anyone in the team can flip.

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
tagging a contact as a hot lead should push it into a sequence or alert the right salesperson.
Watch out
Tag Name is required: the trigger watches one tag, the one you name in the step.
Actions

The 11 Agile CRM actions

Agile CRM gives you 11 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add to Campaign

Action

In Zapier“Subscribe to a Campaign.”

Subscribes a contact, by email, to one of your Agile CRM campaign workflows, which then takes over the follow-up.

When to use it
a download or a trial sign-up elsewhere should start a nurturing sequence without manual import.
Watch out
the campaign workflow must already exist in Agile CRM; no action on Zapier creates one.
2

Add Note

Action

In Zapier“Add a Note to the Contact.”

Attaches a note to a contact found by email, with a subject and a description, all three fields required.

When to use it
a call summary, a survey answer or a support exchange should stay visible on the contact's history for the next person who opens it.
Watch out
the note is matched to a contact through Contact Email, so map the address of the person the note is about.
3

Add Score to Contact

Action

In Zapier“Add Score to a Contact in the AgileCRM.”

Raises the lead score of a contact, identified by email, by the amount you set in the step.

When to use it
buying signals outside the CRM, such as a pricing page form or a reply to an email, should count toward how warm a lead is.
Watch out
the score is added, not replaced, so a Zap that runs twice for one event counts it twice.
4

Add Tag to Contact

Action

In Zapier“Add Tag to a Contact in the Agile CRM.”

Puts one or several tags on an existing contact, found by its email. Tags are separated by commas.

When to use it
an action elsewhere, like attending a webinar, should mark the contact for later segmentation.
Watch out
tags cannot carry special characters other than spaces and underscores, so clean the value before it reaches this step.
5

Create Company

Action

In Zapier“Create a New Company.”

Opens a company record in Agile CRM with the name your Zap provides, so contacts and deals have an account to hang on.

When to use it
a new client signs in your billing or onboarding tool and needs its company sheet in the CRM.
Watch out
only the company name is required, so a trigger that carries nothing else is enough to run it.
6

Create Contact

Action

In Zapier“Creates New Contact in the Agile CRM.”

Adds a brand new person to Agile CRM from whatever your trigger brought in, a form entry or a sign-up for example.

When to use it
leads come from a source that never had a CRM record before.
Watch out
first name and email are both required, and for a person who may already be in the CRM, Create or Update Contact is the one matched on the email.
7

Create Deal

Action

In Zapier“Create a deal in the Agile CRM.”

Puts a new opportunity into your pipeline, with a name and an expected value, both required.

When to use it
a quote request or a demo booking should become a deal the sales team can follow from the first minute.
Watch out
the value field expects an amount; if your source has none, decide on a placeholder value before publishing.
8

Add Event

Action

In Zapier“Create event an event in Agile CRM.”

Writes an event into the Agile CRM calendar. It is the most demanding action of the app: name, priority, owner, start time and end time are all required.

When to use it
meetings booked through an outside scheduler should appear in the CRM too.
Watch out
a missing end time from the source blocks the step, so map both times.
9

Create Ticket

Action

In Zapier“Creates Ticket in the Agile CRM.”

Opens a help desk ticket in Agile CRM from an outside request, with an email, a subject, a priority, an assignee group and a message, all required.

When to use it
requests arriving by form or chat should join the same queue as the rest of support.
Watch out
the assignee is a group name, which must exist in your help desk.
10

Create Task

Action

In Zapier“Create a Task for the Contact.”

Creates a to-do for a contact in Agile CRM, with a subject, a task type and a priority, all three required.

When to use it
a signal elsewhere, like a deal stage or a missed call, should land as a clear next step in someone's list.
Watch out
if your trigger carries no subject, type and priority, set fixed values in the step, since none of the three can stay empty.
11

Create or Update Contact

Action

In Zapier“Updates the contact in Agile CRM based on the Email Address. Alternatively, can also create a contact if one is not found.”

Looks the contact up by email address, updates it when it exists and creates it when it does not. The safest way to feed contacts from several sources.

When to use it
the same person may come back through a second form or a new purchase.
Watch out
the email is the only key, so a typo creates a second contact.
When it breaks

When an Agile CRM Zap breaks

Zapier attaches no help article to Agile CRM and lists no limit specific to it. What breaks are the general rules of Zapier, and they bite hard on a CRM.

A CRM is where Zaps loop most easily, because the same records are read and written by several automations. Before blaming Agile CRM, check the four cases below. For the general method, the Zapier troubleshooting page walks through the usual checks.

  • Existing contacts are never processed

    A Zap only reacts to what happens after you switch it on. Contacts and deals already in Agile CRM stay untouched; moving that backlog is a separate job.

  • A Zap that keeps restarting itself

    New Contact feeding Create Contact in the same account, or New Task feeding Create Task, sets the Zap off again and again and drains your task count.

  • A bulk import gets held back

    After a bulk import or a migration, a trigger may suddenly return a huge batch. Zapier's flood protection can then hold the runs back instead of firing them all.

  • The same record never runs twice

    On a polling trigger, Zapier remembers what it has already seen. Editing a contact does not make New Contact fire again for it.
Need help

Need help automating Agile CRM with Zapier?

A person reads every message.

FAQ

Agile CRM Zapier integration: common questions

01Is the Agile CRM Zapier integration free?
Yes, on Zapier's side. Agile CRM is not a premium app, so it works from the free plan, which gives 100 tasks a month and unlimited Zaps. The limit is the shape of the Zap: on free, one trigger and one action, nothing more. New Deal followed by Create Task fits. Add a filter on the milestone or a second action and the Zap becomes multi-step, which needs a paid plan. What Agile CRM charges for its own plans is a separate question this page does not cover.
02How many Zapier tasks does an Agile CRM Zap use?
One task per action that succeeds, and nothing for the trigger. Zapier checking Agile CRM for new deals or contacts costs nothing either, however often it looks. A failed action is not counted. The catch is multi-action Zaps: creating a contact, tagging it and adding it to a campaign is three actions, so three tasks per new lead. On a busy pipeline, Changing Any Deal Milestone fires on every stage change, which is why a filter in front of the actions saves tasks.
03Is the Agile CRM Zapier integration real time?
For one trigger only. Changing Any Deal Milestone is instant: Agile CRM tells Zapier as soon as a deal moves, so the Zap starts right away, whatever your plan. The 8 other triggers are polling ones: Zapier checks every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Zapier decides the type from the app itself, so it cannot be changed in the editor. If speed on deals matters, build on the instant trigger and filter the stages you need.
04What do you need to connect Agile CRM to Zapier?
An Agile CRM account, plus access to the contacts, deals, tickets and campaigns your Zaps will read or write. The connection starts from the Apps page of Zapier with + Add connection, a search for Agile CRM, then Add connection. You sign in on the Agile CRM side and grant access. Several actions also expect objects that already exist in the CRM: a campaign workflow for Add to Campaign, a help desk group for Create Ticket, a pipeline for Changed Deal Milestone.
05Why does Add Tag to Contact reject some tags?
Because Agile CRM refuses special characters in a tag, except spaces and underscores. A hyphen or a slash coming from a form counts as one. The fix is to clean the value before it reaches the action, or to map a fixed tag instead of a free text field. Several tags go in one field, separated by commas. The contact itself is found by its email, so the email must match a contact that already exists.
06What if the Agile CRM operation you need is missing from Zapier?
Then the Zap has to work around it, because the list is fixed: 9 triggers and 11 actions, with no search and no delete. The usual workaround for lookups is Create or Update Contact, which finds a contact by email on its own. For a deal or a case you want to update, Zapier offers nothing here. In that case, check whether the other automation platforms expose that operation for Agile CRM, or keep that part of the work inside Agile CRM's own automations.
07Zapier, Make or n8n for Agile CRM?
Choose by criteria, not by brand. Zapier fits when your other apps are already connected to it, when one instant trigger on deals matters, and when two-step Zaps are enough, since the free plan covers those. On Zapier, Agile CRM has 9 triggers, 11 actions and no search step, so a Zap cannot look a deal up before acting, and billing counts every successful action. Compare that with the operations Make and n8n expose for Agile CRM and with the tool your team already runs.
Same platform

Other docs you might need on this stack.

Browse all integrations