Resources · Make integration

EspoCRM Make integrationAutomate EspoCRM with Make.

Can Make keep EspoCRM updated while your team sells? The EspoCRM Make integration gives you 44 modules: 1 instant trigger, 35 actions and 8 searches. This guide shows how to connect your account and build a first working scenario.

Try the EspoCRM integration on MakeSee the 44 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the EspoCRM Make integration do?

The EspoCRM Make integration links your CRM to the other tools you use through Make, a no-code automation platform. You build a scenario, the automation itself, as a chain of modules: each module is one brick, like a trigger that listens to EspoCRM or an action that writes to it.

Follow-up that happens on its own. Watch Changes reacts when a lead appears, and Create a Task puts a callback on a salesperson's list. Nobody has to remember to assign it.

A support queue fed from outside. A form on your site becomes a case with Create a Case, and Create an Attachment puts the customer's screenshot on it. List Cases then helps another tool display what is still waiting.

A pipeline that matches your quotes. Create an Opportunity records a quote sent from your billing tool, and Update an Opportunity marks it won once signed elsewhere.

There is only one trigger, and it is instant, so everything else starts from that webhook, from another app or from a schedule. For entities without a dedicated module, Make an API Call reaches the EspoCRM API with the same connection. Make's own page on EspoCRM also warns that its content is AI-generated from EspoCRM documentation, so double-check important details.

To judge the platform before you start, read the Make review or check Make pricing. The same app often has an n8n node too; the n8n vs Make comparison lays out the differences.

Connect

How do you connect EspoCRM to Make?

  1. 01

    Create an API user in EspoCRM

    In EspoCRM, go to Administration, open Roles, click Create and give the new role the permissions the scenario needs. Save, then open API Users, create a user with that role and copy its API key.

  2. 02

    Add an EspoCRM module in Make

    In your scenario, add any EspoCRM module and click Create a connection. The connection is your EspoCRM account linked to Make once, then reused by every EspoCRM module. The Connection name field is optional.

  3. 03

    Paste your credentials

    Enter the credentials copied from EspoCRM, or follow the instructions shown on screen. The doc lists two methods for the API user: an API key or HMAC authentication. Save, and Make can now read your CRM.

First scenario

Your first scenario: a callback task for every new lead

GoalWhen a lead is created in EspoCRM, Make creates a callback task for the sales team.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for EspoCRM and pick Watch Changes.

  2. 02

    Set up the webhook

    Click Create a webhook, then Create a connection with your API key. The trigger covers creations, updates, deletions and field changes across entity types; in its fields, point it at new leads.

  3. 03

    Add the task

    Click the + on the right of the trigger and add Create a Task. Map the lead's name from the previous module into the task so the salesperson knows who to call.

  4. 04

    Test with Run once

    Click Run once, then create a test lead in EspoCRM. Make shows the bundles each module received: one bundle is one item, here your lead. Check that the task appeared in EspoCRM.

  5. 05

    Switch it on

    Save and turn the scenario on. Since the trigger is instant, EspoCRM calls Make as each lead arrives; every module run then counts as an operation on your Make plan.

Triggers

What triggers an EspoCRM scenario?

1 module starts a scenario when something happens in EspoCRM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by EspoCRM as soon as it happens.

EspoCRM1Watch Changes

Watch Changes

Instant trigger

In Make“Watches the creation, updating, deleting or field change events of various entity types.”

Starts your scenario the moment a record in EspoCRM is created, updated, deleted or has a field changed, across several entity types, so Make works on fresh events instead of waiting.

How it fires
instant: the app calls Make through a webhook as soon as it happens. Look for the lightning badge on the module.
When to use it
a lead lands in the CRM and sales should get a task, or a case changes and the customer should be told without anyone watching the screen.
Watch out
click Create a webhook before Create a connection. And if the same scenario updates the entity it watches, each update can fire it again, so filter out your own changes.
Modules

What can EspoCRM do in Make?

EspoCRM gives you 43 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

EspoCRM1

Compose an Email

Action

In Make“Composes an email.”

Builds an email inside EspoCRM from data the scenario already holds, so the message lives in the CRM next to the customer instead of in a personal outbox.

