Resources · Make integration

Survey123 Make integrationAutomate Survey123 with Make.

Can a new Survey123 response kick off work on its own? The Survey123 Make integration gives you 2 modules: one trigger and one action. This guide is for field and GIS teams who want to connect their account and build a first scenario without code.

Try the Survey123 integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Survey123 Make integration do?

The Survey123 Make integration links your Survey123 for ArcGIS account to Make so that submitted survey responses can start an automation. Make can check a survey for new submissions and produce feature reports, with no code to write and nothing to host on your side.

Reports that follow the field work. An inspector submits a form on site. Watch Survey picks up the new response on the next check, and Create Feature Report builds the report for that record, so nobody has to open the survey and export it by hand.

Responses that reach the rest of your tools. Each response travels through Make as a bundle, meaning one item passed from one module to the next. From there you can hand the data to any other app Make supports, such as a spreadsheet, a chat channel or a CRM. If your forms live elsewhere, the 123FormBuilder Make integration follows the same logic.

A clear picture of what is missing. The catalog is short. There is no search module and no Make an API Call module for this app, so anything beyond watching submissions and creating feature reports needs another route. The documentation does not list any numeric limit either.

Before choosing a plan, compare the options on Make pricing. If you also look at n8n, the n8n vs Make comparison lays out the differences between the two tools.

Connect

How do you connect Survey123 to Make?

  1. 01

    Add a Survey123 module

    In a scenario, add Watch Survey or Create Feature Report, then click Create a connection. A connection is your Survey123 account linked to Make once and reused by every Survey123 module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the account owner or the team helps a lot once several people share the same Make organization and pick connections from a list.

  3. 03

    Authorize and save

    Sign in on the page that opens and approve access for Make, or paste the key the app gives you. Then click Save, and every Survey123 module in your scenarios can reuse this connection.

First scenario

Your first scenario with Survey123

GoalWhen a new response is submitted in Survey123, Make creates a feature report for it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. A scenario is the automation you build: a chain of modules, each one a brick such as a trigger or an action.

  2. 02

    Add Watch Survey

    Search for Survey123, pick Watch Survey and choose your connection. Once connected, fill the module fields and let Make list what it can read from your account.

  3. 03

    Add Create Feature Report

    Click the + on the right of Watch Survey, pick Create Feature Report and map the data coming from the response into its fields.

  4. 04

    Test with Run once

    Submit a test response, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can confirm the report was created.

  5. 05

    Schedule and switch on

    Open the clock on Watch Survey. A new scenario checks every 15 minutes by default; adjust it if your plan allows, then switch the scenario on.

Triggers

What starts a Survey123 scenario

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

Survey1231Watch Survey

Watch Survey

triggerIn the docs only

Watch Survey hands each newly submitted survey response to your scenario, so the rest of the chain acts on it with no manual export. It is the only Survey123 trigger, which makes it the natural first module.

How it fires
it is a scheduled trigger. Make checks the app on the scenario's schedule, every 15 minutes by default, and picks up what arrived since the last check. The docs only list its name, so this type is inferred: the clock badge on the module confirms it.
When to use it
a team collects inspections or site visits in the field and the office needs each one processed as it comes in.
Watch out
each response it returns counts as an operation, one module run on one bundle, on your plan.
Modules

What Survey123 can do in Make

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

Survey1231

Create Feature Report

ActionIn the docs only

Create Feature Report produces a report for a feature in your Survey123 for ArcGIS account, which saves you from generating it by hand in the app. It is the only action this integration offers.

When to use it
right after Watch Survey, to turn each fresh submission into a report you can share with a client or a manager.
Watch out
the documentation gives no detail on its fields, so run it once on a test response before switching the scenario on.
Need help

Need help automating Survey123 with Make?

A person reads every message.

FAQ

Survey123 and Make: common questions

01Is the Survey123 Make integration free?
Yes, Survey123 is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow up to 40 minutes of execution. Usage is counted in operations per month. Your Survey123 or ArcGIS subscription is a separate matter.
02What do you need to connect Survey123 to Make?
You need a Survey123 for ArcGIS account and a Make account. The documentation lists no other prerequisite. When you add a Survey123 module, click Create a connection, give it a name if you like, authorize Make on the page that opens or paste the key the app provides, and click Save. The connection is then reused by both Survey123 modules, so you only do this once per account. After that, every scenario that uses Survey123 simply picks it from the list.
03Does the Survey123 trigger in Make fire in real time?
No. Watch Survey works as a scheduled trigger (the docs only give its name; the clock badge on the module confirms the type): Make checks Survey123 on the scenario's schedule rather than being notified the moment a response is submitted. A new scenario checks every 15 minutes by default. On a paid plan you can bring that down to 1 minute, while the Free plan keeps a floor of 15 minutes. If you need a response processed at once, you will have to accept that short wait or look for another way to call Make.
04What if a Survey123 module is missing in Make?
It depends on what you need. The integration has only Watch Survey and Create Feature Report, and it has no Make an API Call module, so this app cannot go beyond those two jobs. A common workaround is to let Watch Survey bring in the response and do the rest with modules of other apps. For a custom need, the Hack'celeration team can study your case and suggest a route.
05Should you use Make or n8n for Survey123?
It depends on your criteria. On the Make side, the facts are simple: Survey123 is a standard app available from the Free plan, with one scheduled trigger and one action, and no Make an API Call module. Many apps also have an n8n node, so check whether Survey123 does before deciding. Base the choice on the modules each tool offers for your use case and the way you prefer to build, and read the comparison page linked above for the broader differences.
Same platform

Other docs you might need on this stack.

Browse all integrations