Resources · Make integration

noCRM.io Make integrationAutomate noCRM.io with Make.

Can Make keep your noCRM.io pipeline moving while your sales team sells? The noCRM.io Make integration gives you 31 modules, including 10 instant triggers. This page is for sales ops people new to Make: connect your account, then build your first scenario step by step.

Try the noCRM.io integration on MakeSee the 31 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the noCRM.io Make integration do for your pipeline?

The noCRM.io Make integration links your noCRM.io account to Make so that leads, prospecting lists and prospects can move between noCRM.io and your other tools without anyone copying data by hand. You build a scenario, the automation you design in Make, out of modules: one brick per trigger, action or search.

Leads that arrive already qualified. A web form in another app hands its answers to Make, and Create a Lead opens the deal in noCRM.io. Right after, Update an Amount and a Probability of a Lead can put a value on it.

A pipeline that reacts to itself. When a salesperson moves a deal, Watch Lead Step Changed or Watch Lead Status Changed wakes the scenario up. From there, Make can tag the lead, log an activity or warn another team in their own tool.

Cleaner prospecting lists. Search Prospecting Lists finds the right list, then Add a Prospect to a Prospecting List or Update a Prospect in a Prospecting List keeps each row current.

Know the limits before you start. Most triggers and a few actions only work on the noCRM.io Expert edition, and the doc lists no official connection steps. If a need falls outside the 31 modules, Make an API Call reaches the rest of the noCRM.io API. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick. For a second opinion on the tool itself, read the Make review, or check Make pricing before you scale up.

Connect

How do you connect noCRM.io to Make?

  1. 01

    Add a noCRM.io module

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

  2. 02

    Name the connection

    Give the connection a clear name if you like, such as the account or the team it belongs to. This step is optional, but it helps a lot when several noCRM.io accounts end up in the same Make organization.

  3. 03

    Authorize Make and save

    Follow what noCRM.io asks: approve access for Make on its page, or paste the key noCRM.io gives you. Then click Save. The noCRM.io doc for Make gives no extra steps, so these generic Make steps apply.

First scenario

Your first noCRM.io scenario in Make

GoalWhen a new lead is created in noCRM.io, Make gives it an estimated closing date so it shows up in your forecast.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. Search for noCRM.io by name.

  2. 02

    Pick Watch Lead Created

    Choose Watch Lead Created and click Create a connection if you have not linked noCRM.io yet. This trigger is instant: noCRM.io calls Make through a webhook the moment a lead appears.

  3. 03

    Add the closing date action

    Click the + on the right of the trigger and add Update an Estimated Closing Date on a Lead. Map the lead from the trigger, then pick the date you want to set.

  4. 04

    Test with Run once

    Click Run once, then create a test lead in noCRM.io. Make shows the bundle each module received, a bundle being one item passed from module to module, here one lead.

  5. 05

    Switch it on

    When the test lead has its date, switch the scenario on. From then on, each new lead triggers one run, and each module that runs counts as one operation on your Make plan.

Triggers

noCRM.io triggers in Make

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

noCRM.io1Watch Lead Assigned

Watch Lead Assigned

Instant trigger

In Make“Triggers when a lead is assigned or re-assigned to someone. This trigger only works for Expert edition.”

This trigger starts your scenario whenever a lead lands on a salesperson, whether it is a first assignment or a hand-over to a colleague. You get a clean moment to act on ownership changes.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the assignment happens.
When to use it
send the new owner a message in your team chat, or copy the owner into another tool that tracks who handles which account.
Watch out
it only works on the noCRM.io Expert edition, so check your plan before you build around it.
noCRM.io2Watch Lead Content/Description Changed

Watch Lead Content/Description Changed

Instant trigger

In Make“Triggers when the content(description) of a lead is updated. This trigger only works for Expert edition.”

Here you catch every edit to the lead description, the free text where reps note context, needs and next steps. Make receives the lead as soon as someone saves new text.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the description changes.
When to use it
keep a copy of the description in a spreadsheet or a shared doc so managers read the context without opening noCRM.io.
Watch out
Expert edition only, and every save counts, including small typo fixes.
noCRM.io3Watch Lead Created

Watch Lead Created

Instant trigger

In Make“Triggers when a new lead is created.”

The simplest entry point: each new lead in noCRM.io starts a run, so nothing new slips past your other tools. It is the trigger most first scenarios should use.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the lead exists.
When to use it
push the new lead into your mailing tool, warn the team channel, or give it a default amount and closing date.
Watch out
unlike most noCRM.io triggers, the doc gives it no Expert edition note, so it is the one to try first on another edition.
noCRM.io4Watch Lead Deleted

Watch Lead Deleted

Instant trigger

