Resources · Make integration

MoreApp Forms Make integrationAutomate MoreApp Forms with Make.

What happens to a form once your field team hits submit? The MoreApp Forms Make integration gives you 17 modules, 13 of them triggers, to push submissions, tasks and exports into your other tools. This page walks you through the connection and a first working scenario.

Try the MoreApp Forms integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MoreApp Forms Make integration do for you?

It links your MoreApp account to Make so that what happens in your forms starts an automation on its own. In Make, that automation is a scenario: a chain of modules, where each module is one brick, such as a trigger that watches MoreApp or an action that does something there.

Tasks handed out without retyping. A job lands in another tool you already use, and Create Task opens the matching task in MoreApp. When the worker completes it, Watch Task Fulfilled lets the next step start by itself.

Failures you hear about. Watch Submission Pipeline Failed and Watch Datasource Import Failed turn a silent problem into an alert in the channel your team actually reads, so nobody discovers it days later from a customer.

Files that leave MoreApp. Download File and Download Report pull content out of MoreApp so the next module can store or send it, for instance after Watch Export Finished.

What the app does not offer in Make: no search module, and the doc shows no instant trigger. Every trigger waits for the scenario's schedule, and anything the listed modules skip goes through Make an API Call. To judge Make itself first, the Make training starts from zero, Make pricing explains how operations are counted, and n8n vs Make puts the two tools side by side if you are still choosing.

Connect

How do you connect MoreApp Forms to Make?

  1. 01

    Create an API key in MoreApp

    In MoreApp, open the Settings page, go to the API keys tab and click Add. Name the key after its use, click Save, then copy the key shown in the window before closing it.

  2. 02

    Open the connection window in Make

    Add any MoreApp Forms module to your scenario and click Create a connection. A connection is your MoreApp account linked to Make once, then reused by every MoreApp module you add later.

  3. 03

    Paste the key and save

    Give the connection a clear name in Connection name (optional, but handy with several accounts), paste the API key you copied, and confirm. Make can now read and act on your MoreApp account.

First scenario

Build your first scenario with MoreApp Forms

GoalWhen a new job appears in the tool where you plan your field work, Make creates the matching task in MoreApp Forms.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module.

  2. 02

    Start from your planning tool

    Pick the app where new jobs show up, choose its trigger and connect it. Each job it finds becomes a bundle: one item handed to the next module.

  3. 03

    Add Create Task

    Click the + on the right, search MoreApp Forms, pick Create Task and select the connection you set up with your API key.

  4. 04

    Map the job details

    Fill the fields Make shows for the task, dragging values from the first module so each job lands in MoreApp with its own details.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check the task in MoreApp.

  6. 06

    Schedule and switch it on

    On the first module, keep the default schedule of every 15 minutes or change it (15 minutes is the floor on the Free plan), then switch the scenario on.

Triggers

The 13 MoreApp Forms triggers

13 modules start a scenario when something happens in MoreApp Forms. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by MoreApp Forms as soon as it happens.

MoreApp Forms1Watch Datasource Import Failed

Watch Datasource Import Failed

triggerIn the docs only

You get told when a datasource import fails in MoreApp, instead of finding out from a form that shows old choices. Make hands the failed import to the next module, which can post an alert or open a ticket.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule, so the alert arrives at the next check, not the second the import breaks.
When to use it
when someone on your team maintains the lists your forms rely on and needs to act before field staff notice.
Watch out
the doc gives no description of this module; run it once to see which details the bundle actually carries.
MoreApp Forms2Watch Export Finished

Watch Export Finished

triggerIn the docs only

Your scenario starts when Make finds that a MoreApp export has completed, which is the right moment to do something with its result.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and picks up exports that finished since the last check.
When to use it
when an export should reach an accountant, a shared drive or a client without someone downloading it by hand; follow it with Download File or Download Report and a storage module.
Watch out
on the Free plan, files above 5 MB are out of reach, so check export size before building the rest of the flow.
MoreApp Forms3Watch Export Scheduled

Watch Export Scheduled

triggerIn the docs only

