Resources · Make integration

involve.me Make integrationAutomate involve.me with Make.

What happens to a lead once they reach your thank you page? The involve.me Make integration offers 1 instant trigger that hands each finished submission to Make. This page shows how to connect your account and build your first scenario around it.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the involve.me Make integration do for you?

The integration lets Make start an automation the moment someone completes one of your involve.me projects. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, like a trigger or an action. involve.me brings the first brick, and other apps supply the rest.

A lead lands in your CRM without copy and paste. Watch Participant Finished fires when a participant reaches the thank you page or outcome page. The next module, from your CRM or a spreadsheet app, receives the answers. Each item passing between modules is a bundle, here one submission.

Sales hears about hot quiz results. A consultant who runs an assessment quiz can route each completed quiz to a chat or email module, so nobody has to refresh the involve.me dashboard.

Calculator results feed a follow-up. A price calculator that ends on an outcome page can hand its data to an email tool, which writes back to the prospect with the right offer. See the Airtable Make integration if you want a table as the destination.

Know the limits before you plan. Make lists a single module for involve.me, and it only watches finished submissions: no action writes to involve.me, no search reads your projects. Make also flags the app's documentation as limited. A visitor who quits halfway through starts nothing.

Weighing tools? The n8n vs Make comparison sets out how each one works, and the Make training covers scenario building step by step.

Connect

How do you connect involve.me to Make?

  1. 01

    Add the involve.me module

    In a new scenario, click the + and search for involve.me. Pick Watch Participant Finished, then click Create a connection. A connection is your involve.me account linked to Make once, then reused.

  2. 02

    Name the connection

    Giving it a name is optional, but it helps later. If your team runs several involve.me workspaces, a clear name like the brand or the client stops you from picking the wrong account in the next scenario.

  3. 03

    Authorize and save

    Make then asks you either to approve access on an involve.me page or to paste the key the app gives you. Complete that step and click Save. The module now lists what it can read from your account.

First scenario

Build your first scenario with involve.me

GoalWhen a participant finishes an involve.me project, Make passes their answers to the app where you track leads.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. Click the + in the middle of the canvas to add the first module.

  2. 02

    Place the trigger

    Search for involve.me and choose Watch Participant Finished. Select your connection, or create it now with Create a connection, then fill in the fields Make shows you.

  3. 03

    Add the destination

    Click the + on the right of the trigger and add a module from the app that should receive the lead. Map the submission data from the involve.me module into its fields.

  4. 04

    Test with Run once

    Click Run once, then finish your project in involve.me as a participant would, up to the last page. Open each module to read the bundle it received.

  5. 05

    Switch it on

    Once the test bundle looks right, switch the scenario on. Because the trigger is instant, involve.me calls Make as each new submission comes in, with no polling clock to set.

Triggers

What starts an involve.me scenario?

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

involve.me1Watch Participant Finished

Watch Participant Finished

Instant trigger

In MakeTriggers when your project has a new submission, meaning that your user reached the last page (thank you page or outcome page).

Every time a participant gets to the end of one of your projects, this trigger hands their submission to Make, ready for the next module. Visitors who leave before the thank you page or outcome page do not count.

How it fires
instant, meaning involve.me calls Make through a webhook as soon as the submission is complete.
When to use it
a lead form, quiz or calculator whose completed answers should reach your CRM, inbox or sheet without anyone exporting them.
Watch out
partial answers never arrive, so plan another route if you care about drop-offs.
Need help

Need help automating involve.me with Make?

A person reads every message.

FAQ

involve.me and Make: common questions

01Is the involve.me Make integration free?
Yes, involve.me is a standard app in Make, so it works from the Free plan. That plan gives you 2 active scenarios, a 15 minute minimum between scheduled runs, runs of up to 5 minutes, 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 minute runs. Usage is counted in operations, one operation being one module handling one bundle. Your involve.me subscription is a separate matter, which this page does not cover.
02What do you need to connect involve.me to Make?
An involve.me account and a Make account. Make's documentation lists no specific prerequisite for this app. The connection follows Make's usual steps: add the Watch Participant Finished module, click Create a connection, optionally name it, then either approve access on the involve.me page or paste the key the app provides, and click Save. Make points out that its involve.me documentation is limited, so follow what the connection screen actually asks. The connection is saved once and every later involve.me scenario reuses it.
03Does the involve.me trigger in Make fire in real time?
Yes. Watch Participant Finished is an instant trigger: involve.me calls Make through a webhook as soon as a participant reaches the last page of a project, whether that is a thank you page or an outcome page. There is no polling interval to set, unlike a scheduled trigger that Make checks on a clock. The trigger only reacts to finished submissions. A visitor who stops partway through a funnel never starts the scenario, so those drop-offs stay inside involve.me.
04What if the involve.me module you need is missing in Make?
It depends on what you need. Make offers a single involve.me module, the Watch Participant Finished trigger, and no Make an API Call module for this app. That means Make cannot write to involve.me or read your projects on demand. The usual workaround is to let the trigger start the flow and do the rest of the work in other apps, like a CRM or a spreadsheet. If your case goes further than that, the team can look at it with you through the contact form on this page.
05Should you use Make or n8n for involve.me?
It depends on your criteria, not on a winner. On Make, involve.me gives you one instant trigger for finished submissions, available from the Free plan, with a guided editor and a Run once test button. Before choosing n8n, check whether it offers an involve.me node and what that node covers compared with the trigger described here. Then weigh the rest of your stack: the tool that already runs your other automations is often the simpler place to add this one. The comparison page linked above sets out how the two tools differ.