Resources · Make integration

Emailchaser Make integrationAutomate Emailchaser with Make.

Can Make feed your Emailchaser campaigns and react when a lead answers? The Emailchaser Make integration gives you 3 modules: 1 trigger and 2 actions. This guide covers the connection, a first scenario and when to pick each module.

Try the Emailchaser integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Emailchaser Make integration automate?

The Emailchaser Make integration links your cold email account to Make, so a scenario (the automation you build in Make, a chain of modules) can push leads into a campaign or react when a lead replies. Each module is one brick of that chain, and you set it up without writing code.

Replies land where sales works. Watch Lead Reply picks up answers from your leads, and the next module can send them to your CRM or your team chat, so nobody has to dig through the outreach inbox to find a warm prospect.

New prospects enter a sequence without copy-paste. When a form, a spreadsheet or a CRM produces a fresh contact, Add Leads To Campaign drops it into the right Emailchaser campaign. For a recruiting agency or a B2B consultant, that is the list that feeds itself.

Anything else goes through the API. Make an API Call reuses the same connection to reach any part of the Emailchaser API that the two other modules leave out.

The catalog is short: 3 modules, no search module, no instant trigger. The Make documentation for this app also warns that it was generated with AI from the Emailchaser docs and may contain mistakes, so test with Run once before you trust a scenario. If you are weighing tools, the n8n vs Make comparison lays out the differences, the Make pricing page explains plans, and the Make training helps you learn the editor.

Connect

How do you connect Emailchaser to Make?

  1. 01

    Create an API key in Emailchaser

    In your Emailchaser account, click Create API key, give the key a name, select its scopes, then click Create. Copy the key shown on screen right away: Make will ask for it in the next step.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the key and save

    Type a label in Connection name if you run several accounts, which is optional. Paste the API key, or follow the instructions Make shows on screen, and confirm to save the connection.

First scenario

Your first scenario: send new leads to an Emailchaser campaign

GoalWhen a new contact appears in another app, Make adds that lead to your Emailchaser campaign.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. It comes from the app where your contacts show up, such as a form tool or a spreadsheet.

  2. 02

    Set up that first module

    Pick the module that watches for new contacts, connect that app and fill its fields. Make lists what it can read once the connection exists, so you choose from a menu instead of typing names.

  3. 03

    Add Add Leads To Campaign

    Click the + on the right, search for Emailchaser and pick Add Leads To Campaign. Use your Emailchaser connection, then map the contact data coming from the first module into the fields.

  4. 04

    Test with Run once

    Click Run once and create a test contact in the source app. Open the bundles each module received (a bundle is one item passed along, here one lead) and check the lead reached Emailchaser.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one lead is an operation, the unit Make counts on your plan.

Triggers

What starts an Emailchaser scenario

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

Emailchaser1Watch Lead Reply

Watch Lead Reply

triggerIn the docs only

Get every answer from your outreach leads handed to the rest of your scenario, so a reply turns into a task, a message or a CRM update instead of waiting in a mailbox. Each reply arrives as its own bundle for the next module.

How it fires
scheduled. Make checks Emailchaser on the scenario's schedule, every 15 minutes by default and never faster than 15 minutes on the Free plan, so replies show up in batches rather than the second they arrive.
When to use it
a sales team that wants each positive answer posted where it works, without anyone watching the outreach inbox.
Watch out
the directory gave no description for this trigger, so run it once with a real reply and read the bundle before building on it.
Modules

What the Emailchaser modules do

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

Emailchaser1

Add Leads To Campaign

ActionIn the docs only

Put new prospects straight into an Emailchaser campaign, so your sequence starts for them without an export, a CSV or a manual import. It acts on one lead per bundle it receives.

When to use it
after a form, a spreadsheet or a CRM hands a fresh contact to the scenario, and that contact belongs in outreach.
Watch out
if you also use Watch Lead Reply, keep reply handling apart from lead creation so a replying lead is not sent back into a campaign.
Emailchaser2

Make an API Call

ActionIn the docs only

Reach any part of the Emailchaser API that the two other modules do not cover, using the Emailchaser connection you already set up. You call the endpoint yourself, which gives you room beyond the short module list.

When to use it
the action you need is not Add Leads To Campaign and no trigger fits either.
Watch out
this module expects you to read the Emailchaser API documentation; if a call fails, the Make troubleshooting guide helps you read the error.
Need help

Need help automating Emailchaser with Make?

A person reads every message.

FAQ

Emailchaser and Make: common questions

01Is the Emailchaser Make integration free?
Yes, on the Make side. Emailchaser is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes and limits transfer to 512 MB. Paid plans such as Core, Pro, Teams and Enterprise drop the interval to 1 minute and remove the cap on active scenarios. Your Emailchaser subscription is separate: you need an active Emailchaser account, and its own pricing page tells you what it costs.
02What does the Emailchaser Make integration need to connect?
An active Emailchaser account and an API key. In Emailchaser, click Create API key, name it, select the scopes and click Create, then copy the key shown. In Make, add an Emailchaser module, click Create a connection, optionally fill Connection name, and paste the key. That single connection then serves every Emailchaser module in all your scenarios, so you only do this once per account. Pick a connection name that tells accounts apart if your team runs more than one.
03Does Watch Lead Reply react in real time?
No. Watch Lead Reply is a scheduled trigger: Make asks Emailchaser for new replies each time the scenario runs, following the schedule set on the first module. A new scenario runs every 15 minutes by default. On a paid plan you can go down to 1 minute, while the Free plan keeps 15 minutes as the minimum. Emailchaser has no instant trigger in Make, so plan your follow-up around that delay.
04What if an Emailchaser module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Emailchaser API with the connection you already created, so you are not limited to the trigger and the single campaign action. You will need the Emailchaser API documentation to set the call up. Also keep in mind that the Make page for this app is AI-generated from the vendor docs and may contain mistakes, so verify important details with Emailchaser.
05Make or n8n for Emailchaser: which one fits?
It depends on the tool you already run. The same app often has an n8n node too, so check that before choosing. On Make, Emailchaser comes with 3 modules, a scheduled reply trigger and an API call module, and it works from the Free plan. The criteria that should decide are the editor your team prefers and where the rest of your automations already live, rather than this one app.
Same platform

Other docs you might need on this stack.

Browse all integrations