This one picks up an export once it is planned in MoreApp, before anything runs, at the scenario's next check. It gives you a trace of what is coming.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and returns each export planned since its last look.
When to use it
when an ops lead wants a log of planned exports in a sheet, or a heads-up to the person who will receive the files.
Watch out
the export has not produced anything yet at this stage, so do not chain a download here; keep that for Watch Export Finished.
MoreApp Forms4Watch Export Started

Watch Export Started

triggerIn the docs only

With this trigger, Make reacts when an export actually begins in MoreApp. It sits between the planned stage and the finished one.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule, so a short export may already be done by the time the scenario runs.
When to use it
when you track how exports progress, for example to update a status column that says an export is in progress.
Watch out
if all you want is the file, this trigger is one step too early. Most scenarios that move data start from Watch Export Finished instead.
MoreApp Forms5Watch Submission Created

Watch Submission Created

triggerIn the docs only

Every new form entry in MoreApp becomes a bundle in Make, ready to feed a CRM, a spreadsheet or a message to the office. This is the trigger most MoreApp scenarios start from.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and returns the submissions created since the previous run.
When to use it
when an inspection, a delivery note or a site report should reach the back office without anyone copying it over.
Watch out
several submissions can arrive in one check, and every module after the trigger then runs once per submission, which adds up in operations on your plan.
MoreApp Forms6Watch Submission Deleted

Watch Submission Deleted

triggerIn the docs only

Keep other tools in step when a submission disappears from MoreApp. Make passes each deleted submission to the next module so you can mark the matching row or record.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule for submissions removed since its last pass.
When to use it
when a copy of your submissions lives in a sheet or a CRM and an entry removed in MoreApp should not survive elsewhere.
Watch out
none of the 17 modules brings a submission back, so this trigger records a deletion; it cannot undo one. Run it once to see what the bundle still contains.
MoreApp Forms7Watch Submission Pipeline Blocked

Watch Submission Pipeline Blocked

triggerIn the docs only

A submission stuck in its MoreApp pipeline surfaces here, so somebody can unblock it before the form result is expected elsewhere.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and returns pipelines that reached the blocked state since the last check.
When to use it
when you want a task or a chat message for the admin whenever processing of a submission is held up.
Watch out
a blocked pipeline and a failed one are two separate triggers. If you want both, either build two scenarios or accept that one of the cases goes unwatched.
MoreApp Forms8Watch Submission Pipeline Created

Watch Submission Pipeline Created

triggerIn the docs only

Here Make catches the moment MoreApp opens a pipeline for a submission, the first step of its processing on the MoreApp side.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and picks up the pipelines created since then.
When to use it
when you log each stage of a submission's life, for instance to measure later which ones get stuck.
Watch out
for most flows, the submission itself matters more than the start of its pipeline; if you only need the data, Watch Submission Created is the simpler choice.
MoreApp Forms9Watch Submission Pipeline Failed

Watch Submission Pipeline Failed

triggerIn the docs only

Turn a failed pipeline into something a person sees. Each failure becomes a bundle that the next module can route to email, chat or a ticket queue.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and returns the failures recorded since its previous check.
When to use it
when a failed submission means a customer does not get a report, and your support lead needs to know that same day.
Watch out
keep the alert module simple. If the alert itself breaks, you lose the warning, and the Make troubleshooting guide covers how to read the error.
MoreApp Forms10Watch Submission Pipeline Mail Sent

Watch Submission Pipeline Mail Sent

triggerIn the docs only

You learn that MoreApp has sent the mail tied to a submission pipeline, which gives you proof of sending in your own tools.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and returns the mails sent since the last run.
When to use it
when your CRM should show that a customer received their report, or a follow-up should only start once the mail is out.
Watch out
this confirms MoreApp sent the mail, not that someone opened it. Run once shows you exactly what the bundle holds before you build a follow-up on it.
MoreApp Forms11Watch Submission Pipeline Succeeded

Watch Submission Pipeline Succeeded

triggerIn the docs only

Your scenario starts only when MoreApp reports that a submission went through its whole pipeline, the green light for any step downstream.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and returns pipelines completed since the previous check.
When to use it
when you want to bill, archive or close a job only after MoreApp has finished its own processing, not as soon as the form arrives.
Watch out
do not pair it with Watch Submission Created for the same action, or the same submission will be handled twice.
MoreApp Forms12Watch Task Created

Watch Task Created

