Resources · Make integration

Landingi Make integrationAutomate Landingi with Make.

Every form filled on a Landingi page can start an automation. The Landingi Make integration gives you 1 instant trigger, Watch Form Submitted. This guide is for marketers and founders who collect leads on landing pages: connect your account, build a first scenario and send each lead where your team works.

Try the Landingi integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Landingi Make integration do?

The Landingi Make integration links your landing pages to Make, a no-code tool where you build scenarios: automations made of modules, one brick per step. On the Landingi side there is a single module, a trigger that fires when a visitor submits a form on a landing page. Everything that happens next runs in the other apps you pick.

Leads in your CRM without copy and paste. Watch Form Submitted receives the submission and a module of your CRM creates the contact from it. The Agile CRM Make integration shows what such a CRM side looks like.

One shared table of every lead. Put an Airtable module after the same trigger and each submission becomes a new row that marketing and sales read together. The Airtable Make integration covers that half of the flow.

A quick reply to demo requests. Pass the form data to an email or chat app so a salesperson sees the request while the visitor still remembers filling it in.

What Make does not do for Landingi: there is no module to edit pages or read other Landingi data, and no Make an API Call module to fill the gap. Make also flags its Landingi documentation as limited, because little public information exists about the app. If you are weighing the two main no-code options, the n8n vs Make comparison sets out the criteria.

Connect

How do you connect Landingi to Make?

  1. 01

    Add the Landingi module

    Open your scenario, click the +, search for Landingi and pick Watch Form Submitted. In the module panel, click Create a connection. A connection is your Landingi account linked to Make once, then reused by every Landingi module.

  2. 02

    Name the connection

    Make offers a field to name the connection. It is optional, but a clear label, such as the brand or the client the pages belong to, saves guesswork when several Landingi accounts end up side by side in Make.

  3. 03

    Authorize Make and save

    Depending on what the window asks, approve Make on the Landingi page that opens, or paste the key Landingi gives you. Then click Save.

First scenario

Your first Landingi scenario, step by step

GoalWhen a visitor submits a form on a Landingi landing page, Make sends the lead to the app your team works in.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + in the editor. This first module starts everything, so it will be the Landingi trigger.

  2. 02

    Set the trigger

    Search for Landingi, choose Watch Form Submitted and select your connection. It is an instant trigger (the lightning badge): Landingi calls Make through a webhook the moment a form is sent.

  3. 03

    Add the app that gets the lead

    Click the + to the right of the trigger and add a module of the app that should receive the lead, a CRM or a table. Map the data the trigger received into its fields.

  4. 04

    Test with Run once

    Click Run once, then send a test form from your landing page. Each module shows the bundles it received, a bundle being one item passed along, here one submission.

  5. 05

    Switch the scenario on

    Once the test looks right, turn the scenario on. From then on, each form sent on the page runs it, and each module run counts as one operation on your Make plan.

Triggers

What starts a Landingi scenario

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

Landingi1Watch Form Submitted

Watch Form Submitted

Instant trigger

In Make“Triggers when a form is submitted on a landing page.”

Watch Form Submitted starts your scenario each time a visitor sends a form on one of your Landingi landing pages. The submission arrives as a bundle. The next modules read it and pass it on, so no lead sits forgotten in an inbox.

How it fires
instant, Landingi calls Make through a webhook as soon as the form is sent, with no polling interval to wait for.
When to use it
a demo request or quote form whose leads your sales team should find in their CRM without anyone exporting a file.
Watch out
it is the only Landingi module in Make, so reading or changing anything else in Landingi stays out of reach from a scenario.
Need help

Need help automating Landingi with Make?

A person reads every message.

FAQ

Landingi and Make: common questions

01Is the Landingi Make integration free?
Yes, Landingi is a standard app, available from the Make Free plan. That plan gives you 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Each module run on a bundle is one operation, and operations are what Make counts on your plan. The paid plans, Core, Pro, Teams and Enterprise, allow unlimited active scenarios and runs of up to 40 minutes. Your Landingi subscription is a separate matter and is not covered on this page.
02What do you need to connect Landingi to Make?
A Landingi account and a Make account are enough to start, since the Make documentation lists no other prerequisite for this app. In the module, click Create a connection, give it a name if you like, then approve Make on the Landingi page or paste the key Landingi provides, and click Save. The connection is stored once and reused by any Landingi module in your scenarios. If the window asks for something unexpected, keep in mind that Make describes its Landingi documentation as limited.
03Does the Landingi trigger in Make work in real time?
Yes. Watch Form Submitted is an instant trigger: Landingi calls Make through a webhook as soon as a visitor submits a form, so the scenario does not wait for a scheduled check. Scheduled triggers work differently, Make polls them at an interval, every 15 minutes by default on a new scenario. In the editor, the lightning badge on the module tells you it is instant. Outside a Run once test, the scenario has to be switched on for new submissions to be processed.
04What if the Landingi module you need is missing in Make?
Landingi has a single module in Make, Watch Form Submitted, and no Make an API Call module to go further. A scenario can therefore react to form submissions, but it cannot edit pages or read other Landingi data. The usual path is to let the trigger feed another app that has the modules you need, such as a CRM, a table or a mailing tool. If your case goes further than that, the help form on this page reaches the team.
05Make or n8n for Landingi?
It depends on the tool you already run and on your own criteria. On Make, Landingi comes with one instant trigger for form submissions, it is a standard app open from the Free plan, and the connection is set once in the editor. n8n often has a node for the same apps, so check its catalog for Landingi before you decide. Then compare how each tool counts usage, which of your other apps each one covers, and which editor your team will maintain more easily.
Same platform

Other docs you might need on this stack.

Browse all integrations