Resources · Make integration

Instasent Make integrationAutomate Instasent with Make.

Keep your Instasent contacts in step with the rest of your tools, without writing code. The Instasent Make integration gives you 7 action modules to add, read and remove contacts, log events and pull stats. This page walks you through the connection and a first working scenario.

Try the Instasent integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Instasent Make integration do for you?

The Instasent Make integration links your Instasent account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick that does one job. Instasent brings 7 modules, all actions, so another app or a schedule starts the scenario and Instasent carries out the work.

New leads land in Instasent on their own. Someone fills in a form in another app, and Add a Contact creates the matching record in Instasent. Chain Add an Event right after it to note what that person just did, so the history sits next to the contact.

A cleanup when a customer leaves. When a customer asks to be forgotten in your CRM, Delete a Contact removes them from Instasent too, so nobody has to remember the second tool.

Numbers in the report, not in a browser tab. Get a Data Source's Stats and Get a Project's Detail read figures from your account, which you can then send on to a sheet or a message in the next module.

What Make cannot promise here: its own documentation for Instasent is marked as limited, and the app has no trigger and no Make an API Call module. If a need falls outside these 7 modules, the Make troubleshooting guide and the Make agency team can help. Weighing tools first? The n8n vs Make comparison sets out the criteria.

Connect

How do you connect Instasent to Make?

  1. 01

    Add an Instasent module

    In your scenario, click the +, type Instasent in the search box and pick any of its modules, for example Add a Contact. The connection you create here is saved once and reused by every other Instasent module.

  2. 02

    Create the connection

    Click Create a connection. Give it a clear name if you like, such as the name of the Instasent project it points to, which helps once you run several accounts side by side.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the Instasent page, or paste the key that Instasent gives you. Then click Save, and Make can start listing what your account holds.

First scenario

Build your first scenario with Instasent

GoalWhen a form is submitted in another app, Make adds the person to Instasent and records an event on their contact.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since Instasent has no trigger, the first module comes from the app that collects your leads, such as your form tool.

  2. 02

    Add Add a Contact

    Click the + to the right of that first module, search Instasent, pick Add a Contact and select your connection. Map the details coming from the form into the fields Make shows for the contact.

  3. 03

    Chain Add an Event

    Add one more module with the +: Add an Event. Map the contact from the step before, so every new lead also gets an entry that says where it came from.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry in your form. Each module shows the bundles it received, a bundle being one item, here one person, passed from module to module.

  5. 05

    Schedule and switch on

    On the first module, open the clock to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What each Instasent module does

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

Instasent1

Add a Contact

ActionIn the docs only

Your new people show up in Instasent without anyone typing them in: this module creates a contact from the data an earlier module passes along.

When to use it
right after a sign-up or a purchase in another app.
Watch out
Make's doc lists no fields for it, so click Run once on a test entry and check what lands in Instasent.
Instasent2

Add an Event

ActionIn the docs only

A contact's history grows by itself when you place this module after the step where something happens, since it logs an event in Instasent.

When to use it
when an order ships, a ticket closes or a lead downloads a guide, and you want Instasent to know about it.
Watch out
the documentation is limited on what an event holds, so test it once and look at the result in Instasent before relying on it.
Instasent3

Delete a Contact

ActionIn the docs only

Removing someone from Instasent stops depending on a person remembering to do it: the scenario deletes the contact for you.

When to use it
when a customer closes their account or asks to be erased from your CRM, so both tools stay aligned.
Watch out
a deletion cannot be rolled back from Make, so test it on a dummy contact first and check which contact the earlier module passes in.
Instasent4

Get a Contact

ActionIn the docs only

With this module, the details Instasent keeps on one contact become available to the modules that follow, ready to map into another app.

When to use it
before updating a record elsewhere, or to copy what Instasent knows into a sheet or a support ticket.
Watch out
Make's doc does not explain how it differs from Get an Audience Contact, so compare the output of both with Run once.
Instasent5

Get a Data Source's Stats

ActionIn the docs only

You get the statistics of one Instasent data source as a bundle, which means the figures can travel to a report without a manual export.

When to use it
to feed a dashboard sheet or a team message after a campaign ends or a list is imported.
Watch out
the doc does not say which figures come back, so read the bundle after Run once before mapping anything.
Instasent6

Get a Project's Detail

ActionIn the docs only

Going by its name, since Make gives no description, the module reads the details of an Instasent project. Later steps can then reuse them instead of hard-coded values.

When to use it
when a scenario serves several projects and needs to know which one it is working on before it writes anything.
Watch out
nothing in the documentation lists the returned details, so inspect the output of a test run first.
Instasent7

Get an Audience Contact

ActionIn the docs only

Its name suggests it fetches a contact as it appears in an Instasent audience. Handy when your scenario works on a segment rather than on the whole contact list.

When to use it
when a later module needs the audience view of a person, for example to decide where to send them next.
Watch out
since Make's doc is limited, check with Run once whether it returns what Get a Contact already gives you.
Need help

Need help automating Instasent with Make?

A person reads every message.

FAQ

Instasent and Make: common questions

01Is the Instasent Make integration free?
Yes, Instasent is a standard app in Make, so it works on the Free plan. That plan lets you keep 2 scenarios active, with at least 15 minutes between two scheduled runs, up to 5 minutes per run 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 per run. Usage is counted in credits, which are operations: one module running on one item. Your Instasent subscription is a separate matter that this page does not cover.
02What do you need to connect Instasent to Make?
An Instasent account and a Make account. Make's documentation for Instasent lists no special prerequisite and is marked as limited, so the connection follows the usual Make path: add an Instasent module, click Create a connection, give it a name if you want, then either approve Make on the Instasent page or paste the key Instasent provides, and click Save. The connection is saved once and every Instasent module in your scenarios reuses it, so you do this step a single time per account.
03Can Instasent start a Make scenario in real time?
No, not by itself. Instasent has no trigger module in Make, only 7 actions, so something else has to start the scenario. You have two options. Put another app's trigger first, for example a form or a store, and let Instasent modules follow it. Or set a schedule on the first module, every 15 minutes by default, and at least every 15 minutes on the Free plan. Whether the start is instant then depends on the trigger of that other app, not on Instasent.
04What if an Instasent module is missing in Make?
It depends on what is missing. The Instasent app in Make has 7 modules and no Make an API Call module, so you cannot send a custom request to Instasent from inside the app. Make's own documentation is also marked as limited. Check first whether one of the 7 modules covers the need once you test it with Run once. If it does not, the work has to pass through another app that Make supports, or through a custom build, which the Hack'celeration team can scope with you.
05Make or n8n for Instasent?
It depends on the criteria that matter to you. On the Make side, Instasent brings 7 action modules, no trigger and no Make an API Call module, and runs on every plan including Free. The same app often has an n8n node too, but this page does not compare what each node covers, how fast it runs or what it costs. The fair test is practical: list the actions your scenario needs, check them against the 7 modules above, and see which editor your team is more at ease building in.
Same platform

Other docs you might need on this stack.

Browse all integrations