Resources · Zapier integration

MTARGET Zapier integrationAutomate MTARGET with Zapier.

The MTARGET Zapier integration gives you 1 trigger, 2 actions and 0 searches. Form Submit picks up new responses to an MTARGET form, while Save Contact and Submit Form Data write contacts and responses into MTARGET from your other apps.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MTARGET Zapier integration does for you

The integration moves form responses and contacts in and out of MTARGET without copy and paste. MTARGET is a marketing platform for building awareness, collecting and managing data, and keeping customers. On Zapier it offers one event to watch, Form Submit, and two things to do: Save Contact and Submit Form Data.

Three outcomes come out of those operations. A single place for responses: a form you run in another tool sends each answer into an MTARGET form through action:submit_data_to_form, so everything sits in one list. A growing contact book: a new person in another app lands in MTARGET with action:save_contact, with its first name, email and Label filled in. A shared record: trigger:trigger_form_submit sends each new MTARGET form response to a spreadsheet, where people who never log in to MTARGET can read it.

Now the limits. The only trigger is Form Submit, so nothing else that happens in MTARGET, such as a contact being edited, can start a Zap. There are no searches either: a later step cannot look up an existing MTARGET contact before writing. And Form Submit is a polling trigger, so responses reach the Zap at your plan's interval, not the moment they are sent.

Comparing platforms first? Read our Zapier review, or open our n8n vs Zapier comparison.

Vocabulary

Zapier words, in plain English

Eight terms come back on this page. Each one is explained once, here, so nothing later needs a second explanation.

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 in an app that starts the Zap. Once the Zap is on, Zapier waits for it. On MTARGET, that is Form Submit.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, such as saving a contact.
Task
The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. MTARGET has none of these on Zapier.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What it really costs

MTARGET is not one of the apps Zapier keeps for paid plans, so it works from the free plan.

  • Trigger and its checksFree, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Filter or second actionPaid plan

Form Submit never costs a task, and neither does each check Zapier runs on it. You pay one task each time an action succeeds, such as a contact saved or a response stored, and an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps of two steps each: one trigger, one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below sets how often Zapier checks Form Submit on each plan.

Connect

Connect MTARGET to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your MTARGET account linked to Zapier once, then reused by every step that uses MTARGET.

  2. 02

    Find MTARGET

    Type MTARGET in the search box of the dialog that opens, pick it from the results, then click Add connection. A new tab opens where you sign in to MTARGET.

  3. 03

    Sign in and grant access

    Sign in to MTARGET in that tab and allow Zapier to access the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

First Zap

Your first Zap: turn form responses into contacts and a shared log

GoalSave each new MTARGET form respondent as an MTARGET contact, then add the response as a row in a spreadsheet.

  1. 01

    Set the trigger

    Start a new Zap, choose MTARGET as the app and Form Submit as the event. Select your connection, then pick the form to follow in the Form ID field.

  2. 02

    Test on real responses

    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 rather than a guess.

  3. 03

    Save the contact

    Add MTARGET with Save Contact. Map the first name and the email from the response, then fill in the Label. Test the step and read what came back before going on.

  4. 04

    Log the response

    Add your spreadsheet app with an action that creates a row. With two actions, this is a multi-step Zap: it needs a paid plan and costs two tasks per response.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, Zapier checks the form at your plan's interval and handles each new response it finds.

Triggers

The MTARGET trigger

1 event starts a Zap when something happens in MTARGET. Zapier checks for them at the interval your plan allows.

1

Form Submit

Polling trigger

In Zapier“Trigger When There is New Form Submission”

Starts your Zap when someone sends a new response to one of your MTARGET forms, and passes that response to the next step so another app can file it, share it or act on it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
when the people who need form responses work in a spreadsheet or another tool rather than in MTARGET.
Watch out
the Form ID field is required, so pick the right form when you set the trigger and check at the test that the sample comes from it.
Actions

The MTARGET actions

MTARGET gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Save Contact

Action

In Zapier“Save your new contact to MTARGET Contact Book”