triggerIn the docs only

Each task created in MoreApp comes into Make as a bundle, which lets you mirror the dispatch in a calendar, a planning sheet or a message to the assignee.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and returns tasks created since its last check.
When to use it
when tasks are handed out inside MoreApp and the rest of the team plans from another tool.
Watch out
never put Create Task after this trigger in the same scenario. Every task you create could be picked up again at the next check and create another one, in a loop.
MoreApp Forms13Watch Task Fulfilled

Watch Task Fulfilled

triggerIn the docs only

Close the loop on field work: Make picks up each task a worker completes in MoreApp and hands it to the next step.

How it fires
scheduled, Make checks MoreApp on the scenario's schedule and returns tasks fulfilled since the previous run.
When to use it
when a completed task should update a job status, notify the customer or trigger an invoice in your billing tool.
Watch out
because the trigger is scheduled, the status elsewhere lags behind MoreApp until the next check; tell the office so nobody chases a job already done.
Modules

What MoreApp Forms can do in a scenario

MoreApp Forms gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

MoreApp Forms1

Create Task

ActionIn the docs only

Create Task opens a task in MoreApp from data that lives elsewhere, so a job planned in another tool reaches the field worker without being typed twice.

When to use it
after a trigger from your planning sheet, CRM or booking tool, when each new job needs its own MoreApp task.
Watch out
fill the fields Make shows from the previous module rather than typing fixed values, or every task will look the same.
MoreApp Forms2

Download File

ActionIn the docs only

This action pulls a file out of MoreApp and hands it to the next module as data, ready to be stored or attached somewhere else.

When to use it
when a file linked to a submission or an export must end up in a shared drive or an email to a client.
Watch out
on the Free plan Make handles files up to 5 MB, so large files need a paid plan before this step works.
MoreApp Forms3

Download Report

ActionIn the docs only

Get a MoreApp report out of the app and into your scenario, so the next module can archive it or send it where people read it.

When to use it
when the report is the thing a customer or manager expects, rather than the raw submission data.
Watch out
the doc does not describe which report this returns; test it with Run once before wiring it into a client email.
MoreApp Forms4

Make an API Call

ActionIn the docs only

Reach any part of the MoreApp API from your scenario with the connection you already set up, for everything the dedicated modules leave out.

When to use it
when you need a search, an update or any action that has no dedicated module in the list.
Watch out
you write the request yourself here, so keep the MoreApp API documentation open and test with Run once.
Need help

Need help automating MoreApp Forms with Make?

A person reads every message.

FAQ

Questions about MoreApp Forms and Make

01Is the MoreApp Forms Make integration free?
Yes, on the Make side. MoreApp Forms is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run and files up to 5 MB. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active MoreApp account, which MoreApp bills on its own terms, so check their pricing page for that part.
02What do you need to connect MoreApp Forms to Make?
An active MoreApp account and an API key. You create the key in MoreApp under Settings, in the API keys tab: click Add, name it, save, then copy the key from the window that appears. In Make, add any MoreApp Forms module, click Create a connection, optionally name it, and paste the key. That single connection then serves all 17 modules, so you only do this once per MoreApp account.
03Do MoreApp Forms triggers react instantly in Make?
No. The doc lists no instant trigger for MoreApp Forms, and their names suggest all 13 are scheduled, so they wait for the scenario's next run. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest gap, while paid plans go down to 1 minute. If a form result needs to move faster than that, shorten the schedule on a paid plan and keep the modules after the trigger light, since each run handles everything found since the last one.
04What if a MoreApp Forms module is missing in Make?
Use Make an API Call. It is one of the 17 modules and calls any endpoint of the MoreApp API with the same connection, so a search or an update that has no dedicated module is still possible. You write the request yourself, which means reading the MoreApp API documentation. The Make doc for this app lists no specific limits, so test each call with Run once before you switch the scenario on.
05Should you use Make or n8n with MoreApp Forms?
It depends on what you need to cover. In Make, MoreApp Forms comes with 17 modules, including 13 scheduled triggers and Make an API Call for the rest, all usable from the Free plan. n8n often has a node for the same app, so check whether one exists for MoreApp and which actions it offers before deciding. Compare the modules you would actually use in each tool, then pick the one your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations