Resources · Make integration

Daxium Air Make integrationAutomate Daxium Air with Make.

Field forms are only useful once their data reaches the rest of your tools. The Daxium Air Make integration offers 17 modules, 9 actions and 8 searches, to create, read and clean up submissions. This guide connects your account and walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Daxium Air Make integration do for you?

The Daxium Air Make integration links your Daxium Air account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that acts on one app. With it, form submissions, their files and your lists move to other apps without copy and paste.

Records created from elsewhere. When a row lands in a spreadsheet or a CRM, Create Form Submission turns it into a Daxium Air submission under the structure you choose, so nobody retypes the same data twice.

Attachments that reach the right place. Get Submission File pulls a file out of a submission and hands it to the next module, which can store it in a drive or send it to a client. List Submission Reports does the same job for the reports tied to a record.

A targeted export. Search Form Submissions keeps only the records matching your conditions, then a sheet or a database module writes them down, one line per record.

Know the limits before you start: Daxium Air has no trigger module in Make, so a scenario starts on a schedule or on another app, and Make's own documentation for this app is limited. Make an API Call fills the gaps. Many apps also have an n8n node; the n8n vs Make comparison helps you pick, and the Make pricing page explains what each plan allows. New to the editor? The Make training starts from zero.

Connect

How do you connect Daxium Air to Make?

  1. 01

    Add a Daxium Air module

    In any scenario, click the +, search for Daxium Air and pick a module, for example List Instances. In its settings, click Create a connection. A connection is your Daxium Air account linked to Make once, then reused by every module of the app.

  2. 02

    Name it and authorize Make

    Give the connection a clear name if you like, useful once you manage several accounts. Then authorize Make on the Daxium Air page that opens, or paste the key that Daxium Air gives you, depending on what the connection window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown. To make sure it works, run List Instances with Run once: if bundles come back, Make can read your account and every other module will use the same access.

First scenario

Your first scenario with Daxium Air

GoalWhen a new row appears in your spreadsheet, Make creates the matching submission in Daxium Air.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since Daxium Air has no trigger, the first module comes from the app that holds your rows, such as your spreadsheet tool.

  2. 02

    Add Create Form Submission

    Click the + on the right of that first module, search for Daxium Air and choose Create Form Submission. Select your connection, or click Create a connection if this is your first Daxium Air module.

  3. 03

    Pick the structure and map the data

    Choose the structure that should receive the submission; Make lists what it can read once the connection exists. Then drag the values of the row into the matching fields, so each bundle becomes one submission.

  4. 04

    Test with Run once

    Add a test row, then click Run once. Open the bubble above each module to read the bundles it received and check that the submission shows up in Daxium Air as expected.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on, each new row turns into a submission without anyone opening Daxium Air.

Modules

What each Daxium Air module does

Daxium Air gives you 17 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Daxium Air1

Create Form Submission

Action

In Make“Create a new form submission for a given structure.”

Adds a brand new form submission to Daxium Air under the structure you pick, so data collected in another tool lands in the right form without retyping.

When to use it
a row, an email or a web form answer from another app should become a Daxium Air record.
Watch out
choose the structure first, since the submission belongs to it, and test on dummy data before switching the scenario on.
Daxium Air2

Delete a Form Submission

Action

In Make“Deletes a form submission using its id.”

Removes one form submission for good, identified by its ID. It keeps Daxium Air tidy when a record was created by mistake or duplicated by an earlier test.

When to use it
after a Run once created test submissions you do not want to keep.
Watch out
a delete cannot be undone from Make, so map the ID from a search you trust rather than typing it by hand.
Daxium Air3

Get a Form Submission

Action

In Make“Get a specific form submission using its id.”

Brings back the content of a single submission when you already know its ID. You get one bundle, one item passed to the next module, ready to map into an email, a sheet or a report.

When to use it
an earlier module handed you the ID and you need the details behind it.
Watch out
without an ID, start with Search Form Submissions instead.
Daxium Air4

Get an Instance

Action

In Make“Retrieves a specific instance using the app_short parameter.”

Returns one Daxium Air instance, which the module identifies through its app_short parameter. Handy when the rest of the scenario must point at one precise instance.

When to use it
before modules that need to know which instance to work in.
Watch out
the documentation says little about this parameter, so copy the value that List Instances returns rather than guessing it.
Daxium Air5

Get a Structure

Action

In Make“Retrive a specific structure for a given app.”

Reads one structure of a given app, the same kind of structure that new submissions are created under. Checking it first spares you from writing values into the wrong form.

When to use it
while setting up Create Form Submission or Patch Form Submission, to confirm which structure you target.
Watch out
it reads a single structure; to browse all of them, List Structures is the better pick.
Daxium Air6

Get Custom App

Action

In Make“Get the full custom app from its id”

Loads a whole custom app from its ID in one step. The result can feed a documentation sheet or show you what the app holds before you write into it.

When to use it
you have the ID from List Custom Apps and want everything about that one app.
Watch out
the module needs the exact ID, so chain it after the list module instead of pasting values by hand.
Daxium Air7

Get Submission File

Action

In Make“Retrieve a file from its ID and a submission ID”

Retrieves a file attached to a submission, using the file ID and the submission ID together. The file then travels to the next module, to be stored in a drive or sent by email.

When to use it
photos or documents gathered in a form have to end up somewhere else.
Watch out
on the Free plan Make handles files up to 5 MB, so heavier attachments call for a paid plan.
Daxium Air8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Daxium Air API while reusing the connection you already created, so no second login is needed. It covers what the listed modules leave out.

