Resources · Zapier integration

Metaforms Zapier integrationAutomate Metaforms with Zapier.

1 trigger, 0 actions, 0 searches. The Metaforms Zapier integration does one job: it hands every new form response to the rest of your tools, the moment it lands. Here is what that costs, how to connect it and what to watch.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Metaforms Zapier integration actually does

Metaforms builds feedback forms driven by AI, where the next question adapts to the previous answer. Zapier links it to your other apps: each time someone finishes a form, a Zap (the automation you build on Zapier) picks up that response and passes it to the tool of your choice.

Everything rests on a single trigger, New Form Response. That is enough for three useful outcomes. A response log: every answer becomes a row in a spreadsheet, so the whole team reads the same list instead of logging in to Metaforms. A feedback alert: a filter checks one field of the response and only the ones that match reach your team chat. A follow-up record: the response opens or updates an entry in the tool where you track the people who answered.

Now the honest part. Zapier offers no action and no search for Metaforms. It cannot create a form, edit a response or push anything back into Metaforms: the data flows one way, out, and the trigger is the only door. And a Zap never goes back in time, so responses collected before you switch it on stay where they are.

If you are weighing Zapier against other platforms for this kind of flow, see our n8n vs Zapier guide, or open our Zapier review first.

Vocabulary

The Zapier words you will meet on this page

Eight terms, in plain English. Each one appears again below without a reminder.

Zap
The automation itself: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Here, a finished Metaforms 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 task is one action your Zap completes successfully; your plan counts those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Connection
Your Metaforms account linked to Zapier once, then reused by every Zap and every step that needs it.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What it really costs

The Metaforms trigger never costs a task. You pay for what happens after it: each action that succeeds counts once.

  • TriggerFree, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A two-step Zap (the trigger plus one action) runs on the free plan, which gives 100 tasks a month and unlimited Zaps, each limited to two steps. Add a filter or a second action and it becomes multi-step, so a paid plan. An action that fails is not counted. Metaforms is not a premium app. The interval grid below exists for polling triggers only; it does not apply to this app, whose single trigger is instant.

Connect

Connect Metaforms to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Metaforms account, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Find Metaforms

    Type Metaforms in the search box of the dialog, pick it from the list, then click Add connection. A new tab opens on the Metaforms side, where you finish the sign-in.

  3. 03

    Sign in and grant access

    Log in to Metaforms in that tab and allow Zapier to reach the account. From then on, every Zap you build on Metaforms reuses that same connection, so you sign in only once.

First Zap

Your first Zap: unhappy answers straight to the team chat

GoalEach new Metaforms response is checked by a filter, and only the ones matching your condition reach your team chat as a message.

  1. 01

    Pick the trigger

    Create a Zap, choose Metaforms as the app and New Form Response as the event. Select your connection, then the form to watch in the Form field.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent responses of the connected account, so you map the next steps on a real one. No empty sample to guess from.

  3. 03

    Add the filter

    Click the plus icon and add Filter. Set the three boxes: the field to look at, the rule, the value. Pick a text rule for text and a number rule for numbers.

  4. 04

    Add the action

    Pick your chat app and its message action, then map the response fields into the message. Test this step and read what came back before going further.

  5. 05

    Publish

    Click Publish to switch the Zap on. With a filter it is a multi-step Zap, so it needs a paid plan; without the filter, the same alert runs on the free plan.

Triggers

The Metaforms trigger

1 event starts a Zap when something happens in Metaforms, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New Form Response

Instant trigger

In Zapier“Triggers when a new form response is received.”

Starts your Zap each time someone completes one of your Metaforms forms, and passes the answers to the next step so you can file, forward or sort them.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
any time a finished response should land somewhere else, such as a spreadsheet row or a message to the people who read feedback.
Watch out
the Form field is required, so one Zap watches the form you pick there; check at test time which answers come through.
When it breaks

When it breaks

Metaforms has no documented error of its own on Zapier. What goes wrong comes from how Zapier works in general.

  • Old responses never show up

    A Zap only reacts to what happens after it is switched on. Responses collected earlier stay in Metaforms; moving that backlog is a separate job.

  • A sudden wave gets held back

    When a trigger suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold those runs back instead of firing them all.

  • The filter never lets anything through

    Filter rules are typed: a text rule only works on text, a number rule only on numbers. Picking the wrong type is the usual reason a filter never passes.
Need help

Need help automating Metaforms with Zapier?

A person reads every message.

FAQ

Metaforms and Zapier: frequent questions

01Is the Metaforms Zapier integration free?
Yes, as long as your Zap stays at two steps. Metaforms is not a premium app, so it works on Zapier's free plan, which gives 100 tasks a month and unlimited Zaps of two steps: the New Form Response trigger plus one action. A spreadsheet log or a simple alert fits that frame. The moment you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. The trigger itself never costs a task.
02How many tasks does a Metaforms Zap use?
One task per action that succeeds, per response. The trigger is free, so a Zap that turns each response into a spreadsheet row costs one task each time someone finishes the form. A Zap that writes the row and also posts a message costs two per response. A filter that stops the Zap means the actions after it never run, so nothing is counted for them. An action that fails is not counted either. Some apps and actions take more than one task when they complete.
03Does Metaforms reach Zapier in real time?
Yes. New Form Response is an instant trigger: Metaforms tells Zapier the moment a form is completed, and the Zap starts right away whatever your plan. The polling interval of each plan does not apply here, which makes this integration a good fit for the free plan. In the editor, a Zap built on an instant trigger shows a lightning bolt, a quick way to check the trigger type before you publish.
04What do you need to connect Metaforms to Zapier?
An account on Metaforms, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once from the Apps page of your Zapier account: you click + Add connection, search for Metaforms, sign in to it in the tab that opens and grant Zapier access. Every Zap you build on Metaforms then reuses that connection, so there is nothing to redo per Zap.
05Why does a new Zap ignore earlier Metaforms responses?
Because a Zap only reacts to what happens after it is switched on. Responses collected in Metaforms before you published the Zap are never picked up, however many there are. If you need them in your spreadsheet or your other tool, moving that history is a separate job, done outside the Zap. From the moment the Zap is on, each new completed form goes through. Because the trigger is instant, each of those new responses starts the Zap right away, whatever your plan.
06What if the Metaforms operation you want is not there?
Then Zapier cannot do it for Metaforms today. The app currently exposes one trigger, New Form Response, and no action or search, so nothing can be created or changed inside Metaforms from a Zap. The Metaforms page on Zapier shows the current list of operations, worth checking before you plan a flow. Inside that limit, the trigger can still feed any action of your other apps, which covers most cases where responses need to go somewhere.
07Zapier, Make or n8n for Metaforms?
Judge on criteria, not on a ranking. On Zapier, Metaforms offers one instant trigger, so the plan interval never slows it down, and a two-step Zap runs on the free plan. What you pay for is the number of successful actions per response, and any filter means a paid plan. Whether Make or n8n carry a Metaforms connector is not covered here: check their catalogues, then compare how each one bills a flow that runs once per response.
Same platform

Other docs you might need on this stack.

Browse all integrations