Resources · Make integration

Encharge Make integrationAutomate Encharge with Make.

Your Encharge contacts can drive the rest of your stack. The Encharge Make integration gives you 13 modules: 5 instant triggers and 8 actions on people and tags. This page shows you how to link your account and build a first scenario, step by step.

Try the Encharge integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Encharge Make integration automate?

The Encharge Make integration links your Encharge account to Make, a visual tool where you chain apps together without code. Each automation you build is called a scenario. With it, a new person, a tag or an unsubscribe in Encharge can start work in your other tools, and data from those tools can create or update people in Encharge.

Tag leads from any form. A lead comes in through a form tool you already use. Create a Person adds them to Encharge, then Add Tags to a User files them under the right tag, so the matching email flow can pick them up.

Keep opt-outs consistent. Watch User Unsubscribed tells Make the moment someone stops receiving your emails. The next module can mark that contact in your CRM or a spreadsheet, and nobody on the team keeps mailing a person who said no.

Let a tag start a sales task. Watch User Tagged listens for one tag you choose. When a person gets it, Make can post a message to your sales channel or open a deal elsewhere. Remove Tags from a User closes the loop when the person moves on.

What Make does not give you: the Make documentation for Encharge is marked as limited, with no official connection steps and no troubleshooting notes. Anything the 8 actions do not cover goes through Make an API Call. Before you commit, the Make review covers the tool itself, Make pricing explains how operations are counted, and n8n vs Make helps if you are still choosing a platform.

Connect

How do you connect Encharge to Make?

  1. 01

    Add an Encharge module

    In a new scenario, click the +, search for Encharge and pick any module, for example Watch New User. Make then asks for a connection: your Encharge account linked to Make once, and reused by every Encharge module after that.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps when several Encharge accounts sit in the same Make team. Then follow what Make asks: either an authorization page from Encharge, or a key that Encharge gives you to paste.

  3. 03

    Save and check

    Click Save. If the connection works, the module opens its settings and you can fill them. From then on, every Encharge module in any scenario offers this same connection in its list, so you only do this once.

First scenario

Build your first scenario with Encharge

GoalWhen a lead signs up in another app, Make creates the person in Encharge and tags them.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your leads arrive first, such as your form tool, and choose its trigger.

  2. 02

    Add Create a Person

    Click the + on the right of that first module, search Encharge and choose Create a Person. Select your connection, then map the lead's details from the form module into the Encharge fields.

  3. 03

    Tag the new person

    Add Add Tags to a User after it. Map the person from the previous module and type the tag your Encharge flow listens to. Each lead travels as one bundle, meaning one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry in your form. Open the bubbles on each module to read the bundle it received, and check in Encharge that the person exists with the tag.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run counts as one operation, the unit Make uses to measure your plan.

Triggers

What can start an Encharge scenario?

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

Encharge1Watch New User

Watch New User

Instant trigger

In Make“Triggers when a person is created in Encharge.”

This trigger starts your scenario each time a new person is created in your Encharge account, so a fresh subscriber reaches your other tools without any export. Each person arrives as one bundle your next modules can read.

How it fires
instant. Encharge calls Make through a webhook as soon as the person is created.
When to use it
copying every new subscriber into your CRM, or pinging sales in a chat channel when a contact joins.
Watch out
edits to an existing person belong to Watch User Updated, so pick the trigger that matches the moment you care about.
Encharge2Watch User Tagged

Watch User Tagged

Instant trigger

In Make“Triggers when a person is tagged with the entered tag.”

A tag you apply in Encharge turns into a signal the rest of your stack can act on. You enter the tag to follow, and the scenario runs each time a person receives it.

How it fires
instant. Encharge sends the event to Make through a webhook as soon as the tag lands on the person.
When to use it
a demo-request tag that should open a deal in your CRM or alert the account owner.
Watch out
the trigger follows the tag you entered, so type it exactly as it is written in Encharge before your first Run once.
Encharge3Watch User Unsubscribed

Watch User Unsubscribed

Instant trigger

In Make“Triggers when a person has unsubscribed from receiving emails in Encharge.”

You get told the moment someone opts out of your Encharge emails, which lets you respect that choice in every other tool, not just in Encharge itself.

How it fires
instant. The unsubscribe reaches Make through a webhook as soon as it happens in Encharge.
When to use it
flagging the contact in your CRM, or taking them off an audience you run in another marketing app.
Watch out
this module only listens. To unsubscribe someone from inside a scenario, the matching move is the Unsubscribe a Person action further down this page.
Encharge4Watch User Untagged

Watch User Untagged

Instant trigger

In Make“Triggers when a person is untagged with the entered tag.”

Removing a tag in Encharge can now clean up after itself elsewhere. You enter the tag to follow, and the scenario runs whenever a person loses it.

How it fires
instant. Encharge warns Make through a webhook as soon as the tag is taken off.
When to use it
a trial tag that disappears when someone converts, which should update their status in your billing sheet or CRM.
Watch out
it pairs naturally with Watch User Tagged on the same tag; keep the two scenarios apart so each one does a single job you can debug.
Encharge5Watch User Updated

Watch User Updated

Instant trigger

In Make“Triggers when a person is updated in Encharge.”