In Make“Triggers when a lead is deleted. This trigger only works for Expert edition.”

Your other tools learn that a lead is gone the moment it disappears from noCRM.io. That keeps mailing lists and reports from chasing deals that no longer exist.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the lead is deleted.
When to use it
remove the contact from a nurture list, or mark the matching row as closed in your reporting sheet.
Watch out
Expert edition only. The lead is already gone from noCRM.io, so a Get a Lead placed after it will most likely find nothing to read.
noCRM.io5Watch Lead (Manual Trigger)

Watch Lead (Manual Trigger)

Instant trigger

In Make“Triggers when someone clicks on the lead Actions menu for a manual fire. This trigger only works for Expert edition.”

This one gives your reps a button. A salesperson picks the scenario from the lead Actions menu, and Make runs on that single lead, only when a human decides.

How it fires
instant, noCRM.io calls Make through a webhook as soon as someone clicks the action.
When to use it
a step you do not want on every lead, such as sending a proposal request to another team or pushing a hot lead into a separate follow-up tool.
Watch out
Expert edition only. Name the scenario clearly so reps know what the click will do.
noCRM.io6Watch Lead Status Changed

Watch Lead Status Changed

Instant trigger

In Make“Triggers when a specific status of the lead is changed.”

You react to the outcome of a deal: the scenario starts when a lead takes the status you target, for example the one that marks a deal as won. It is the natural hook for anything that happens after the sale.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the status changes.
When to use it
hand a won deal to billing or onboarding, or send lost deals to a list for a later campaign.
Watch out
the doc says it reacts to a specific status, so test with Run once to see which status changes actually reach Make.
noCRM.io7Watch Lead Step Changed

Watch Lead Step Changed

Instant trigger

In Make“Triggers when a step of a lead is changed. This trigger only works for Expert edition.”

Every move of a lead through your pipeline steps can start a run. You follow the deal while it is still open, not only at the finish line.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the step changes.
When to use it
when a deal reaches a demo or proposal step, create the matching task in your project tool or send the prospect the right document.
Watch out
Expert edition only. A rep who moves a lead back and forth starts a run each time, and each run uses operations.
noCRM.io8Watch Prospect Created

Watch Prospect Created

Instant trigger

In Make“Triggers when a prospect is created in a prospect list. This trigger only works for Expert edition.”

Prospecting work gets its own trigger: each prospect added to a prospecting list reaches Make right away, before it ever becomes a lead.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the prospect exists.
When to use it
enrich the prospect in another tool, or copy it into a cold outreach sequence while your team is still qualifying it.
Watch out
Expert edition only, and it watches prospects in lists, not leads, so pair it with Watch Lead Created if you need both sides.
noCRM.io9Watch Task Status Changed

Watch Task Status Changed

Instant trigger

In Make“Triggers when a specific status of the task is changed. This trigger only works for Expert edition.”

Follow-up work becomes visible outside noCRM.io: the scenario starts when a task reaches the status you pick, such as done.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the task status changes.
When to use it
log completed calls in a shared report, or start the next step elsewhere once a rep ticks off a task.
Watch out
Expert edition only, and like the lead status trigger it reacts to a specific status; check with Run once which changes come through.
noCRM.io10Watch Unassigned Lead Created

Watch Unassigned Lead Created

Instant trigger

In Make“Triggers when a lead is created unassigned. This trigger only works for Expert edition.”

Leads that nobody owns yet are the ones that go cold. This trigger flags each lead created without an owner, so Make can make sure someone picks it up.

How it fires
instant, noCRM.io calls Make through a webhook as soon as the unassigned lead is created.
When to use it
alert a sales manager in the team chat, or post the lead in a channel where reps claim new deals.
Watch out
Expert edition only. Watch Lead Created may well fire on the same lead too, so test before wiring both to the same alert.
Modules

noCRM.io actions and searches in Make

noCRM.io gives you 21 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

noCRM.io1

Add an Attachment on a Lead

Action

In Make“Adds an attachment on a lead.”

A signed quote or a brief ends up on the lead where reps actually look, instead of in an inbox. The file comes from an earlier module of the scenario.

When to use it
a contract signed in another app should sit on the matching deal.
Watch out
on the Make Free plan, files are capped at 5 MB, so large documents can fail.
noCRM.io2

Add a Prospect to a Prospecting List

Action

In Make“Creates a row on a prospecting list specified by ID. This action only works for Expert edition.”

New names flow into your prospecting lists without anyone pasting rows. Each bundle, one contact from an earlier module, becomes one row in the list you target.

When to use it
event sign-ups or a purchased file should feed a list your reps work through.
Watch out
Expert edition only, and the list is chosen by its ID, so find it first with Search Prospecting Lists.
noCRM.io3