When to use it
none of the other Daxium Air modules does the job you have in mind.
Watch out
you have to know the endpoint and its parameters yourself, and public documentation on Daxium Air is limited.
Daxium Air9

Get List Items

Search

In Make“Get list items using its id.”

Fetches the items of one Daxium Air list from its ID, each returned as a separate bundle. That makes it simple to copy the values of a list into a sheet or to compare them with another tool.

When to use it
a list stored in Daxium Air must be mirrored or checked elsewhere.
Watch out
modules placed after it run once per item, and each run is an operation, one execution counted on your plan.
Daxium Air10

List Custom Apps

Search

In Make“Lists all custom apps for a specific instance”

Shows every custom app of one instance, one bundle per app. It is the starting point when you want to act on several apps or simply find the ID of one.

When to use it
to feed Get Custom App, or to take stock of what an instance contains.
Watch out
point it at the right instance, otherwise the list will not match what you expect to see.
Daxium Air11

List Form Submissions

Search

In Make“Lists all submissions linked to the form.”

Pulls all the submissions linked to a form in one pass, each as its own bundle. Exports become easy: every record can be written as a line in a sheet or a database.

When to use it
you want the whole set, with no filter at all.
Watch out
nothing in the documentation says it skips records already read, so expect the same ones at each scheduled run and prefer Search Form Submissions when only some matter.
Daxium Air12

List Instances

Search

In Make“Lists all instances.”

Lists every Daxium Air instance in one go. Most people use it once while building, to find the value that other modules expect as an instance.

When to use it
before Get an Instance or List Custom Apps, when you do not know which instance to target.
Watch out
it returns several bundles, so anything placed after it runs once per instance unless you add a filter.
Daxium Air13

List Lists

Search

In Make“List all instances for a specific instance”

Returns the lists that belong to a specific instance, one bundle each. Picking the right one there gives you the ID that Get List Items needs.

When to use it
you manage several lists and want to sync or check them one after another.
Watch out
the official wording of this module is ambiguous, so run it once and read the bundles before mapping anything further.
Daxium Air14

List Structures

Search

In Make“Lists all structures for a given app.”

Gives back all the structures of a given app. From there you decide which one should receive new submissions or which one deserves a closer look.

When to use it
while building, to see the available structures without leaving Make.
Watch out
an app with many structures produces many bundles, so add a filter when only one of them interests you.
Daxium Air15

List Submission Reports

Search

In Make“Lists reports for a given submission.”

Collects the reports tied to one submission, so you can pass them on to a client or file them next to the original record.

When to use it
a submission is complete and its reports must leave Daxium Air for an email, a drive or a CRM.
Watch out
a submission may have no report yet, and then the next modules simply receive nothing and do not run.
Daxium Air16

Search Form Submissions

Search

In Make“Search find submissions that correspond to specific field operators.”

Finds only the submissions that match conditions set with field operators, instead of returning everything. Fewer bundles also means fewer operations used on your plan.

When to use it
you only care about the records that meet a precise condition on one of their fields.
Watch out
a search can return none, one or many results, so test it with Run once and count the bundles.
Daxium Air17

Patch Form Submission

ActionIn the docs only

Its name points to an update of an existing submission rather than a new one. Make gives no official description for it, so confirm its exact behavior on a dummy record.

When to use it
a value changed in another tool and the matching Daxium Air record should follow.
Watch out
the documentation does not say which fields it accepts, so run it once on test data before relying on it.
Need help

Need help automating Daxium Air with Make?

A person reads every message.

FAQ

Daxium Air and Make: frequent questions

01Is the Daxium Air Make integration free?
Yes. Daxium Air is a standard app in Make, available from 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 40 minutes of execution, with usage counted in credits each month. Your Daxium Air subscription is a separate matter that this page does not cover.
02What is needed to connect Daxium Air to Make?
A Daxium Air account and a Make account are enough to get started, as the documentation lists no other prerequisite. Add any Daxium Air module, click Create a connection, optionally give it a name, then authorize Make on the Daxium Air page or paste the key the app gives you, and click Save. The connection is created once and reused by all 17 modules, so you never repeat these steps for each new scenario that touches the same account.
03Does Daxium Air trigger Make scenarios in real time?
No. Daxium Air has no trigger module in Make, neither scheduled nor instant, so nothing inside Daxium Air can start a scenario by itself. You have two ways around it. Put a search module such as Search Form Submissions first and let the schedule run it, every 15 minutes by default and down to 1 minute on paid plans. Or start the scenario on a trigger from another app, a new row or a new contact, and let Daxium Air modules do the work after it.
04What if the Daxium Air module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Daxium Air API with the connection you already set up, which covers anything the listed modules do not. Keep in mind that Make describes its own Daxium Air documentation as limited, for lack of public information about the app, so plan to test each call with Run once on dummy records before switching the scenario on. The Make troubleshooting guide helps when a call fails.
05Should you use Make or n8n for Daxium Air?
It depends on where your automations already live. In Make, Daxium Air comes with 17 ready modules plus Make an API Call, and the page above shows how to build with them without code. Many apps also have an n8n node, so check whether Daxium Air has one before deciding. Neither tool is ranked here: keeping all your scenarios in one place is usually the simplest criterion, and the comparison linked in the first section lays out how the two tools differ.