Resources · Make integration

Agile CRM Make integrationAutomate Agile CRM with Make.

Your CRM can do the follow-up work while your team sells. The Agile CRM Make integration gives you 40 modules, 7 of them triggers, to move contacts, deals, tasks and tickets without code. This guide connects your account and walks you through a first working scenario.

Try the Agile CRM integration on MakeSee the 40 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Agile CRM Make integration do for you?

The Agile CRM Make integration links your CRM account to Make, a visual tool where you build a scenario: an automation made of modules. A module is one brick of that chain, a trigger that watches Agile CRM, an action that writes to it, or a search that reads from it. You click them together, no code involved.

No deal left without a next step. Watch Deals spots a deal that was created or updated, and Create a Task hands the owner a follow-up in Agile CRM. Your pipeline stops relying on memory.

Support tickets with the full story. Watch Tickets picks up a new or updated ticket, Get All Messages in a Ticket pulls the whole conversation, and Add a Note can pin a summary to the matching contact or deal.

Campaigns that follow your tags. Watch Contact's Tags notices a new tag on a contact you choose, and Add a Contact to a Campaign enrolls that person by email in the right sequence.

Know the limits before you start. All 7 Agile CRM triggers are scheduled: Make checks the account on the scenario's clock, it is never pinged the moment something happens. The official Make documentation for this app is also flagged as AI-generated, so double-check anything important against Agile CRM itself. If a step breaks, the Make troubleshooting guide covers the usual suspects.

Agile CRM also has a node in n8n. If you are weighing both tools, read our n8n vs Make comparison or open the Agile CRM n8n integration page.

Connect

How do you connect Agile CRM to Make?

  1. 01

    Copy your API key in Agile CRM

    In Agile CRM, open Admin Settings, then pick API & Analytics in the menu. Copy the API key for REST client shown on screen. You need an active Agile CRM account for this key to exist.

  2. 02

    Add an Agile CRM module in Make

    In your scenario, add any Agile CRM module and click Create a connection. A connection is your Agile CRM account linked to Make once, then reused by every Agile CRM module you add later.

  3. 03

    Name it and paste your credentials

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the credentials copied from Agile CRM, follow the prompts on screen, and save.

First scenario

Your first scenario: a task for every deal that moves

GoalWhen a deal is created or updated in Agile CRM, Make adds a follow-up task for it.

  1. 01

    Create a new scenario

    Go to the Scenarios page in Make, create a new scenario and click the big + in the middle of the canvas to add your first module.

  2. 02

    Pick Watch Deals

    Search for Agile CRM, choose Watch Deals and select the connection you just created, or click Create a connection if you skipped that part.

  3. 03

    Add Create a Task

    Click the + on the right of Watch Deals and add Create a Task. Map details of the deal from the previous module into the task so your rep knows which deal to chase.

  4. 04

    Test with Run once

    Update a test deal in Agile CRM, then click Run once. Make runs the scenario one time and shows the bundles each module received. A bundle is one item passing through, here one deal.

  5. 05

    Schedule it and switch it on

    Open the clock on Watch Deals. A new scenario checks every 15 minutes by default. Keep that or adjust it, then switch the scenario on so it keeps working without you.

Triggers

The 7 triggers that start your scenario

7 modules start a scenario when something happens in Agile CRM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Agile CRM as soon as it happens.

Agile CRM1Watch Companies

Watch Companies

Scheduled trigger

In Make“Triggers when a company is created, updated or viewed.”

This trigger starts your scenario whenever a company record in Agile CRM is created, updated, or simply viewed. Each matching company arrives in Make as a bundle you can pass to the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, so changes show up at the next check, not the second they happen.
When to use it
you keep a shared account list in a spreadsheet or another tool and want it refreshed when a company changes in the CRM.
Watch out
a colleague opening a company can count as activity too, so expect runs, and operations, that carry no real change.
Agile CRM2Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a contact is created, updated or viewed.”

Watch Contacts sends Make every contact that was created, edited, or viewed in Agile CRM since the last check. It is the widest entry point of the app, since almost everything in a CRM starts with a person.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
a new lead lands in the CRM and you want your newsletter tool, billing app or team chat to hear about it.
Watch out
because views count, a single burst of CRM activity can push many contacts through. Each one uses operations, the unit Make counts on your plan.
Agile CRM3Watch Contact's Tags

Watch Contact's Tags

Scheduled trigger