Add Tags on a Lead

Action

In Make“Adds new tags on a lead specified by ID. This action only works for Expert edition.”

Tags let your team filter and sort leads by source, product or campaign, and this action adds them for you. The lead is picked by its ID.

When to use it
tag every lead coming from a given form or webinar so reps know where it came from.
Watch out
Expert edition only; it adds new tags on top of existing ones.
noCRM.io4

Create a Comment on a Lead

Action

In Make“Creates a comment on a lead specified by ID. This action only works for Expert edition.”

Context from other tools shows up in the lead history as a comment, where the rep reads it before the next call. No more switching tabs to find what the prospect said.

When to use it
a support ticket or a reply to a campaign should appear on the deal.
Watch out
Expert edition only. Keep comments short and useful, or reps will stop reading them.
noCRM.io5

Create a Lead

Action

In Make“Creates a new lead.”

Every inbound request can become a deal in noCRM.io without retyping. You map the data from a form, a chat or a spreadsheet, and the lead appears in the pipeline.

When to use it
a website form or a booking tool collects requests your sales team should follow up.
Watch out
run Search Leads first if the same person may write twice, or you will get duplicates.
noCRM.io6

Delete a Lead

Action

In Make“Deletes a lead specified by ID.”

Spam and test entries leave your pipeline automatically, so reports stay honest. The action removes the lead you point to by ID.

When to use it
a lead flagged as spam in another tool should vanish from noCRM.io too.
Watch out
a deletion is hard to undo, so test with Run once on a dummy lead before you switch the scenario on.
noCRM.io7

Delete a Prospect in a Prospecting List

Action

In Make“Deletes a specific row on a prospecting list specified by ID.”

This removes one prospect row from a list, keeping your reps away from contacts who should not be called. You target the list and the row by ID.

When to use it
someone unsubscribes or asks to be left alone in another tool.
Watch out
the row is gone from the list, so copy anything you need with Get a Prospect in a Prospecting List first.
noCRM.io8

Get a Lead

Action

In Make“Gets a lead specified by ID.”

You fetch the full record of one lead when a trigger or another module only gave you its ID. Later modules can then map every detail of the deal.

When to use it
a webhook from another tool sends a lead ID and you need the title, amount or owner.
Watch out
it reads one lead by ID; to find a lead when you do not have its ID, use Search Leads instead.
noCRM.io9

Get a Prospect in a Prospecting List

Action

In Make“Gets a specific row on a prospecting list specified by ID.”

One prospect row, read in full, so you can send its details somewhere else. It needs the list ID and the row ID.

When to use it
after Watch Prospect Created, pull the complete row before sending it to an enrichment or outreach tool.
Watch out
it returns a single row; reading a whole list is the job of Get a Prospecting List.
noCRM.io10

Get a Prospecting List

Action

In Make“Gets a prospecting list specified by ID.”

Where the row module reads one prospect, this one reads the list itself, by its ID. You get what the list holds to use further down the scenario.

When to use it
export a list your team finished working to a sheet or a reporting tool.
Watch out
you need the list ID; if you only know its name, start with Search Prospecting Lists.
noCRM.io11

Log an Activity

Action

In Make“Logs an activity on a lead specified by ID. This action only works for Expert edition.”

Calls, meetings and emails that happen in other tools get recorded on the lead, so the activity history tells the whole story. The lead is chosen by ID.

When to use it
a meeting booked in a calendar tool or a call from your phone system should count as sales activity.
Watch out
Expert edition only, so check your plan before mapping it.
noCRM.io12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the 31 modules does what you need, this one calls any endpoint of the noCRM.io API with the connection you already set up. No second login.

When to use it
a noCRM.io feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the noCRM.io API documentation open and test with Run once.
noCRM.io13

Update a Lead

Action

In Make“Updates a lead specified by ID.”

The general edit tool: it changes a lead picked by ID, for all the details the more targeted update modules do not cover. Use it to keep noCRM.io in line with your other systems.

When to use it
contact details change in your billing or support tool and the deal should follow.
Watch out
for status, step, title, amount or closing date, the dedicated modules below are clearer.
noCRM.io14

Update an Amount and a Probability of a Lead

Action

In Make“Sets an amount and a probability of a lead specified by ID.”

Your forecast stays realistic because amount and probability are set together on the lead, without a rep editing them by hand. The lead is chosen by ID.

When to use it
a quote is sent from another app and the deal value should match it.
Watch out
both values are set in one move, so map both, not only the amount.
noCRM.io15

Update an Estimated Closing Date on a Lead

Action

In Make“Sets an estimated closing date on a lead specified by ID.”

Every open deal gets a closing date, which makes pipeline reviews far easier to read. This module writes that date on the lead you point to by ID.