Adds a person to your MTARGET contact book with the details mapped from an earlier step.

When to use it
when someone shows up in another app and should become part of your MTARGET audience.
Watch out
first name, email and Label are all required, so make sure your source carries the first two and check at the test that they arrive filled.
2

Submit Form Data

Action

In Zapier“Save all form responses to the MTARGET Form.”

Saves the responses carried by an earlier step into one of your MTARGET forms.

When to use it
when responses come in through another tool and you want them kept in an MTARGET form too.
Watch out
the Form field asks for a published form, so publish it in MTARGET before you set this step.
When it breaks

When the Zap breaks

Zapier attaches no help article of its own to MTARGET, so the cases below are the general Zapier limits that apply to these operations.

When a Zap stops behaving, start from these cases. For a step-by-step method, see our Zapier troubleshooting guide.

  • Older responses never show up

    A Zap only reacts to what happens after it is switched on. Form responses sent before you published are not picked up; moving that backlog is a separate job.

  • A big batch gets held back

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

  • A Zap that sets itself off

    As a general precaution, a Zap that writes into the place its own trigger watches can start itself again and again, and burn through your task count.

  • The same response, once

    Zapier remembers which responses Form Submit has already seen, so the same response does not start the Zap twice.
Need help

Need help automating MTARGET with Zapier?

A person reads every message.

FAQ

MTARGET and Zapier: common questions

01Is the MTARGET Zapier integration free?
Yes, it runs on the free plan. MTARGET is not one of the apps Zapier reserves for paid plans and free trials. The free plan gives you 100 tasks a month and an unlimited number of Zaps, but each Zap stays at two steps: one trigger and one action. Saving the contact and logging the response in the same Zap, as in the first Zap above, or adding a filter, makes it multi-step, and that needs a paid plan.
02How many tasks does an MTARGET Zap use?
Only successful actions count. Form Submit never costs a task, however often Zapier checks it. Each Save Contact or Submit Form Data that goes through costs one task, so a two-action Zap, like the first Zap above, costs two tasks per response. An action that fails is not counted against your plan. To plan your volume, count the actions in the Zap and multiply by the responses or contacts you expect each month.
03Is the MTARGET trigger real time?
No. Form Submit is a polling trigger: Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one, 2 minutes on Professional, 1 minute on Team and Enterprise. On paid plans you can change how often it checks and also run a check by hand from the editor. The type comes from the app and cannot be switched to instant.
04What do you need to connect an MTARGET account?
You need an account on MTARGET, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection starts from the Apps page of Zapier with + Add connection, then you sign in to MTARGET in a new tab and grant Zapier access. When you test Form Submit, Zapier brings back the three most recent responses of that account, so you map on real data. The same connection then serves every MTARGET step.
05Does Form Submit pick up responses sent before the Zap was on?
No. A Zap only reacts to what happens after it is switched on, so responses that reached your MTARGET form before you published stay where they are. Moving that backlog to another tool is a separate job, done outside the Zap. From then on, Zapier keeps track of the responses Form Submit has already seen, so the same response does not start the Zap twice. When you test the trigger, the three most recent responses come back only so you can map fields.
06What if the MTARGET operation you need is not there?
Open the MTARGET page on Zapier: it shows the current list of operations, which today is Form Submit, Save Contact and Submit Form Data. Anything else cannot be added from the editor. A workable route is to rebuild the Zap around those three, letting the app on the other side do the rest, or to check whether another automation tool offers the MTARGET operation you are after. Start from the list before you design anything.
07Zapier, Make or n8n for MTARGET?
Compare on criteria rather than picking a winner. Coverage: on Zapier you get one polling trigger and two actions, so check what each other tool offers for MTARGET. Speed: Form Submit waits for your plan's interval, which matters if responses need a fast follow-up. Billing: Zapier counts one task per successful action and never the trigger. Shape: one trigger and one action fit the free plan, anything longer needs a paid plan.
Same platform

Other docs you might need on this stack.

Browse all integrations