In Make“Triggers when a new tag is added to the selected contact.”

Unlike the other watchers, this one follows a single contact you pick in the module and fires when a new tag gets added to that person. Every fresh tag becomes a bundle Make can act on.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
a key account or a partner contact whose tags mark progress, such as a signed contract or a renewal in play, and you want the team alerted.
Watch out
it does not scan your whole database. If you need tag changes across all contacts, Watch Contacts is the better starting point.
Agile CRM4Watch Deals

Watch Deals

Scheduled trigger

In Make“Triggers when a deal is created or updated.”

Your pipeline, piped into Make. Watch Deals picks up each deal that was created or updated in Agile CRM and hands it to the rest of the scenario as one bundle per deal.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
a deal moves forward and someone should get a task, a message or an updated forecast sheet.
Watch out
any update counts, not only a stage change, so a small edit to a deal can also start a run. Check the bundle on your first Run once test.
Agile CRM5Watch Events

Watch Events

Scheduled trigger

In Make“Triggers when a calendar event occurs.”

Calendar events from Agile CRM can drive automations too. This trigger reacts when an event on the CRM calendar occurs and passes that event to the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, so an event is picked up at the check that follows it.
When to use it
a demo or a client meeting is on the calendar and you want a prep checklist or a reminder sent to the people involved.
Watch out
with the schedule between checks, this is not the right tool for a last-second reminder. Set the scenario clock with that gap in mind.
Agile CRM6Watch Tasks

Watch Tasks

Scheduled trigger

In Make“Triggers when a task is created, due, started or completed.”

Watch Tasks covers the whole life of a task: it fires when one is created, becomes due, gets started or is completed in Agile CRM. That makes it useful for both reminders and reporting.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
a manager wants a message when a task is completed, or a rep needs a nudge in chat when a task falls due.
Watch out
one task can come through several times as it moves from created to completed. Decide which moment matters before you add the next module.
Agile CRM7Watch Tickets

Watch Tickets

Scheduled trigger

In Make“Triggers when a ticket is created or updated.”

For teams handling support inside Agile CRM, Watch Tickets hands Make every ticket that was opened or updated since the previous check.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the instant a customer writes.
When to use it
a new ticket should ping the support channel, or an updated one should refresh a shared tracking board.
Watch out
the ticket arrives without its full thread. Add Get All Messages in a Ticket right after when you need the conversation itself, and remember each extra module costs operations.
Modules

Everything Agile CRM can do in Make

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

Agile CRM1

Add a Contact to a Campaign

Action

In Make“Adds a contact by email to a selected campaign.”

Enrolls a person in one of your Agile CRM campaigns using their email address, so your nurture sequence starts without anyone clicking through the CRM.

When to use it
a webinar sign-up or a form submission elsewhere should drop that lead straight into the matching follow-up campaign.
Watch out
the module works by email, so a typo or an address missing from Agile CRM leaves the contact out of the campaign.
Agile CRM2

Add an Event

Action

In Make“Adds a new event on the calendar.”

Puts a new event on the Agile CRM calendar, which keeps meetings booked in other tools visible to the whole sales team in one place.

When to use it
a prospect books a call through a scheduling page or a form, and you want that slot in the CRM next to the deal it belongs to.
Watch out
run a test with Run once first, then open the calendar in Agile CRM to confirm the date and time landed where you expect.
Agile CRM3

Add a Note

Action

In Make“Adds a new note to a ticket, contact or deal.”

Writes a note on a ticket, a contact or a deal. It is the simplest way to leave a written trace of what an automation did or learned.

When to use it
a call summary, a survey answer or a message from another app should sit on the record your team already opens every day.
Watch out
the module adds a new note each time it runs, so a scenario that fires twice on the same record will leave two notes behind.
Agile CRM4

Create a Company

Action

In Make“Creates a new company.”

Adds a company record to Agile CRM from data coming out of another module, such as a signup form, an invoicing tool or an enrichment step.

When to use it
a new customer account appears in your billing app and your sales team should see it as a company in the CRM right away.
Watch out
nothing here checks for an existing company. Run List Companies first when you want to avoid creating the same organization twice.
Agile CRM5

Create a Contact

Action

In Make“Creates a new contact.”

This is the module that turns an outside lead into a person in your CRM. Whatever you map from the previous step becomes the contact's details in Agile CRM.