When to use it
a case moves forward and the customer should hear about it, with wording assembled from what the previous modules received.
Watch out
to join a file, prepare it first with Create an Attachment, which the doc ties to email composition.
EspoCRM2

Create a Call

Action

In Make“Creates a call.”

Logs a phone call in EspoCRM for you, so the conversation shows up in the history without anyone typing a recap after hanging up.

When to use it
your phone system reports a finished call and the sales team wants the record in the CRM right away.
Watch out
each run adds a new call; if the same event can reach Make twice, check with List Calls before creating.
EspoCRM3

Create a Case

Action

In Make“Creates a case.”

Opens a support case in EspoCRM from a form, an inbox or any app Make connects, so every request lands in one queue your team can follow.

When to use it
a customer fills in the support form on your website and the request should become a trackable case.
Watch out
a form submitted twice produces two cases; List Cases can check for an existing one before this module runs.
EspoCRM4

Create a Contact

Action

In Make“Creates a contact.”

Adds a person to EspoCRM as a contact, filled with details another app already collected, so nobody retypes names from one tool to the next.

When to use it
someone places a first order in your online store and should exist in the CRM from that moment.
Watch out
Make does not look for duplicates on its own; search with List Contacts first when the same buyer can come back.
EspoCRM5

Create a Lead

Action

In Make“Creates a lead.”

Turns an inbound request into a lead in EspoCRM, ready for sales to qualify, without a spreadsheet export in between.

When to use it
a demo request or a webinar signup should reach sales while the prospect still remembers filling in the form.
Watch out
if one person can sign up through two forms, run List Leads first so sales does not call them twice.
EspoCRM6

Create a Meeting

Action

In Make“Creates a meeting.”

Puts a meeting on the EspoCRM calendar so the CRM matches what was actually booked with the prospect or client.

When to use it
a booking tool confirms an appointment and the account manager should see it on the record before the call.
Watch out
a rescheduled booking belongs to Update a Meeting; sending it here again leaves the old slot in the CRM.
EspoCRM7

Create an Account

Action

In Make“Creates an account.”

Creates a company record, what EspoCRM calls an account, so contacts, deals and cases have an organization to belong to.

When to use it
a contract gets signed with a new client company and finance and sales both need it in the CRM.
Watch out
company names are rarely typed the same way twice; List Accounts before creating keeps a single record per company.
EspoCRM8

Create an Attachment

Action

In Make“Creates an attachment for case, task, or composing an email.”

Uploads a file into EspoCRM as an attachment, which the doc says can serve a case, a task or an email you compose.

When to use it
a customer sends a screenshot with a support request and the image should sit on the case where agents look.
Watch out
on the Free plan Make handles files up to 5 MB, so a heavier file stops in Make before reaching EspoCRM.
EspoCRM9

Create an Opportunity

Action

In Make“Creates an opportunity.”

Records a deal as an opportunity in EspoCRM, so the pipeline shows a quote or a request as soon as it exists elsewhere.

When to use it
a quote leaves your invoicing tool and the sales manager wants the deal visible in the pipeline for follow-up.
Watch out
resending the same quote creates a second deal; keep one scenario as the only door for new opportunities.
EspoCRM10

Create a Task

Action

In Make“Creates a task.”

Hands someone a to-do in EspoCRM, generated by the scenario, so follow-ups stop depending on anyone's memory.

When to use it
Watch Changes reports a new lead and a salesperson should get a callback task attached to it.
Watch out
test with Run once, then open the task in EspoCRM to confirm who it landed on before switching the scenario on.
EspoCRM11

Delete a Call

Action

In Make“Deletes a call.”

Removes a call record from EspoCRM, which is handy when another automation logged calls by mistake.

When to use it
a test scenario filled the CRM with fake calls and List Calls can feed each one to this module for cleanup.
Watch out
Make cannot bring a deleted call back; run the search alone with Run once and read the bundles before adding this step.
EspoCRM12

Delete a Case

Action

In Make“Deletes a case.”

Erases a case from EspoCRM for good, which suits spam and duplicates better than genuine requests that were resolved.

