Resources · Make integration

ActiveDEMAND Make integrationAutomate ActiveDEMAND with Make.

The ActiveDEMAND Make integration turns contact changes into follow-ups that run on their own. Make offers 12 ActiveDEMAND modules, 3 of them triggers. This guide is for marketers who run ActiveDEMAND, and it walks you through the connection and a first scenario.

Try the ActiveDEMAND integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ActiveDEMAND Make integration automate?

The ActiveDEMAND Make integration links your ActiveDEMAND account to Make, a tool where you build automations without code. Make watches ActiveDEMAND for new contacts, edited contacts and new history entries, then passes them on to other apps. It also works the other way: create, update, look up or forget contacts in ActiveDEMAND when something happens elsewhere.

New leads shared with sales. Watch New Contacts picks up each person added in ActiveDEMAND and can pass them to a team chat or a spreadsheet, so sales hears about a lead without logging in.

One clean record per person. When someone signs up in another tool, Search Contacts checks ActiveDEMAND first. Create a Contact or Update a Contact then writes the result, and duplicates stop piling up.

Outside activity kept in ActiveDEMAND. A payment or a support ticket handled in another app can become an entry through Create a History, and List Histories pulls past entries back out when you need a report.

What Make does not do here: none of the three triggers is instant, so changes arrive on the scenario's schedule rather than the moment they happen, and the Make doc gives no description for any module. Whatever the modules skip goes through Make an API Call. Weighing your options? The n8n vs Make comparison lays out the criteria, Make pricing details the plans, and Make training takes you past a first scenario.

Connect

How do you connect ActiveDEMAND to Make?

  1. 01

    Get your vendor token and API key

    ActiveDEMAND asks for a step on its side first: apply to the ActiveDEMAND Developer Partner Program and get approved, which gives you an API vendor token. Then open Settings, go to API Integration or API Keys, and copy the key shown.

  2. 02

    Add a module and create the connection

    In a Make scenario, add any ActiveDEMAND module and click Create a connection. A connection is your ActiveDEMAND account linked to Make once, then reused by every ActiveDEMAND module. Filling in Connection name is optional.

  3. 03

    Paste your credentials

    Paste the credentials you copied from ActiveDEMAND, or follow the instructions Make shows on screen, then save. The connection now appears in the module, and Make can list what it reads from your account.

First scenario

Your first scenario: turn each webinar sign-up into a contact with its history

GoalWhen someone registers in your webinar tool, Make creates the contact in ActiveDEMAND and logs a history entry for that sign-up.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario. A scenario is the automation you build, a chain of modules. Click the + in the middle of the canvas to place the first one.

  2. 02

    Start from your webinar tool

    Search for the app where people register and pick its trigger for new sign-ups. A module is one brick of the scenario; this first one starts it, and each registrant arrives as a bundle.

  3. 03

    Add Create a Contact

    Click the + to the right and pick the ActiveDEMAND module Create a Contact. Click Create a connection or select yours, then map the registrant's details into the fields Make lists.

  4. 04

    Log the sign-up with Create a History

    Add Create a History after it and point it to the contact you just created. The entry keeps a trace of the webinar in ActiveDEMAND, so marketing sees where the lead came from.

  5. 05

    Test, schedule, switch on

    Click Run once with a test registration and check the contact in ActiveDEMAND. Then set the clock on the first module (every 15 minutes by default) and switch the scenario on.

Triggers

What can start an ActiveDEMAND scenario?

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

ActiveDEMAND1Watch New Contacts

Watch New Contacts

triggerIn the docs only

Every contact added to ActiveDEMAND since the previous check reaches your scenario, each one as its own bundle, meaning one item handed to the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so nothing moves the second a contact signs up.
When to use it
when a fresh lead should land in another tool, such as a CRM, a shared sheet or a team chat, without anyone copying it over by hand.
ActiveDEMAND2Watch New Histories

Watch New Histories

triggerIn the docs only

You get each history entry recorded in ActiveDEMAND since the last run, so what gets logged there can travel to the tools your team actually reads.

How it fires
scheduled. Make polls ActiveDEMAND on the scenario's clock, shown as the clock badge on the module, and collects what was added in between.
When to use it
when a sales rep needs to hear about new entries on a lead without opening ActiveDEMAND.
Watch out
the Make doc gives no description of this module, so click Run once and read a bundle before you map anything.
ActiveDEMAND3Watch Updated Contacts

Watch Updated Contacts

triggerIn the docs only

Contacts edited after they were created are what this trigger hands you: each changed record reaches the scenario as a separate bundle.

How it fires
scheduled. Make asks ActiveDEMAND for changes at the interval set on the scenario, 15 minutes at the shortest on the Free plan and down to 1 minute on paid plans.
When to use it
when a copy of your contacts lives in another tool and has to stay in line with ActiveDEMAND.
Watch out
if the same scenario runs Update a Contact on those records, it can wake itself up again; send the write to another app instead.
Modules

What can Make do in ActiveDEMAND?

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

ActiveDEMAND1

Create a Contact

ActionIn the docs only

A person who signs up somewhere else ends up in your ActiveDEMAND base with Create a Contact, with no manual import to run.

When to use it
after a registration in another tool, such as a webinar platform or a checkout page, placed right behind that tool's trigger.
Watch out
put Search Contacts in front when the person may already exist, or you risk two records for the same lead.
ActiveDEMAND2

Create a Form Submit