When to use it
leads come in from a landing page, an event list or a chat tool, and you want them in Agile CRM without copy and paste.
Watch out
if the person may already exist, look them up before creating, or switch to Update a Contact for returning leads.
Agile CRM6

Create a Deal

Action

In Make“Creates a new deal.”

Opens a new deal in your Agile CRM pipeline, so an opportunity spotted by another tool shows up where your reps track revenue.

When to use it
a quote request, a trial signup or a qualified form answer should become a deal your reps can see and work on.
Watch out
a deal on its own is easy to forget. Pair it with Create a Task so someone actually owns the next step.
Agile CRM7

Create a Task

Action

In Make“Creates a new task.”

Hands someone a to-do inside Agile CRM. The task sits in the rep's list with whatever context you mapped from earlier modules.

When to use it
after a deal moves, a ticket escalates or a contact gets a key tag, and a human needs to do something about it.
Watch out
if the trigger before it fires on every small update, you can bury your team in duplicate tasks. Test the flow with Run once before you switch it on.
Agile CRM8

Create a Ticket

Action

In Make“Creates a new ticket.”

Opens a support ticket in Agile CRM from a message that started somewhere else, like a web form, an email parser or a chat widget.

When to use it
customer requests land in several places and your support team wants a single queue inside the CRM.
Watch out
if the same request can arrive twice, for example from two forms, you will get two tickets. Clean the source before you plug it in.
Agile CRM9

Delete a Company

Action

In Make“Deletes a company.”

Removes a company record from Agile CRM for good, based on the ID it receives from a previous module.

When to use it
a cleanup flow where companies flagged as duplicates or test records elsewhere should disappear from the CRM as well.
Watch out
there is no undo from Make. Test on a dummy record with Run once and double-check which ID you mapped before switching the scenario on.
Agile CRM10

Delete a Contact

Action

In Make“Deletes a contact.”

Erases a person from Agile CRM. Use it when a contact must leave the database entirely, not just stop receiving emails.

When to use it
someone asks for their data to be removed, and your team logs that request in a form or a ticket that the scenario can read.
Watch out
the deletion is final. If you only want to pause outreach, updating the contact is the safer move.
Agile CRM11

Delete a Deal

Action

In Make“Deletes a deal.”

Takes a deal out of your Agile CRM pipeline completely, identified by the deal ID mapped from an earlier module.

When to use it
deals created by mistake, such as test entries or duplicates from an import, need to leave the pipeline without manual cleanup.
Watch out
a deleted deal also leaves your pipeline history. For lost deals you want to keep for reporting, Update a Deal is usually what you need.
Agile CRM12

Delete an Event

Action

In Make“Deletes an event.”

Removes an event from the Agile CRM calendar, which keeps the CRM honest when a meeting is cancelled in another tool.

When to use it
a prospect cancels through your booking page and the slot should disappear from the shared calendar too.
Watch out
you need the right event ID. List Events or Get an Event can help you find it before the deletion runs.
Agile CRM13

Delete a Task

Action

In Make“Deletes a task.”

Clears a task out of Agile CRM entirely. Handy when an automation created it and the reason behind it no longer applies.

When to use it
a deal was closed or a ticket resolved elsewhere, and the related to-do would only clutter a rep's list.
Watch out
deleting is not the same as completing. If your reports count finished tasks, update the task instead of removing it.
Agile CRM14

Delete a Ticket

Action

In Make“Deletes a ticket”

Removes a support ticket from Agile CRM, with the ticket ID coming from a trigger or a search earlier in the scenario.

When to use it
spam or test tickets keep landing in the queue and a rule elsewhere already identifies them.
Watch out
the conversation goes with the ticket. If there is any chance you need it later, save it with Get All Messages in a Ticket first.
Agile CRM15

Get a Company

Action

In Make“Gets the details of a company.”

Fetches the full record of one company when you already know its ID, so later modules can use details the trigger did not bring along.

When to use it
a deal or a contact points to a company, and you need that company's information for an invoice, a report or a message.
Watch out
without an ID this module has nothing to look up. If all you have is a name, start with List Companies.
Agile CRM16

Get a Contact by ID

Action

In Make“Gets the details of a contact by ID.”

Reads one contact from Agile CRM using its ID and returns everything the CRM stores about that person to your scenario.

When to use it
a ticket, task or deal arrived with a contact ID attached, and the next step needs the person's name or email.
Watch out
as the name says, it works by ID only. An email address alone will not do, so map the ID from the previous bundle.
Agile CRM17