When to use it
a spam check upstream flags a message that had already become a case and you want the queue clean again.
Watch out
to keep the history of a real request, change its data with Update a Case instead of removing it.
EspoCRM13

Delete a Contact

Action

In Make“Deletes a contact.”

Takes a person out of EspoCRM entirely, rather than simply marking them as inactive somewhere else.

When to use it
someone asks for their data to be erased and your intake tool should trigger the removal in the CRM too.
Watch out
two people can share a name; confirm the exact record with Get a Contact first, because deletion is final.
EspoCRM14

Delete a Lead

Action

In Make“Deletes a lead.”

Gets rid of a lead from EspoCRM and keeps the sales queue free of junk entries that nobody will ever call.

When to use it
a spam check runs after the lead was created and the fake prospect should disappear before sales sees it.
Watch out
a real lead that went cold still has history worth keeping; Update a Lead preserves it for later.
EspoCRM15

Delete a Meeting

Action

In Make“Deletes a meeting.”

Drops a meeting from EspoCRM so the calendar stops showing an appointment nobody plans to attend.

When to use it
a booking gets cancelled in your scheduling tool and the slot should vanish from the CRM record as well.
Watch out
the scenario must know which meeting to remove, so keep the EspoCRM record from the moment it was created.
EspoCRM16

Delete an Account

Action

In Make“Deletes an account.”

Deletes a company record from EspoCRM, the heaviest cleanup among these modules.

When to use it
two accounts exist for the same company and everything useful already sits on the one you are keeping.
Watch out
check with Get an Account which record you are about to remove; nothing in Make restores it afterwards.
EspoCRM17

Delete an Opportunity

Action

In Make“Deletes an opportunity.”

Pulls a deal out of the EspoCRM pipeline so forecasts stop counting something that was never real.

When to use it
a duplicate opportunity came from the same quote being sent twice and only one should stay.
Watch out
a lost deal is still information; if it was genuine, record the outcome with Update an Opportunity instead.
EspoCRM18

Delete a Task

Action

In Make“Deletes a task.”

Clears a task from EspoCRM, so nobody receives reminders about work that no longer exists.

When to use it
a lead was disqualified and the automatic follow-up task created for it should disappear with it.
Watch out
it removes the one task you point to; when several match, List Tasks sends them one bundle at a time.
EspoCRM19

Get a Call

Action

In Make“Gets a call.”

Reads one call from EspoCRM and passes its details to the next modules of the scenario.

When to use it
an earlier module tells you a call was updated and you want the full record before posting a summary in your team chat.
Watch out
it returns a single call you identify; to find calls by a criterion, List Calls is the right module.
EspoCRM20

Get a Case

Action

In Make“Gets a case.”

Fetches a single case as it stands now, so the scenario works from fresh data rather than an old copy.

When to use it
a customer replies by email and the scenario must check the current state of the case before deciding what to send.
Watch out
give it the case an earlier module produced; on its own, it has no way to guess which case you mean.
EspoCRM21

Get a Contact

Action

In Make“Gets a contact.”

Pulls one contact out of EspoCRM and gives later modules the person's details to reuse wherever you need them.

When to use it
an invoice about to be issued in another tool should carry the contact details stored in the CRM.
Watch out
if all you have is a name or an email, start with List Contacts; this module expects one precise record.
EspoCRM22

Get a Lead

Action

In Make“Gets a lead.”

Loads a lead from EspoCRM so the scenario can decide what happens next based on what the record holds.

When to use it
a filter should route promising leads to one teammate and the rest to another, based on the lead's data.
Watch out
skip it when the bundle from the previous module already holds what you need; every module run costs an operation.
EspoCRM23

Get a Meeting

Action

In Make“Gets a meeting.”

Reads the details of one meeting in EspoCRM, useful when another app expects them in its own format.

When to use it
a meeting was just updated and a reminder message should be built from the version stored in the CRM.
Watch out
run it after the module that tells you which meeting changed, not as the first step of the scenario.
EspoCRM24

Get an Account

Action

In Make“Gets an account.”

Retrieves a company record from EspoCRM to enrich what the rest of the scenario sends elsewhere.

When to use it
a new invoice in your accounting tool should carry the company details exactly as sales keeps them in the CRM.
Watch out
it returns one account; looking up companies by name is the job of List Accounts.
EspoCRM25

