How to Build a CRM Automation With Make.com

To build a CRM automation with Make.com, you build one scenario with five parts. The first module watches your website form. The second module searches your CRM to check if the person is already a client. A filter then decides: a new person gets a contact and a deal, an existing client gets a note added to their card. The fourth module pings your sales team in Slack. The fifth adds a row to your weekly report.

What is Make.com, in plain terms?

The video explains Make.com like you have never opened it before. Make.com is a visual builder. You connect your apps like LEGO blocks, with no code at all.

Two words cover the whole tool. Each workflow is called a scenario. Each block in that workflow is called a module. Once you know those two words, the build below is just five modules placed in order, each with one clear job.

How do you build a CRM automation with Make.com step by step?

Step 1: a module that watches your website form

Module one watches your website form. A new request comes in, and that request starts the scenario.

This is the entry point. Nothing runs until someone fills out the form, so the CRM update is tied to a real inquiry, not to a person remembering to copy details over later.

Step 2: a module that searches your CRM

Module two searches your CRM. The question it answers is simple: is this person already a client?

That search matters because a new lead and an existing client should not be handled the same way. Checking first is what stops the scenario from creating a duplicate contact for someone who is already in the system.

Step 3: a filter that decides new or existing

Then a filter decides, based on the search. If the person is new, the scenario creates a contact and a deal. If the person is an existing client, it adds a note to their card instead.

For example, as an illustration: a first time inquiry becomes a new contact with a new deal to work, while a current client who sends a new request does not get a second record. Their existing card simply gains a note about the new request, so the history stays in one place.

Step 4: a module that pings your sales team in Slack

Module four pings your sales team in Slack.

The record alone is not enough if nobody knows it changed. A Slack ping tells the team a request came in and the CRM is already updated, so the next step is a human follow up, not data entry.

Step 5: a module that adds a row to your weekly report

Module five adds a row to your weekly report.

That last module closes the loop. Each form request leaves a trace in the weekly report as it happens, instead of someone rebuilding the week from memory or from scattered records later.

What happens when you switch the scenario on?

Switch it on and it runs every time someone fills out the form.

That is the whole point of the sequence described in the video. The form watch, the CRM search, the filter, the Slack ping, and the report row happen in order for each new request, without a person moving the data by hand between steps.

Which CRMs can you use with this Make.com scenario?

The video names two directly: HubSpot and Pipedrive plug right in, and it says many other CRMs do too.

So the scenario is not tied to one CRM. The pattern stays the same whichever CRM you connect: watch the form, search the CRM first, let the filter split new people from existing clients, tell the sales team, and log the result in the weekly report.

How do you grow this into a CRM that handles the routine?

The video ends with a simple pace: build one scenario a week, and in a month your CRM handles most of the routine on its own.

That pace is part of the lesson. You do not need to automate everything at once. Start with this one form to CRM scenario, let it run, then add one more scenario the next week for the next routine task. This series, the video notes, is for owners and managers learning to put AI and automation inside their processes, and it closes with a prompt to save the video for your first Make scenario.

What this means for your business

Manual lead updates are the work this scenario removes. In the setup from the video, a website form request no longer waits for someone to check the CRM, create or update a record, tell the sales team, and remember the report.

Start with the five parts in order: form, search, filter, Slack, report. If any one of those steps is still done by hand in your business today, that step is the clearest place where requests can be missed, duplicated, or delayed.

Frequently asked questions

How do you build a CRM automation with Make.com?

Build one scenario with five parts: a module that watches your website form, a module that searches your CRM, a filter that creates a contact and a deal for a new person or adds a note for an existing client, a module that pings your sales team in Slack, and a module that adds a row to your weekly report. Switch it on and it runs every time someone fills out the form.

What is a scenario and a module in Make.com?

In Make.com, each workflow is called a scenario and each block in that workflow is called a module. Make.com is a visual builder, so you connect your apps like LEGO blocks, with no code at all.

How does the automation avoid duplicate CRM records?

The second module searches your CRM to check if the person is already a client, and a filter decides what happens next. A new person gets a contact and a deal created. An existing client gets a note added to their card instead of a new record.

Which CRMs work with a Make.com automation like this?

The video names HubSpot and Pipedrive as CRMs that plug right in, and says many other CRMs do too. The five part pattern stays the same whichever CRM you connect.

How fast should you add more CRM automations?

The video suggests building one scenario a week. At that pace, it says, in a month your CRM handles most of the routine on its own.

Keep Reading: How to Automate Your Entire Sales Pipeline in a CRM

Keep Reading: How to Build a Simple Zapier Automation