Get a Deal

Action

In Make“Gets the details of a deal.”

Pulls the current state of a single deal, handy when the data from the trigger is not enough or may be out of date by the time the scenario reaches this step.

When to use it
before you send a proposal or update a forecast, you want the deal exactly as it stands in Agile CRM right now.
Watch out
you need the deal ID. Pass it from Watch Deals, List Deals or a note that references it.
Agile CRM18

Get an Event

Action

In Make“Gets the details of an event.”

Returns the details of one calendar event from Agile CRM, based on the event ID you map into it.

When to use it
a follow-up email or a prep document should include the meeting's exact information, pulled from the CRM rather than typed by hand.
Watch out
it reads a single event. When you need everything planned for a period, List Events is the module to pick.
Agile CRM19

Get a Task

Action

In Make“Gets the details of a task.”

Looks up one task in Agile CRM and gives the scenario its current details as the CRM stores them.

When to use it
before chasing someone, you want to confirm the task is still open, so you do not send a reminder for work already done.
Watch out
the module needs the task ID. Watch Tasks and List Tasks both provide it in their bundles.
Agile CRM20

Get a Ticket

Action

In Make“Gets the details of a ticket.”

Retrieves a single support ticket so the scenario knows its current state before doing anything else with it.

When to use it
a customer replies through another channel and you want to check the linked ticket before posting an update to your team.
Watch out
this returns the ticket, not its full thread of messages. Add Get All Messages in a Ticket when the conversation matters.
Agile CRM21

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your escape hatch. This module lets you call any endpoint of the Agile CRM API with the same connection you already set up, even when no dedicated module exists for the job.

When to use it
you need an Agile CRM feature that none of the dedicated modules covers.
Watch out
you write the request yourself, so keep the Agile CRM API reference open and test with Run once before relying on it.
Agile CRM22

Update a Company

Action

In Make“Updates an existing company.”

Changes an existing company record in Agile CRM with fresh data, so the account view stays accurate without manual edits.

When to use it
your billing or enrichment tool learns something new about a customer, and the CRM should reflect it on the company record.
Watch out
you must point it at the right company ID. Map it from a trigger or a search, never guess it.
Agile CRM23

Update a Contact

Action

In Make“Updates an existing contact.”

Edits a person who already exists in Agile CRM, which is how you keep contact data in step with the other tools your team uses.

When to use it
someone changes their phone number in your support tool or upgrades their plan in your app, and the CRM should know.
Watch out
an empty value mapped by mistake may overwrite good data. Check the bundle in a Run once test before going live.
Agile CRM24

Update a Deal

Action

In Make“Updates an existing deal.”

Moves or edits an existing deal, keeping your Agile CRM pipeline aligned with what happens outside the CRM.

When to use it
a contract gets signed in your e-signature tool or an invoice is paid, and the deal in the CRM should say the same thing.
Watch out
if Watch Deals starts the same scenario, updating the deal can trigger it again. Keep the two apart or check the bundle to avoid loops.
Agile CRM25

Update an Event

Action

In Make“Updates an existing event.”

Adjusts an event already on the Agile CRM calendar, for instance when its time or details change in another tool.

When to use it
a client reschedules through your booking page and the CRM calendar should show the new slot, not the old one.
Watch out
you need the event ID from the original booking. Store it somewhere, a note or a sheet, when the event is first created.
Agile CRM26

Update a Task

Action

In Make“Updates an existing task.”

Modifies a task in Agile CRM, from its details to its status, without anyone opening the CRM.

When to use it
the work behind a task gets done in another tool, such as a ticket closed or a document signed, and the task should reflect it.
Watch out
Watch Tasks also fires on completed tasks, so combining both in one scenario can loop. Test the flow with Run once first.
Agile CRM27

Get All Messages in a Ticket

Search

In Make“Retrieves all messages within a specified ticket.”

Brings back the full conversation of one support ticket, message by message, so your scenario can read what the customer and your team actually wrote.

When to use it
you want to archive a thread, send it to a teammate, or have an AI tool summarize it before adding a note.
Watch out
this is a search, so each message comes out as its own bundle. Modules placed after it run once per message and consume operations each time.
Agile CRM28

List Companies

Search

In Make“Retrieves a list of all companies.”

Returns your companies from Agile CRM as a batch, one bundle each, which makes it the starting point for exports and bulk checks.

