Integration · Make

Automate what happens to every lead with Make

The Larvabot app for Make (formerly Integromat) watches for new leads, contacted leads, replies and conversations, and hands them to a visual scenario. Route hot conversations to Slack and the rest to a sheet, enrich a business before it reaches your CRM, or build a weekly digest. If you like seeing the whole flow on one canvas, Make is the better fit.

Available now, and in review for Make's public app directory

Triggers

What can start a scenario. Each comes with the lead's full details.

Watch New Leads

Larvabot scores a business as a fit.

Watch Contacted Leads

The first email to a lead is sent.

Watch Lead Replies

A lead replies to your email.

Watch New Conversations

Someone posts asking for what you sell, scored 50 or more.

Popular workflows

Route conversations by score

LarvabotSlackGoogle Sheets

Watch New Conversations → Router: relevance 85+ goes to a Slack channel with the drafted reply; everything else is added to a review sheet.

Enrich, then add to the CRM

LarvabotHubSpotPipedrive

Watch New Leads → look up the company → Create or update the organisation and person in your CRM, with Larvabot's fit reason as a note.

Per-project pipelines for agencies

LarvabotAirtableNotion

One scenario per client project (pick the project on the trigger), each writing to that client's own base or board.

A Monday digest

LarvabotGmailSlack

Schedule a weekly run → Make an API Call to /leads?event=replied → Text aggregator → send one summary of last week's replies.

When Make is the right choice

Branching workflows: one router sends each lead somewhere different by fit score, platform or project.
Lower cost at volume: Make bills per operation, which is usually cheaper than per-task pricing for busy scenarios.
Advanced users who want the Make an API Call module for anything the ready-made modules don't cover.

Set it up in five minutes

1In Larvabot, open Settings → Integrations and click Create API key. Copy it.
2Add the Larvabot app in Make with the link on the same page, then create a scenario and add a Larvabot Watch module.
3Click Add next to Connection and paste your API key.
4Pick a project (or leave it empty for all), set the limit and choose where to start: from now on, or including recent items.
5Add the next modules, map the fields and switch the scenario on with a schedule (every 15 minutes is plenty).

Field-by-field details: Send leads to your CRM · API reference

What it costs

The Larvabot app for Make is included in every Larvabot plan, the free trial too. Make has its own plans: each run of a scenario uses operations, and the free plan includes a monthly allowance that's usually enough for a small project.

Good to know

It's one way: Larvabot sends to your apps; nothing comes back from Make into Larvabot.
Watch modules run on your scenario's schedule, so items arrive at the next run, not instantly.
The API is read-only, so Make an API Call can read leads, conversations and projects but not change them.

Frequently asked questions

Does Larvabot work with Make (Integromat)?

Yes. The Larvabot app for Make has four Watch modules (new leads, contacted leads, lead replies and new conversations) plus Make an API Call, and connects with an API key from Settings → Integrations.

Make or Zapier: which should I use with Larvabot?

Zapier if you want the most apps and the quickest setup. Make if you want branching (routers), cheaper runs at volume, or to see the whole workflow on one canvas. The Larvabot apps for both have the same triggers and data.

How often does Make check for new leads?

As often as you schedule the scenario: every 15 minutes is a good default. Larvabot itself checks conversations about every two hours, so faster rarely helps.

Start finding the leads to send

Larvabot finds people asking for what you sell and businesses worth emailing, with a draft for each. The Make app is included in every plan. 14 days free, no card required.

Get started See pricing