MPU-Manager Zapier integrationAutomate MPU-Manager with Zapier.
The MPU-Manager Zapier integration gives you 2 triggers, 1 action and 1 search. New clients can start a Zap, other apps can create clients in MPU-Manager, and a search by email checks who is already there. Here is what it does, what it costs and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the MPU-Manager Zapier integration actually does
MPU-Manager runs in the browser and keeps the clients, appointments and documents of MPU preparation work in one place. Plugging it into Zapier lets client records travel without copy and paste: a new client in MPU-Manager can be passed to another app, and a client captured elsewhere can be created in MPU-Manager.
Three results you can build. A client list outside the platform: New Client sends each new record to a spreadsheet or another tool your team reads. Clients entered once: Create Client opens the record in MPU-Manager from data captured in another app, with first name, last name, email and the date the client joined. No duplicates on the way in: Client Search looks the person up by email first, and its find-or-create variant handles the case where nobody is found.
What Zapier does not do here. Appointments and documents are part of MPU-Manager, but no trigger or action touches them on Zapier. Nothing updates or deletes a client either. Both triggers poll, so neither is instant: a new client reaches the Zap at the next check of your plan. And List Team Members has a name and an official description that do not match; check at the test what it really returns.
Before picking a platform, see our Make vs Zapier comparison or our Zapier review.
Zapier words in one minute
Eight words you will meet in the editor, in plain English.
- 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 a Zap, such as a new client in MPU-Manager. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like creating a client.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer for new items; an instant one is reported by the app itself. Both MPU-Manager triggers poll.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found.
- 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 MPU-Manager on Zapier really costs
Zapier bills tasks, not checks. The trigger never costs a task, and looking for new clients is free however often Zapier looks.
- Free plan100 tasks a month, unlimited two-step Zaps
- MPU-Manager on freeYes, not reserved for paid plans
- Trigger checksNever billed
- Search, filter or second actionPaid plan required
Every action that succeeds counts once; an action that fails is not counted. MPU-Manager is not reserved for paid plans, so it works on the free plan: 100 tasks a month and unlimited Zaps, each limited to two steps. That limit matters here, because Client Search, a filter or a second action each turn the Zap into a multi-step one, which needs a paid plan. The grid below shows how often Zapier checks a polling trigger on each plan.
Connect your MPU-Manager account
- 01
Open Apps and add a connection
Go to the Apps page of your Zapier account and click + Add connection. You need an MPU-Manager account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick MPU-Manager
Search MPU-Manager by name in the dialog, select it and click Add connection. A new tab opens on the MPU-Manager sign-in screen, where the next step happens.
- 03
Sign in and grant access
Log in to MPU-Manager in that tab, then grant Zapier access to the account. Every MPU-Manager step in your Zaps reuses this connection afterwards, so it is a one-time job.
Your first Zap: log selected new clients in a spreadsheet
GoalWhen a client is created in MPU-Manager and passes a filter, add a row with their details to your spreadsheet.
- 01
Build: set the trigger
Create a Zap, choose MPU-Manager as the trigger app and
New Clientas the event, then select the MPU-Manager connection you made earlier. - 02
Test the trigger
Run the test. Zapier brings back the three most recent clients of the connected account, so the mapping is done on a real record rather than a blank one.
- 03
Add the filter
Click the plus icon, choose Filter, then set the field to look at, the rule and the value. A filter makes the Zap multi-step, so this step needs a paid plan.
- 04
Add the spreadsheet action
Add your spreadsheet app and its add-row action, connect the account that holds the sheet, then map the client fields to the columns you keep. Test it and read the row it wrote.
- 05
Publish
Click Publish to switch the Zap on. Only clients created after this point are sent; the ones already in MPU-Manager stay where they are.
MPU-Manager triggers
2 events start a Zap when something happens in MPU-Manager. Zapier checks for them at the interval your plan allows.
List Team Members
Polling triggerIn Zapier“Triggers when you select a team tember for client create”
Its name points to a list of team members, while its official description talks about choosing a team member when a client is created. The two do not match, so nothing here can tell you for sure what it sends.
New Client
Polling triggerIn Zapier“Triggers when a new client is created”
Starts a Zap each time a client is created in MPU-Manager and passes that record to the next step, so the rest of your tools learn about the person without anyone retyping the details.
MPU-Manager actions
MPU-Manager gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Client
ActionIn Zapier“Creates a new client with personal data, MPU reason, and optional address information.”
Turns data that arrived in another app into a client record in MPU-Manager, including why the person is preparing for the MPU and, when you have it, their address.
MPU-Manager search
1 search step looks for data that already exists in MPU-Manager, so a later step can use it.
A search step finds an existing record and passes it to the next steps. It sits at the bottom of the Action event list, under the SEARCH heading, and like any extra step it makes the Zap multi-step. Three settings decide what happens when the result is not a clean single match.
Client Search
SearchFind or createIn Zapier“Search and find a client by email and stop the workflow if they already exist.”
Looks a client up by email in MPU-Manager. Its official description adds that it stops the workflow when the client already exists, so check that behavior at the test step.
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 the search into a find-or-create: the setting above disappears and the step 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 MPU-Manager Zap breaks
Zapier lists no MPU-Manager-specific limit or error. What can go wrong comes from how every Zap works.
Four cases are worth knowing before you publish. If a Zap behaves oddly, our Zapier troubleshooting guide is the next stop.
Existing clients never show up
A Zap only reacts to what happens after it is switched on. Clients that already existed are not picked up; moving that backlog is a separate job.A Zap that keeps restarting
A Zap that writes into the place its own trigger watches can set itself off again and again, and eat tasks fast.A bulk import is held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.The same client twice? No
On a polling trigger Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating MPU-Manager with Zapier?
A person reads every message.