When to use it
you want to rebuild an account list in a spreadsheet, or check whether a company exists before creating it.
Watch out
every company becomes a bundle, and every module after it runs once per company. On a large database, watch your operations.
Agile CRM29

List Contacts

Search

In Make“Retrieves a list of all contacts.”

Pulls contacts out of Agile CRM in one go, each person flowing to the next module as a separate bundle.

When to use it
a one-off sync to another tool, an audit of your database, or a search for a contact before you decide to create or update.
Watch out
this can return a lot of people. Put it in a scenario you run on demand rather than on a tight schedule, or your operations will add up fast.
Agile CRM30

List Deals

Search

In Make“Retrieves a list of all deals.”

Gets the deals in your Agile CRM pipeline as a list, perfect for building a forecast or a pipeline report outside the CRM.

When to use it
sales leadership wants deal data in a spreadsheet or dashboard they already read, refreshed by a scenario rather than by hand.
Watch out
each deal is a bundle. If you only need one deal and you have its ID, Get a Deal costs far fewer operations.
Agile CRM31

List Events

Search

In Make“Retrieves a list of all events.”

Collects the events on your Agile CRM calendar and passes them on one by one.

When to use it
you want a digest of upcoming meetings sent to the team, or calendar data copied into a planning sheet.
Watch out
the module returns several bundles, so a message module placed right after it sends one message per event. Add an aggregator, a Make tool that groups bundles, when you want a single digest.
Agile CRM32

List Tasks

Search

In Make“Retrieves a list of the tasks by given filter parameters.”

Unlike the other list modules, this one accepts filter parameters, so you can ask Agile CRM for just the tasks that matter instead of every task on record.

When to use it
a manager wants a short list of the tasks that matter to them, sent to chat or written into a sheet.
Watch out
set the filters before the first test. An empty filter can pull far more tasks than you planned, and each one costs operations downstream.
Agile CRM33

List Tickets

Search

In Make“Retrieves a list of all tickets.”

Returns the support tickets stored in Agile CRM, each one as a bundle ready for reporting or follow-up.

When to use it
support leads want a count or a table of tickets in a tool the whole company already reads.
Watch out
the list gives ticket records, not their conversations. Chain Get All Messages in a Ticket only for the tickets that need it, since each call adds operations.
Need help

Need help automating Agile CRM with Make?

A person reads every message.

FAQ

Agile CRM and Make: your questions

01Is the Agile CRM Make integration free?
Yes, you can use it on the Free plan. Agile CRM is a standard app in Make, not an Enterprise one, so all 40 modules are available from the start. The Free plan limits you to 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of run time per execution, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. You still need your own Agile CRM account, which Make does not provide.
02What does it take to connect Agile CRM to Make?
An active Agile CRM account and its API key. In Agile CRM, open Admin Settings, choose API & Analytics and copy the API key for REST client. In Make, add any Agile CRM module to a scenario, click Create a connection, give it a name if you like, and paste the credentials. Make saves that connection once and reuses it for every Agile CRM module you add afterwards, so you only do this setup a single time per account.
03Do Agile CRM triggers react in real time?
No. All 7 Agile CRM triggers in Make are scheduled, none of them is instant. Make checks your Agile CRM account on the scenario's schedule, which is every 15 minutes by default on a new scenario. On the Free plan, 15 minutes is also the shortest gap allowed, while paid plans can check as often as every minute. Plan your automations with that delay in mind: they suit follow-ups, syncs and reporting better than alerts that must land the very second something changes.
04What if the Agile CRM module you need does not exist?
Use Make an API Call. It reaches any endpoint of the Agile CRM API with the connection you already set up, so you are not limited to the ready-made modules. You write the request yourself, which means keeping the Agile CRM API reference open. Also note that the Make documentation for this app is marked as AI-generated and may contain mistakes, so confirm important details with Agile CRM directly before you build on them.
05Make or n8n for Agile CRM: which one fits?
It depends on where the rest of your automations live. Agile CRM has an app in Make with 40 modules, including 7 scheduled triggers and a Make an API Call module, and it also has a node in n8n. Neither choice locks you out of the CRM. Compare the modules each tool offers against the jobs you listed, check which platform your team already uses for other scenarios, and pick the one that keeps everything in one place. Our comparison page and the n8n version of this guide go into the details.
Same platform

Other docs you might need on this stack.

Browse all integrations