ActionIn the docs only

A form filled outside ActiveDEMAND can still be recorded there: going by its name, Create a Form Submit sends that submission from your scenario.

When to use it
when leads come from a form hosted by another app and ActiveDEMAND should hold the entry too.
Watch out
the Make doc gives no detail on this module, so test it with Run once on a dummy entry and check what ActiveDEMAND shows before going live.
ActiveDEMAND3

Create a History

ActionIn the docs only

Create a History leaves a trace in ActiveDEMAND of something that happened in another tool, as a new history entry.

When to use it
when a call, a payment or a ticket handled elsewhere should show up in ActiveDEMAND for the marketing team.
Watch out
every run adds an entry, so a trigger that fires twice on the same event leaves two of them; filter before this module if that matters.
ActiveDEMAND4

Forget a Contact

ActionIn the docs only

Removal requests reach ActiveDEMAND without manual cleanup: Forget a Contact is the module to pick when a person asks to be forgotten, though the Make doc does not say exactly what it erases.

When to use it
when that request comes in through a form or a support tool and has to be applied in ActiveDEMAND as well.
Watch out
treat it like a delete that may not be undone; try it on a test contact first and put a filter before it.
ActiveDEMAND5

Get a Contact

ActionIn the docs only

With Get a Contact, the following modules receive the full record of one ActiveDEMAND contact, ready to copy into another tool.

When to use it
when an earlier module points to a single contact and you need the whole record before writing to another app.
Watch out
if you only have a partial clue and might get several matches, Search Contacts is the better fit.
ActiveDEMAND6

List Histories

SearchIn the docs only

Past history entries come out of ActiveDEMAND in one go with List Histories, each one becoming its own bundle for the modules that follow.

When to use it
for a report or an export of entries already recorded, rather than waiting for new ones with Watch New Histories.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which adds up in operations on your plan.
ActiveDEMAND7

Make an API Call

ActionIn the docs only

Any endpoint of the ActiveDEMAND API becomes reachable from your scenario with Make an API Call, using the connection you already set up.

When to use it
when you need an ActiveDEMAND feature that none of the other eleven modules offers.
Watch out
you write the request yourself from the ActiveDEMAND API reference, which asks more of you than the ready-made modules do.
ActiveDEMAND8

Search Contacts

SearchIn the docs only

Search Contacts tells you whether a person is already in ActiveDEMAND, returning zero, one or several matching contacts as bundles.

When to use it
right before Create a Contact, so a sign-up coming from another tool does not create a duplicate.
Watch out
plan what the scenario does when nothing matches, otherwise new people never get created.
ActiveDEMAND9

Update a Contact

ActionIn the docs only

Update a Contact keeps an existing ActiveDEMAND record current with fresh data from another tool, so nobody has to retype it.

When to use it
when a customer's details change in your billing or support tool and ActiveDEMAND should follow.
Watch out
avoid pairing it with Watch Updated Contacts in the same scenario, or each update can start a new run.
Need help

Need help automating ActiveDEMAND with Make?

A person reads every message.

FAQ

ActiveDEMAND and Make: common questions

01Is the ActiveDEMAND Make integration free?
Yes, on the Make side. ActiveDEMAND is a standard app, so its modules work on the Free plan. That plan allows 2 active scenarios, runs spaced at least 15 minutes apart, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits, that is operations: one module run on one bundle. Your ActiveDEMAND subscription is a separate matter, covered on ActiveDEMAND's own pricing page.
02What do you need to connect ActiveDEMAND to Make?
Approval in the ActiveDEMAND Developer Partner Program, before anything else. The Make doc asks you to apply to that program and be accepted, which gives you an API vendor token, and to have an ActiveDEMAND account. You then copy the API key from Settings, under API Integration or API Keys, click Create a connection in any ActiveDEMAND module and paste your credentials. The connection is made once, and every ActiveDEMAND module in your scenarios reuses it.
03Does the ActiveDEMAND trigger in Make work in real time?
No. The three ActiveDEMAND triggers, Watch New Contacts, Watch New Histories and Watch Updated Contacts, are scheduled (a type read from their names, since the Make doc lists them without detail): Make asks ActiveDEMAND for news on the scenario's schedule, every 15 minutes by default. This app has no instant trigger, so there is no webhook through which ActiveDEMAND would call Make the moment something happens. On a paid plan the interval can drop to 1 minute; on the Free plan, 15 minutes is the floor. Keep that in mind before promising anyone an instant alert.
04What if an ActiveDEMAND module is missing in Make?
Use Make an API Call. It lets the scenario call any endpoint of the ActiveDEMAND API through the same connection, which covers what the listed modules skip. You write the request yourself, so the ActiveDEMAND API reference becomes your guide. Note also that the Make doc for this app warns it was generated with AI from ActiveDEMAND's documentation and may contain mistakes: when a module behaves oddly, check with ActiveDEMAND directly and test with Run once before relying on it.
05Should you use Make or n8n for ActiveDEMAND?
It depends on where the rest of your automations live. On Make, ActiveDEMAND comes with 12 modules: 3 scheduled triggers, 7 actions (Make an API Call among them) and 2 searches, all available on the Free plan. Many apps also have an n8n node, so check whether one exists for ActiveDEMAND and whether it covers the same contacts and histories. Start from the tool your team already maintains, then compare the two on the exact actions your scenario needs.
Same platform

Other docs you might need on this stack.

Browse all integrations