Resources · Make integration

Basin Make integrationAutomate Basin with Make.

What happens to a form entry after Basin receives it? The Basin Make integration gives you 2 modules: an instant trigger for new submissions and a search that lists them. This page shows how to connect your form and build a first scenario that passes each entry along.

Try the Basin integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Basin Make integration do for your forms?

The Basin Make integration links a Basin form to Make, a visual tool where you build a scenario (the automation itself: a chain of modules, each one a brick from an app). Basin tells Make the moment a clean entry lands, and Make hands that entry to whatever app comes next in the chain.

Leads that reach sales on their own. A contact form on a landing page feeds Watch New Submissions. Each entry becomes a bundle (one item passed from module to module, here one submission) that the next module turns into a CRM record or a chat message for the person on call.

A clean backlog for a newly connected form. Your form collected entries before the scenario existed? List Submissions reads what a chosen form already holds, so a one-off run can copy that history into a sheet or a database.

Less noise in your inbox. Basin keeps entries it flags as spam away from the trigger. Only genuine submissions start the scenario, which also saves operations (one module run on one bundle, the unit Make counts on your plan).

What the integration does not offer: there are no action modules, so Make cannot edit, delete or flag a submission inside Basin, and there is no Make an API Call module for anything else. If you run a different form tool, the 123FormBuilder Make integration covers a similar need. Weighing tools first? The n8n vs Make comparison and the Make pricing guide help you decide.

Connect

How do you connect Basin to Make?

  1. 01

    Copy the key from your Basin form

    In Basin, open your form dashboard, go to the Integrations page of the form you want to automate and copy the API key shown there. You need an active Basin account for this key to exist.

  2. 02

    Add a Basin module in Make

    In your scenario, add a Basin module and click Create a connection. A connection is your Basin account linked to Make once, then reused by every Basin module. For the instant trigger, click Create a webhook first.

  3. 03

    Paste the key and save

    Give the connection a clear name in Connection name if you like (it is optional), then paste the API key you copied. The connection then appears in the module, ready to use.

First scenario

Build your first Basin scenario

GoalWhen another app starts the scenario, Make pulls the entries of your Basin form and hands them to the next app in the chain.

  1. 01

    Start a new scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Set what starts the run

    Pick the trigger of the app that should kick things off, such as a new row in the sheet your team fills in. Basin itself comes right after it.

  3. 03

    Add List Submissions

    Click the + on the right, search for Basin and choose List Submissions. Click Create a connection, paste the API key of your form and select that form.

  4. 04

    Test with Run once

    Click Run once and open the output of List Submissions. Each entry shows up as its own bundle, so you can check the answers before sending them anywhere.

  5. 05

    Add the destination and switch on

    Click the + after Basin, add the app that should store the entries and map the submission data into it. Then switch the scenario on.

Triggers

What starts a Basin scenario

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

Basin1Watch New Submissions

Watch New Submissions

Instant trigger

In Make“Triggers when a new submission is received. Only submissions that are not flagged as spam will trigger a webhook.”

You get every new entry of your Basin form pushed into Make as soon as it arrives, with the spam already left out. Basin only calls the webhook for submissions it has not flagged as spam, so the next modules work on real messages.

How it fires
instant. Basin calls Make through a webhook as soon as a submission comes in; there is no polling interval to set.
When to use it
a quote request or contact form whose answers should reach your CRM or your team chat while the visitor is still on your site.
Watch out
a webhook can only see what arrives after it was created, so older entries never fire it; use List Submissions to catch up on those.
Modules

What Basin can do in Make

Basin gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Basin1

List Submissions

Search

In Make“Lists all submissions for a selected form.”

This search hands you the submissions of the form you select, each one as its own bundle, so you can work on entries that already sit in Basin instead of waiting for new ones.

When to use it
right after connecting an older form, to copy its past answers into a spreadsheet before the instant trigger takes over.
Watch out
a search can return zero, one or many bundles, and every later module runs once per bundle, which adds operations on a busy form.
Need help

Need help automating Basin with Make?

A person reads every message.

FAQ

Basin and Make: common questions

01Is the Basin Make integration free?
Yes, on the Make side. Basin is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in operations each month. Your Basin subscription is separate: check the Basin pricing page for what your form plan includes.
02What do you need to connect Basin to Make?
An active Basin account and the API key of the form you want to automate. In Basin, open the form dashboard, go to that form's Integrations page and copy the key. In Make, add a Basin module, click Create a connection, optionally name it, and paste the key. For Watch New Submissions, click Create a webhook before creating the connection. The same connection is then reused by every Basin module in your scenarios.
03Does the Basin Make integration trigger in real time?
Yes. Watch New Submissions is an instant trigger: Basin calls Make through a webhook as soon as a submission arrives, instead of Make checking on a schedule. Two limits apply. Entries Basin flags as spam never call the webhook, and, logically, entries received before the webhook existed do not start the scenario. For those older entries, run List Submissions once and send the results where you need them. Keep that in mind when you first switch the scenario on.
04What if the Basin module you need is missing in Make?
It depends on what you need. The app has only 2 modules, a trigger and a search, and no Make an API Call module, so Make cannot change, delete or flag a submission in Basin. If your process needs that, handle it in Basin itself, pick a form tool whose Make app covers the step, or ask the team to look at your case. For reading and forwarding entries, the 2 modules are enough.
05Make or n8n for Basin forms?
It depends on your criteria rather than on a winner. On Make, Basin gives you an instant trigger for clean submissions and a search for older ones, built visually with a Run once test at each step. Before choosing, check whether n8n offers a node for Basin and which steps it covers, then compare the two on the modules you really need. Neither tool adds actions that Basin does not expose through its integration.
Same platform

Other docs you might need on this stack.

Browse all integrations