Get an Opportunity

Action

In Make“Gets an opportunity.”

Looks up one deal in EspoCRM so its data can travel to the next steps of the scenario.

When to use it
an opportunity just changed and the team channel should get a message with the deal details, not just a notification.
Watch out
read the bundle in Run once before mapping, so you know what the module really returns for your deals.
EspoCRM26

Get a Task

Action

In Make“Gets a task.”

Grabs a single task from EspoCRM with its latest state, whatever changed on it last.

When to use it
a project tool mirrors CRM tasks and needs the current version each time one is modified.
Watch out
place it after the module that tells you which task changed; each fetch counts as one operation.
EspoCRM27

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the EspoCRM API with the connection you already set up, covering whatever the listed modules leave out.

When to use it
you need an entity or an action that has no dedicated module on this page.
Watch out
you write the request yourself, so keep the EspoCRM API documentation open and test the call with Run once.
EspoCRM28

Update a Call

Action

In Make“Updates a call.”

Corrects a call that already exists in EspoCRM, so the record reflects what really happened on the phone.

When to use it
a call was logged ahead of time and your phone system later reports how it went.
Watch out
the module needs to know which call to change; keep it from Create a Call or find it with List Calls.
EspoCRM29

Update a Case

Action

In Make“Updates a case.”

Edits an existing case, the right move when a request evolves instead of ending.

When to use it
your helpdesk marks a ticket as solved and the matching EspoCRM case should follow without a manual edit.
Watch out
it changes one case at a time; to update many, a search module has to feed them in one by one.
EspoCRM30

Update a Contact

Action

In Make“Updates a contact.”

Keeps a contact current by writing new details over the old ones in EspoCRM.

When to use it
a customer changes their address in your store account and the CRM should stay aligned.
Watch out
a loop is easy to build: if Watch Changes watches contacts and this module edits contacts, each edit can restart the scenario.
EspoCRM31

Update a Lead

Action

In Make“Updates a lead.”

Moves a lead forward in EspoCRM by changing its data after something happened in another tool.

When to use it
the prospect books a demo on your site and sales should see that progress on the lead.
Watch out
send only the data that changed; test with Run once and compare the lead before and after.
EspoCRM32

Update a Meeting

Action

In Make“Updates a meeting.”

Adjusts a meeting already in EspoCRM, typically when the booking moves to another time.

When to use it
your scheduling tool reports a new slot for an appointment that was already confirmed.
Watch out
if the booking tool sends a cancellation instead, route it to Delete a Meeting rather than this module.
EspoCRM33

Update an Account

Action

In Make“Updates an account.”

Refreshes a company record in EspoCRM with information coming from another system.

When to use it
your billing tool is where addresses get corrected, and each correction should reach the CRM account.
Watch out
decide which tool wins for each piece of data, or two scenarios will keep overwriting each other.
EspoCRM34

Update an Opportunity

Action

In Make“Updates an opportunity.”

Pushes new data onto a deal in EspoCRM so the pipeline follows what happens outside the CRM.

When to use it
a quote gets signed in your e-signature tool and the opportunity should reflect the win.
Watch out
check the outcome in EspoCRM after Run once before switching on; a wrong mapping touches every deal that passes.
EspoCRM35

Update a Task

Action

In Make“Updates a task.”

Modifies an existing task, to reassign it or close it from outside EspoCRM.

When to use it
someone ticks the item off in your project tool and the CRM task should close as well.
Watch out
it needs the task's identity from an earlier module; Get a Task or List Tasks can supply it.
EspoCRM36

List Accounts

Search

In Make“Lists or searches accounts.”

Searches your EspoCRM accounts and returns every match as its own bundle, one item that flows to the next modules.

When to use it
before creating a company, check whether it already exists so the CRM keeps one record per client.
Watch out
if nothing matches, no bundle comes out and the modules after it do not run for that item.
EspoCRM37

List Calls

Search

In Make“Lists or searches calls.”

Finds calls in EspoCRM and hands them over one bundle at a time to the rest of the scenario.