When to use it
right after Watch Lead Created, as in the first scenario above, or when a prospect confirms a decision date.
Watch out
map a real date from an earlier module rather than typing a fixed one.
noCRM.io16

Update a Prospect in a Prospecting List

Action

In Make“Updates a specific row on a prospecting list specified by ID.”

Prospect rows stay current when the data changes elsewhere, so reps call with the right details. You target the list and the row by ID.

When to use it
an enrichment tool returns a job title or a phone number for a prospect already in a list.
Watch out
to add a new row rather than change one, use Add a Prospect to a Prospecting List.
noCRM.io17

Update a Status of a Lead

Action

In Make“Updates a status of a lead specified by ID.”

Deals close themselves when the proof arrives from another tool. The module changes the status of a lead picked by ID, for example the one that marks a won deal.

When to use it
a paid invoice or a signed contract should mark the deal as won.
Watch out
if Watch Lead Status Changed runs in another scenario, this update can start it too.
noCRM.io18

Update a Step of a Lead

Action

In Make“Updates a step of a lead specified by ID.”

A lead moves forward in the pipeline as soon as the prospect acts, not when a rep remembers to drag it. You pick the lead by ID and set its new step.

When to use it
a demo booked in a scheduling tool should push the deal to the demo step.
Watch out
this change can fire Watch Lead Step Changed in another scenario, so check the two do not feed each other.
noCRM.io19

Update a Title of a Lead

Action

In Make“Updates a title of a lead specified by ID.”

Clear lead titles make the pipeline readable at a glance. This module renames a lead picked by ID, for instance by adding the company and the product.

When to use it
leads created by a form get a generic title and you want a consistent naming rule.
Watch out
reps may search by title, so tell them before you change the naming.
noCRM.io20

Search Leads

Search

In Make“Searches leads by provided queries.”

Before you create or update anything, this search tells you whether the lead already exists. It runs your query and returns zero, one or several leads, each as its own bundle.

When to use it
a form reply arrives and you want to update the existing deal instead of opening a new one.
Watch out
zero results means the next modules do not run, and several results means they run once per lead found.
noCRM.io21

Search Prospecting Lists

Search

In Make“Searches a prospecting lists.”

Finding the right prospecting list by search saves you from hunting for IDs. The module returns the matching lists, each as a bundle, ready to feed the prospect modules.

When to use it
before Add a Prospect to a Prospecting List, to aim at the right list.
Watch out
several lists can match, and each one runs the next modules, which counts extra operations.
Need help

Need help automating noCRM.io with Make?

A person reads every message.

FAQ

noCRM.io and Make: common questions

01Is the noCRM.io Make integration free?
Yes, on the Make side. noCRM.io is a standard app, so it is available from the Free plan, like the 3,000+ standard apps. The Free plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes, handles files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits, with unlimited active scenarios and a 1-minute minimum interval. Your noCRM.io subscription is separate, and many noCRM.io modules require its Expert edition.
02What do you need to connect noCRM.io to Make?
A noCRM.io account and a Make account. The noCRM.io doc for Make lists no prerequisites and no specific steps, so the generic Make flow applies: add a noCRM.io module, click Create a connection, give it a name if you want, authorize Make on the noCRM.io page or paste the key noCRM.io gives you, then click Save. The connection is reused by every noCRM.io module. Check your noCRM.io edition at the same time, because most triggers and some actions only work on Expert.
03Do noCRM.io triggers in Make fire in real time?
Yes. All 10 noCRM.io triggers are instant: noCRM.io calls Make through a webhook as soon as the event happens, so the scenario starts right away instead of waiting for a schedule. That covers new leads, assignments, status and step changes, deletions, new prospects, task status changes and the manual button in the lead Actions menu. The 15-minute default interval of Make only concerns scheduled triggers, and noCRM.io has none. Keep in mind that eight of the triggers require the noCRM.io Expert edition.
04What if a noCRM.io module you need is missing in Make?
Use Make an API Call. This module reaches any endpoint of the noCRM.io API with the connection you already created, so you can cover what the 19 actions and 2 searches do not. You write the request yourself, which means reading the noCRM.io API documentation first, then testing with Run once before switching the scenario on. The Make doc for noCRM.io gives no numeric limit for the listed modules, so there is no documented cap to work around on that side.
05Should you use Make or n8n for noCRM.io?
It depends on what you already use. On Make, noCRM.io comes with 31 ready modules, including 10 instant triggers, and a connection you set up once, which suits teams that want to build visually from the Free plan. The same app often has an n8n node too, so check the n8n side for the exact modules you need before you commit. Compare the two on the modules available for your use case, on the plan limits that apply to your volume, and on the tool your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations