Resources · Zapier integration

Magpi Zapier integrationAutomate Magpi with Zapier.

Magpi Zapier integration: 3 triggers, 0 actions, 0 searches. All three are instant and follow the life of a form record: added, updated, deleted. Each one hands the record to your other tools. Below: the real cost, the connection, a first Zap and the traps.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Magpi Zapier integration does for you

Magpi is built for collecting data in the field: people fill its forms on a phone, with or without a network, and it can also take answers by text message. On Zapier, Magpi reports what happens to the records of a form, and a Zap (the automation you build on Zapier) carries each record to another app.

Three results cover most needs. A live copy of the collection: New Record sends each submitted record to a spreadsheet or a database, so the analysis starts without an export. Corrections that follow: Update Record passes on a record that someone edited, so the copy elsewhere can be brought back in line. A trace of what disappeared: Delete Trigger reports a record removed from a form, so another tool can log it or clean up its own copy.

Here is what Zapier does not do with Magpi. There is no action and no search. A Zap therefore cannot create a form, add or edit a record in Magpi, send an SMS through Magpi or look up an existing record. Everything flows one way, out of Magpi and into the tools you already use. And records collected before your Zap was switched on are never replayed.

This site has no Magpi page for Make or n8n yet. If you are weighing platforms anyway, start with n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Seven Zapier terms come back on this page. One plain line each, and after that the page uses them as is.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap, like a new record on a Magpi form. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts those and nothing else.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app itself as it happens. All three Magpi triggers are instant.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your Magpi account linked to Zapier once, then reused by every step and every Zap that reads from Magpi.
Cost

What a Magpi Zap really costs

Magpi is not a premium app, so it works on the free plan. Zapier counts tasks, and Magpi's triggers never count as one.

  • Delete Trigger, New Record, Update Record0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo

A record that is added, updated or deleted costs nothing. Each action that succeeds afterwards, in the other app, costs one task; an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger and one action. A filter or a second action makes it a multi-step Zap, which needs a paid plan. The grid below shows how often Zapier checks polling triggers on each plan. It does not apply to Magpi, whose three triggers are instant on every plan.

Connect

Connect Magpi to Zapier in three steps

  1. 01

    Go to Apps

    In your Zapier account, open Apps and click + Add connection. You need a Magpi account, plus access to any form you do not own yourself and want the Zap to watch.

  2. 02

    Choose Magpi

    Search for Magpi in the dialog, select it and click Add connection. A new tab opens on the Magpi side, where you sign in with your usual Magpi account.

  3. 03

    Sign in and grant access

    Log in to Magpi in that tab and let Zapier reach the account. The connection then sits in your list, and every Magpi trigger in every Zap you build reuses it.

First Zap

First Zap: a spreadsheet that fills as records come in

GoalAnalyse collected data without exporting: each new record on one Magpi form that passes your filter becomes a row in your spreadsheet.

  1. 01

    Start with New Record

    Create a Zap, choose Magpi as the app and New Record as the event, then select your Magpi connection from the account list.

  2. 02

    Pick the form

    Choose the form to watch in the required Form field. Only records added to that form will start this Zap, so one Zap follows one form.

  3. 03

    Test on real records

    Run the test. Zapier brings back the three most recent records of that form, so you map the columns on a real submission rather than on blanks.

  4. 04

    Add the filter and the sheet

    From the plus icon, add Filter: field, rule, value. Then add your spreadsheet and map the answers to columns. The filter makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the row looks right, click Publish. Every new record that passes the filter is copied from then on.

Triggers

Magpi triggers

3 events start a Zap when something happens in Magpi, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Delete Trigger

Instant trigger

In Zapier“Triggers when a Form record is deleted.”

Starts your Zap when a record is removed from the Magpi form you picked, and passes what Zapier receives about it to the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a copy of your Magpi data lives elsewhere and must not keep records that were deleted at the source.
Watch out
the form to watch is a required field, so one Zap only hears about deletions on that single form.
2

New Record

Instant trigger

In Zapier“Triggers when a new record is added to a Form.”