Any change to a person in Encharge can be copied to your other tools, which keeps a contact's details in sync without retyping them.

How it fires
instant. Encharge calls Make through a webhook as soon as the person is updated.
When to use it
a customer changes company or email in Encharge and your CRM record should follow.
Watch out
if the same scenario ends with Update a Person on that Encharge account, the update can fire this trigger again; send the change to another app instead, or filter out the edits your scenario makes.
Modules

What can Make do in Encharge?

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

Encharge1

Add Tags to a User

Action

In Make“Adds tags to an existing user.”

Puts one or more tags on a person who already exists in Encharge, which is usually how you drop a contact into the right segment or flow.

When to use it
right after a purchase, a form entry or a CRM stage change that should change what emails someone receives.
Watch out
the person must exist first; for a brand new lead, place Create a Person before it.
Encharge2

Create a Person

Action

In Make“Creates a new person.”

Adds a new contact to your Encharge account from data another app hands over, so nobody has to import a file by hand.

When to use it
a webinar signup, a checkout or a lead form in another tool that should feed your Encharge list directly.
Watch out
map every detail you want to segment on later, since tags and flows can only use what reached Encharge.
Encharge3

Delete a Person

Action

In Make“Deletes the selected person.”

Removes the selected person from Encharge entirely, which helps when a deletion request has to reach every tool at once.

When to use it
a data removal request logged in your help desk or CRM that must be carried out in Encharge too.
Watch out
treat it as final; run it only after a filter that confirms you picked the right person, and prefer Unsubscribe a Person when the goal is just to stop emails.
Encharge4

Get a Person

Action

In Make“Returns information about the selected person.”

Reads what Encharge knows about one person and hands it to the next modules, so a scenario can decide based on the contact's current record.

When to use it
before updating your CRM, to pull the latest Encharge details of the contact your trigger just received.
Watch out
it returns a single selected person, so you need to know which one you want before this step.
Encharge5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Encharge API through the connection you already set up, which covers anything the 7 other actions leave out.

When to use it
you need an Encharge endpoint that no listed module offers, and you have the API reference open next to you.
Watch out
this is the one technical module here; you write the path and body yourself, so test it with Run once before switching the scenario on.
Encharge6

Remove Tags from a User

Action

In Make“Removes tags from an existing user.”

Takes one or more tags off an existing person, which moves them out of a segment or stops a flow tied to that tag.

When to use it
a trial ends, a deal closes or a ticket is solved, and the tag that described the old situation no longer fits.
Watch out
a scenario started by Watch User Untagged on the same tag will react to this change too.
Encharge7

Unsubscribe a Person

Action

In Make“Unsubscribes a person to prevent from receiving any more emails.”

Stops Encharge from sending any more emails to the selected person. Unlike Delete a Person, it does not remove the contact.

When to use it
an opt-out collected somewhere else, such as a CRM field or a support request, that Encharge must honor as well.
Watch out
this action can fire Watch User Unsubscribed; if that trigger feeds a scenario that unsubscribes people elsewhere, check the two do not bounce the same contact back and forth.
Encharge8

Update a Person

Action

In Make“Updates a person.”

Changes the details of a person already in Encharge, so your emails use the latest name, company or other data from your source tool.

When to use it
your CRM holds the reference record and every edit there should reach Encharge.
Watch out
placed after Watch User Updated on the same account, it can start that trigger again; use it in scenarios that start from another app.
Need help

Need help automating Encharge with Make?

A person reads every message.

FAQ

Questions about the Encharge Make integration

01Is the Encharge Make integration free?
Yes, Encharge is a standard app in Make, so its modules are available on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run. Your Encharge subscription is separate and not covered here.
02What do you need to connect Encharge to Make?
An Encharge account and a Make account. Make's documentation lists no specific prerequisite for Encharge and gives no dedicated connection steps, so the generic flow applies: add an Encharge module, click Create a connection, optionally name it, authorize Make on the page Encharge shows or paste the key Encharge gives you, then click Save. The connection is then reused by every Encharge module in your scenarios, so you set it up once.
03Do Encharge triggers in Make fire instantly?
Yes. All 5 Encharge triggers are instant: Encharge calls Make through a webhook as soon as the event happens, whether a person is created, updated, tagged, untagged or unsubscribed. You do not wait for a polling interval, which is how scheduled triggers work in other apps. In the editor, these modules carry the lightning badge rather than the clock. Scenarios that start from another app, like the first scenario on this page, still follow the schedule you set, every 15 minutes by default.
04What if an Encharge module is missing in Make?
Use Make an API Call. It sends any request to the Encharge API with the connection you already created, so you can reach endpoints that the 8 listed actions do not cover. It does ask you to read the Encharge API reference and write the request yourself. Keep in mind that Make marks its own Encharge documentation as limited, so for unusual cases the Encharge side is the better source of detail.
05Make or n8n for Encharge?
It depends on where the rest of your automations already live. On Make, Encharge comes with 13 modules: 5 instant triggers and 8 actions on people and tags, including Make an API Call for anything else, all available from the Free plan. If your team already runs its workflows in n8n, check whether an Encharge node exists there before moving anything. Neither tool is ranked here; the n8n vs Make comparison on this site lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations