MtnStudio Zapier integrationAutomate MtnStudio with Zapier.
The MtnStudio Zapier integration gives you 0 triggers, 2 actions and 4 searches. Your other apps start the Zap, the two actions push leads into MtnStudio, and the four searches look up clients, generators, products and send types along the way.
Verified Trustpilot reviews · AI, automation & growth agency
What the MtnStudio Zapier integration does for you
The integration sends the leads your other tools collect into MtnStudio, without exports or retyping. MtnStudio is a reporting platform built for marketing teams who want to steer their campaigns with better data. On Zapier it offers two actions that create leads and four searches that fetch MtnStudio details for those actions.
Three outcomes come out of those operations. Leads in one place: a form response elsewhere becomes a lead in MtnStudio through action:lead, with Applied Origin, Is Paid Media? and Is Campaign? filled in. Leads routed to one generator: action:leadbygenerator sends the person to a specific lead generator, after you choose a client. Details fetched on the way: a search such as search:product_lookup brings back a product's ID and name from MtnStudio and hands them to the steps that follow. In each case the first card belongs to another app.
Now the limits. MtnStudio has no trigger on Zapier, so nothing that happens inside MtnStudio can start a Zap: the first step always belongs to another app. The two actions only create leads; there is nothing to update or delete one. And every search adds a step, which makes the Zap multi-step and needs a paid plan.
Weighing the tool first? Read our Zapier review, or open our Make vs Zapier comparison.
Zapier words, in plain English
Eight terms come back on this page. Each one is explained once, here, so the rest of the page can use them freely.
- 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. With MtnStudio, it always comes from another app.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you. Here, sending a lead.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling vs instant trigger
- A polling trigger is checked by Zapier at a fixed interval; an instant one is reported by its app the moment the event happens.
- Search step
- A step that looks up something that already exists in an app, so the steps that follow can use what it found.
- 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, a filter or a search makes one, and it then needs a paid plan.
What it really costs
MtnStudio is not one of the apps Zapier keeps for paid plans, so a simple Zap works from the free plan.
- TriggerFree, never counted
- Each lead sent1 task
- Free plan100 tasks a month, two-step Zaps
- Search, filter or second actionPaid plan
The trigger of your other app never costs a task. Each lead sent successfully counts as one task, 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. That covers a trigger plus a lead. Add one of the four searches, a filter or a second action, and the Zap becomes multi-step, which needs a paid plan. The grid below is how often Zapier checks a polling trigger; it applies to the app that starts your Zap, if its trigger works that way.
Connect MtnStudio to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your MtnStudio account linked to Zapier once, then reused by every step that uses MtnStudio.
- 02
Find MtnStudio
Type MtnStudio in the search box of the dialog that opens, pick it from the results, then click Add connection. A new tab then opens where you sign in.
- 03
Sign in and grant access
Sign in to MtnStudio 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.
Your first Zap: only the form leads you want, into MtnStudio
GoalSend new form responses to MtnStudio as leads, but only the ones that meet a condition you choose.
- 01
Set the trigger
Start a new Zap, pick your form tool and its new-submission event, connect the account and choose the form. Test the trigger and read the sample response it brings back.
- 02
Add the filter
Click the plus icon, add Filter, then set the field to check, the rule and the value. A filter makes this a multi-step Zap, so it needs a paid plan.
- 03
Add the lead action
Add MtnStudio with Send Lead to MtnStudio. Map the name and the email from the form, answer the opt-in question, then set the origin, the paid media and the campaign fields.
- 04
Test the lead step
Run the test of the MtnStudio step and read what came back before going further. If a value is missing, fix the mapping and test the step again.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new form response that passes the filter reaches MtnStudio as a lead, at one task per lead sent.
The MtnStudio actions
MtnStudio gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Lead to MtnStudio
ActionIn Zapier“Create a new lead in MtnStudio.”
Creates a lead in MtnStudio from the details an earlier step carried, along with your answers to its origin, paid media and campaign questions.
Send Lead Using Lead Generator
ActionIn Zapier“Sends a Lead to a Specific Lead Generator.”
Sends a person to one specific lead generator in MtnStudio, rather than as a plain lead.
The MtnStudio searches
4 search steps look for data that already exists in MtnStudio, so a later step can use it.
A search step fetches something that already exists in MtnStudio and hands it to the next steps. In the editor, the searches sit at the bottom of the Action event list, under SEARCH. Whether a search needs the exact value is decided by MtnStudio, not Zapier. MtnStudio exposes no find-or-create variant on Zapier. Three settings decide what happens when the result is not the expected one.
Find Client and Token
SearchIn Zapier“Busca o client e retorna o token”
Looks up one of your MtnStudio clients from its Client ID and passes what it finds, its token included, to the steps after it.
Find Generator
SearchIn Zapier“Find and persist Generator info from MtnStudio.”
Fetches the details of a lead generator from MtnStudio so the rest of the Zap can reuse them.
Find Product
SearchIn Zapier“Find and persist Product ID and name from MtnStudio.”
Retrieves a product's ID and name from MtnStudio, ready to be mapped into a later step.
Find Send Type
SearchIn Zapier“Find and persist Send Type from MtnStudio.”
Brings back a send type stored in MtnStudio, so the steps after it can work with that value instead of a typed one.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns a search into a find-or-create, which stops offering the setting above and asks for the fields needed to create the missing item.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When the Zap breaks
Zapier attaches no help article of its own to MtnStudio, so the cases below are the general Zapier limits that touch these operations.
When a Zap stops behaving, start from these cases. For a step-by-step method, see our Zapier troubleshooting guide.
Old contacts never become leads
A Zap only reacts to what happens after it is switched on. Responses or contacts that existed before you published are not sent; moving that backlog is a separate job.A big batch gets held back
When the app that starts the Zap 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.
Need help automating MtnStudio with Zapier?
A person reads every message.