Fires each time a record is added to the chosen Magpi form, and hands that record, with its answers, to the steps that follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
collected data should reach a spreadsheet, a database or a team without anyone exporting it first.
Watch out
you must choose the form, a required field; records sent to any other form do not start this Zap.
3

Update Record

Instant trigger

In Zapier“Triggers when a Form record is updated.”

Reacts when an existing record on your Magpi form is edited, and sends the updated version on to the rest of the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
someone corrects an answer after the fact and the copy in another tool must be brought back in line.
Watch out
the form to watch is required here too; pair this Zap with a New Record Zap on the same form to keep both sides aligned.
When it breaks

When a Magpi Zap breaks

Zapier attaches no help article to Magpi, and the app page lists no limit of its own. The cases below come from how Zapier works, applied to Magpi.

  • Earlier records never arrive

    A Zap only reacts to what happens after it is switched on. Records already on the form are not replayed, and copying them is a separate job.

  • A big batch is held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the Zap back.

  • The Zap will not publish on Free

    The free plan allows one trigger and one action per Zap. A filter or a second action makes it multi-step, and that needs a paid plan.

  • A failed step, no task billed

    An action that does not go through is not counted. The record did not reach the other app either, so read what the step returned.
Need help

Need help automating Magpi with Zapier?

A person reads every message.

FAQ

Magpi Zapier integration: frequent questions

01Is the Magpi Zapier integration free?
Yes. Magpi is not a premium app, so its three triggers work on the free plan. That plan includes 100 tasks a month and unlimited Zaps, with one limit people discover late: each Zap has two steps, one trigger and one action. A New Record trigger feeding one spreadsheet fits. A filter, a second action or a search step turns the Zap multi-step, and that needs a paid plan. Also check the app on the receiving end, since premium apps are kept for paid plans and the free trial.
02How many tasks does a Magpi Zap use?
The Magpi side costs nothing: a trigger never uses a task, whether the record was added, updated or deleted. What counts is each action that succeeds in the other app. One action per record means one task per record; three actions mean three. An action that fails is not counted. Watching for new events is free however often it happens. A few apps and actions take more than one task when they complete, so look at your receiving steps before you choose a plan.
03Are Magpi triggers real time?
Yes, all three. Delete Trigger, New Record and Update Record are instant: the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan. On the free plan, polling triggers are checked every 15 minutes, and that wait does not concern Magpi. In the editor, a Zap built on an instant trigger shows a lightning bolt. The type is set by Magpi itself, so there is nothing to change in Zapier, and no faster plan to buy for it.
04What do you need to connect Magpi to Zapier?
A Magpi account, and access to any form you do not own but want the Zap to watch. In Zapier, open Apps, click + Add connection, search for Magpi, click Add connection, sign in to Magpi in the new tab and grant access. Each trigger then asks for a form, and that field is required, so the account needs at least one form it can see. The connection is reused by all your Magpi triggers afterwards, so you set it up once.
05Why does a Magpi Zap ignore records from another form?
Because each trigger watches one form only. Delete Trigger, New Record and Update Record all ask which form to follow, and that field is required. Records added, edited or deleted on any other form never reach that Zap. If several forms need the same treatment, build one Zap per form. The free plan allows unlimited Zaps, so that costs nothing extra in Zaps; the tasks are still counted per successful action, whichever form the record came from.
06What if the Magpi operation you need is not on Zapier?
Then Zapier does not offer it today. The editor shows only what the Magpi app page lists: three triggers, Delete Trigger, New Record and Update Record, with no action and no search. So a Zap cannot create a form, write a record into Magpi, send a message through it or look up a record. Everything starts from a change on a form and flows outward. If that is not enough, compare what each automation tool publishes for Magpi before you plan around a step that is not there.
07Zapier, Make or n8n for Magpi?
Choose by criterion, not by ranking. On Zapier, Magpi brings three instant triggers on form records and works on the free plan as long as each Zap keeps two steps. Billing is per successful action, so count what each record will go through. Then weigh where your other apps are already connected and which editor your team can maintain. Whatever you pick, check first that the tool exposes the Magpi events you rely on, since each tool publishes its own list of operations.
Same platform

Other docs you might need on this stack.

Browse all integrations