When to use it
a manager wants the calls matching a search copied into a spreadsheet for a review.
Watch out
every call found runs the following modules once, and each of those runs counts as operations on your plan.
EspoCRM38

List Cases

Search

In Make“Lists or searches cases.”

Looks through EspoCRM cases and returns the ones that match your search, each as a separate bundle.

When to use it
a dashboard in another tool should show the cases still waiting for an answer.
Watch out
a wide search on a busy support queue returns many bundles; narrow it before connecting modules that write.
EspoCRM39

List Contacts

Search

In Make“Lists or searches contacts.”

Searches contacts in EspoCRM, returning zero, one or several people depending on what matches.

When to use it
your store sends an order and you need to know whether the buyer is already in the CRM before creating anyone.
Watch out
several matches mean several bundles, so the next module runs once per person found.
EspoCRM40

List Leads

Search

In Make“Lists or searches leads.”

Pulls leads out of EspoCRM that match your criteria and passes each one along as a bundle.

When to use it
sales wants the leads matching a search copied to a sheet for a quick review.
Watch out
connect a write module after it only once Run once shows the right leads; otherwise it touches every result.
EspoCRM41

List Meetings

Search

In Make“Lists or searches meetings.”

Pulls the meetings stored in EspoCRM that match your search into the scenario, each as its own bundle, ready to feed a recap or a follow-up step.

When to use it
a sales manager wants every meeting matching a search pushed to a shared sheet, rather than fetching one known meeting with Get a Meeting.
Watch out
the search can return zero, one or many bundles, and each following module runs once per bundle, so plan for the empty case.
EspoCRM42

List Opportunites

Search

In Make“Lists or searches opportunites.”

Brings back the deals of your EspoCRM pipeline that match your search, one bundle per deal, so the next modules can report on them or act on each one.

When to use it
a revenue lead needs a batch of deals sent to a dashboard, not the single record Get an Opportunity returns.
Watch out
every returned deal triggers the modules after it, and each run of a module on a bundle counts as an operation on your Make plan.
EspoCRM43

List Tasks

Search

In Make“Lists or searches tasks.”

Collects tasks from EspoCRM that match your search and hands them over one bundle at a time, to remind owners or copy them to another tool.

When to use it
a support coordinator wants all tasks matching a search posted to a team channel, instead of reading one task with Get a Task.
Watch out
when nothing matches, no bundle comes out and the rest of the scenario stays idle, so test with Run once first.
Need help

Need help automating EspoCRM with Make?

A person reads every message.

FAQ

EspoCRM and Make: frequent questions

01Is the EspoCRM Make integration free?
Yes, EspoCRM is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your EspoCRM subscription is a separate matter, handled on EspoCRM's side.
02What do you need to connect EspoCRM to Make?
You need an active EspoCRM account and an API user with either an API key or HMAC authentication. You create that API user in EspoCRM under Administration: first a role with the permissions you want to give Make, then the API user attached to that role. Copy the key it displays, then click Create a connection in any EspoCRM module in Make and paste it. The connection is then reused by every EspoCRM module.
03Does the EspoCRM trigger in Make work in real time?
Yes. Watch Changes is an instant trigger: EspoCRM calls Make through a webhook as soon as a record is created, updated, deleted or has a field changed, instead of Make checking on a schedule. That is why you click Create a webhook before creating the connection. It is the only trigger of the app, so scenarios that need to start from something else begin with another app or with a scheduled first module.
04What if an EspoCRM module is missing in Make?
Use Make an API Call. With the connection you already created, it can reach any endpoint of the EspoCRM API, so a record type or an action without a dedicated module is still within reach. You write the request yourself, so keep the EspoCRM API documentation at hand and test with Run once. Make also notes that its EspoCRM documentation is AI-generated from the vendor's docs, so confirm important details with EspoCRM.
05Should you use Make or n8n for EspoCRM?
It depends on what you need to build. On Make, EspoCRM comes with 44 modules, including 1 instant trigger that watches creations, updates, deletions and field changes, plus Make an API Call for the rest. The same app often has an n8n node as well, so compare the modules each side offers for your entities before choosing. If your team already runs one of the two platforms, starting there keeps a single place to monitor your automations. The n8n vs Make comparison page covers both in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations