Resources · Make integration

HappyForms Make integrationAutomate HappyForms with Make.

Can a HappyForms submission set work in motion on its own? The HappyForms Make integration offers 2 modules: an instant trigger and an API call action. This page takes you from the connection to a first scenario that runs by itself.

Try the HappyForms integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HappyForms Make integration do for you?

The HappyForms Make integration links your HappyForms account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick. Here you get two: a trigger that fires when someone submits a form, and an action that calls the HappyForms API with the same account.

No more copying answers by hand. For a small agency with a contact form, New Activity hands every successful submission to Make, and the next module (from another app you already use) files it where your team reads it.

A follow-up that starts with the form. A training company can chain a module of its mailing or CRM tool right after New Activity, so the person who filled in the form hears back without anyone watching the inbox.

Reach beyond the listed modules. Make an API Call talks to any endpoint of the HappyForms API with the connection you already set up. It is the way to cover what New Activity does not.

One honest limit: Make says its own documentation for HappyForms is incomplete, because too little public information exists about the app. So the page stays on what Make confirms, and Run once is your best guide to the data a submission really carries. If a scenario misbehaves, Make troubleshooting walks through the usual causes.

New to the editor? Make training covers the basics step by step. Weighing another tool too? The n8n vs Make comparison sets out how the two differ.

Connect

How do you connect HappyForms to Make?

  1. 01

    Add a HappyForms module

    In a scenario, click the +, search for HappyForms and pick a module, New Activity for example. Then click Create a connection. A connection is your HappyForms account linked to Make once and reused by both modules.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later; this is optional. Then do what HappyForms asks: either approve Make on the HappyForms authorization page, or paste the key HappyForms gives you.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and the next HappyForms module you add can pick it from the list instead of asking you again.

First scenario

Your first scenario with HappyForms

GoalWhen someone submits a HappyForms form, Make receives the answers and calls the HappyForms API endpoint you choose.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. That empty circle is where your first module goes.

  2. 02

    Place New Activity first

    Search for HappyForms, choose New Activity and select the connection you saved. Fill in the fields Make shows; this module is instant, so it waits for a real submission.

  3. 03

    Add Make an API Call

    Click the + on the right of New Activity and pick Make an API Call. Keep the same connection, then map the answers that New Activity passes along into the call.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry in your form. Each module shows the bundles it received: a bundle is one item passing from a module to the next, here one submission.

  5. 05

    Switch it on

    Once the test looks right, switch the scenario on. From then on, every successful submission starts it without you opening Make.

Triggers

What starts a HappyForms scenario?

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

HappyForms1New Activity

New Activity

Instant trigger

In Make“Triggers after a successful submission.”

New Activity puts your scenario to work the moment someone completes one of your HappyForms forms, and hands Make that submission as a bundle. Only a successful submission counts, which keeps your flow tied to real answers.

How it fires
instant: HappyForms calls Make through a webhook as soon as the submission goes through, and the module carries the lightning badge.
When to use it
a contact or quote form whose answers must reach your team without anyone copying them over.
Watch out
Make's documentation for HappyForms is limited, so run a test entry with Run once to see which answers the bundle really holds before you map them.
Modules

What else can Make do with HappyForms?

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

HappyForms1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call gives your scenario access to any endpoint of the HappyForms API, through the connection you already created. It fills the gap when New Activity alone is not enough.

When to use it
you need a HappyForms action that has no dedicated module in Make.
Watch out
Make's documentation does not detail this call, so you choose the endpoint and what to send yourself. Each run is one operation, the unit Make counts on your plan.
Need help

Need help automating HappyForms with Make?

A person reads every message.

FAQ

HappyForms and Make: common questions

01Is the HappyForms Make integration free?
Yes, HappyForms is a standard app in Make, so you can use it from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the minimum interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in credits, meaning operations, each month.
02What do you need to connect HappyForms to Make?
A HappyForms account and a Make account; Make's documentation lists no other prerequisite. Add a HappyForms module, click Create a connection, optionally name it, then either approve Make on the HappyForms authorization page or paste the key HappyForms provides. Click Save and the connection is ready. Both HappyForms modules reuse it, so you set it up once. Since the official documentation for this app is limited, check your HappyForms account settings if the window asks for something you do not recognize.
03Does the HappyForms trigger fire in real time?
Yes. New Activity is an instant trigger: HappyForms calls Make through a webhook as soon as a submission succeeds, so Make does not need to check the form at an interval. In the editor you spot it by the lightning badge on the module. Only successful submissions start the scenario. To test it, click Run once and send an entry through your form, then read the bundle New Activity received before mapping its answers into the next module.
04What if the HappyForms module you need is missing in Make?
Use Make an API Call. It can reach any endpoint of the HappyForms API with the connection you already have, which covers what New Activity does not. You pick the endpoint and what to send yourself, since Make's documentation does not detail this call. Keep in mind that Make describes its HappyForms documentation as limited, because little public information exists about the app. If the API cannot give you what you need, another form app with more modules in Make may suit your case better.
05Should you use Make or n8n for HappyForms?
It depends on your case. In Make, HappyForms gives you an instant trigger for each successful submission and an API call module for everything else, and it works from the Free plan. Many apps also have an n8n node, so check whether one exists for HappyForms before deciding. Compare what each tool offers for this specific app, then pick the one whose modules match the scenario you have in mind and the tool your team already works in.
Same platform

Other docs you might need on this stack.

Browse all integrations