Resources · Make integration

ConvertBox Make integrationAutomate ConvertBox with Make.

What happens to a lead after it fills in your ConvertBox form? The ConvertBox Make integration gives you 1 instant trigger that hands each submission to Make. This page shows marketers how to connect the account and build a first scenario around it.

Try the ConvertBox integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ConvertBox Make integration do for you?

The ConvertBox Make integration listens for form submissions in ConvertBox and passes each one to Make, the tool where you build a scenario (the automation itself, a chain of modules). Every other step of that scenario belongs to another app: ConvertBox starts the flow, the rest of your stack does the work.

Leads that land in your CRM on their own. Put Watch Form Submitted first, then add the module of your CRM that creates a contact. Each submission becomes a bundle, meaning one item that flows from module to module, and the CRM receives it without anyone copying a line.

A sales team that hears about hot leads at once. The same trigger can feed a chat or messaging app. If your team works in WhatsApp, the 2Chat Make integration shows what that side offers.

A list you can actually trust. Send submissions to a spreadsheet or a mailing tool and keep one clean record of who signed up from which offer.

Keep the scope in mind: ConvertBox has a single module in Make, and Make says its own documentation for this app is limited for lack of public information. Anything beyond receiving a submission happens in other apps. The same app may also exist in n8n; the n8n vs Make comparison helps you pick, and the Make training covers the editor from zero.

Connect

How do you connect ConvertBox to Make?

  1. 01

    Add the ConvertBox module

    In your scenario, click the +, search for ConvertBox and pick Watch Form Submitted. Then click Create a connection: a connection is your ConvertBox account linked to Make once and reused by every ConvertBox module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you run several ConvertBox accounts, which is optional. Then follow what the window asks: either authorize Make on the ConvertBox page, or paste the key ConvertBox gives you.

  3. 03

    Save and check the result

    Click Save. The connection now appears in the module, and every future ConvertBox module in any of your scenarios can reuse it without asking for your credentials again.

First scenario

Your first scenario with ConvertBox

GoalWhen a visitor submits a ConvertBox form, Make passes the answers to the next app of your choice.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas to place the first module.

  2. 02

    Place the ConvertBox trigger

    Search for ConvertBox, choose Watch Form Submitted and select the connection you created, or click Create a connection if this is your first ConvertBox module.

  3. 03

    Add the destination

    Click the + on the right of the trigger and pick the module of the app that should receive the lead. Then drag the answers ConvertBox sent into its fields: that is what Make calls mapping.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry on your ConvertBox form. Open the bubbles to read the bundle each module received and fix any mapping that looks wrong.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. From then on each new submission starts it, and each module run counts as one operation on your Make plan.

Triggers

What starts a ConvertBox scenario

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

ConvertBox1Watch Form Submitted

Watch Form Submitted

Instant trigger

In Make“Triggers when a form is submitted.”

Watch Form Submitted gets you every new ConvertBox form submission inside Make, ready to send to a CRM, a sheet or a message. It is the only ConvertBox module, so it always opens the scenario.

How it fires
instant. ConvertBox calls Make through a webhook as soon as the form is submitted, which is why the module carries a lightning badge instead of a clock.
When to use it
any time a lead captured by a ConvertBox offer has to reach another tool without a manual export.
Watch out
Make documents this app only briefly, so run a real test submission with Run once before you map anything.
Need help

Need help automating ConvertBox with Make?

A person reads every message.

FAQ

ConvertBox and Make: common questions

01Is the ConvertBox Make integration free?
Yes, on the Make side. ConvertBox is a standard app, so its trigger is available from the Free plan. That plan allows 2 active scenarios, runs of 5 minutes at most and files up to 5 MB. The 15 minute minimum interval applies to scheduled scenarios; an instant trigger like this one is called by ConvertBox instead. Paid plans (Core, Pro, Teams, Enterprise) lift the active scenario cap and count usage in credits per month. Your ConvertBox subscription is a separate matter this page does not cover.
02What do you need to connect ConvertBox to Make?
A ConvertBox account and a Make account. The Make documentation lists no other prerequisite for this app. You add Watch Form Submitted, click Create a connection, optionally name it, then either authorize Make on the ConvertBox page or paste the key ConvertBox provides, and click Save. Since Make describes its ConvertBox documentation as limited, follow the window you actually see if it differs from these generic steps. Once saved, the connection is reused by every ConvertBox module in your scenarios.
03Does the ConvertBox trigger in Make work in real time?
Yes. Watch Form Submitted is an instant trigger: ConvertBox calls Make through a webhook as soon as someone submits a form, rather than Make checking at an interval. In the editor you recognize it by the lightning badge on the module. That makes it a good fit when a lead should reach sales or a mailing list right away. Test it with Run once and a real submission first, because the bundle you receive is what every later module will work from.
04What if the ConvertBox module you need is missing in Make?
It depends on what you need. ConvertBox offers a single module in Make, Watch Form Submitted, and no Make an API Call module, so you cannot reach other parts of ConvertBox from here. Make also warns that its documentation for this app is limited. The practical route is to use ConvertBox only as the starting point and let other apps handle every following step. If your case needs more than a submission, the agency team can look at it with you.
05Should you use Make or n8n for ConvertBox?
It depends on your criteria. In Make, ConvertBox gives you one instant trigger, available on the Free plan, and every action happens in the other apps you add after it. Many apps also exist as n8n nodes, so check whether ConvertBox is one of them before choosing. Weigh the tool your team already knows, the apps the rest of the scenario needs and how each platform counts usage. The n8n vs Make comparison on this site lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations