Momindum Zapier integrationAutomate Momindum with Zapier.
The Momindum Zapier integration gives you 1 trigger, and no action or search. New Scoring checks Momindum on a timer and passes each new scoring to your other tools. Nothing writes back into Momindum, and a two-step Zap runs on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Momindum Zapier integration actually does
The Momindum Zapier integration takes what happens in Momindum, the video presentation software for training, learning and online communication, and passes it to your other tools. It does one thing: when a new scoring is added in Momindum, it starts a Zap. You set that Zap up once, and it runs while it is switched on.
Three results people build from that one trigger. A results sheet that fills itself: New Scoring adds a row to a spreadsheet for every new scoring, so nobody exports them by hand. A message to the team: the same trigger posts in your team chat, so a new scoring is seen without opening Momindum. A copy in another tool: the scoring details the trigger test shows are mapped into a note or a field of the tool you choose. Testing the trigger brings back the three most recent scorings of the account, so you see what each one carries before mapping it.
What Zapier does not do here. There is a single trigger and nothing else. No action, so no Zap can create, change or send anything in Momindum: data only leaves it. No search either. And the trigger polls: Zapier checks Momindum at an interval set by your plan, so a scoring never reaches the Zap at the exact moment it is added.
Choosing between tools? See our Make vs Zapier comparison. Rather learn Zapier properly first? There is our Zapier training.
Zapier vocabulary in one minute
A few words come back on every line below. Here they are in plain English, once.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, like a new scoring in Momindum. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes or sends something. With Momindum, the actions belong to other apps.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer; an instant one is reported by the app itself. New Scoring polls.
- Filter
- A step that lets the Zap go on only when what arrived meets a 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.
What a Momindum Zap really costs
Momindum is not a premium app on Zapier, so it works on the free plan. You pay in tasks, never in checks.
- Free plan100 tasks a month, unlimited Zaps of two steps
- Premium appNo, Momindum works on the free plan
- What countsEach successful action after the trigger
New Scoring itself costs nothing, however often Zapier looks at Momindum. Each action that follows and succeeds counts as one task, and one that fails is not counted. A Zap with three actions uses three times what a one-action Zap uses, and a few apps and actions take more than one. The free plan stops at two steps: a filter or a second action makes the Zap multi-step, so paid. The grid shows how often New Scoring is checked, by plan.
Connect Momindum to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. You need a Momindum account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Momindum
Search for Momindum in the dialog, select it and click Add connection. A new tab opens where you sign in to Momindum with the account whose scorings you want to follow.
- 03
Grant access
Sign in to Momindum in that tab and give Zapier access to the account. The connection is saved once, and every Momindum trigger you add later, in any Zap, reuses it.
Your first Momindum Zap: a results sheet and a heads-up
GoalEach time a new scoring is added in Momindum, add it to your spreadsheet and post a short message to the team.
- 01
Create the Zap
Start a new Zap and pick Momindum as the app that starts it. With two actions after the trigger, this is a multi-step Zap and needs a paid plan.
- 02
Set the trigger
Choose New Scoring and your Momindum connection. Test it: Zapier brings back the three most recent scorings of the account, so you map on real data.
- 03
Add the row
Add your spreadsheet step and put what the test returned into the right columns. Check at the test which details the scoring actually carries.
- 04
Post the message
Add your team chat step and write a short message using a couple of the scoring details, so the team sees the new scoring without opening Momindum.
- 05
Publish
Run each step once and read what came back, then publish the Zap to switch it on. From then on, each new scoring goes through once.
Momindum triggers on Zapier
1 event starts a Zap when something happens in Momindum. Zapier checks for them at the interval your plan allows.
New Scoring
Polling triggerIn Zapier“Triggers when new scoring is added.”
Starts a Zap each time a new scoring is added in Momindum. It is the only operation of this integration, so every Momindum Zap begins here and sends the scoring on to another app.
When a Momindum Zap breaks
Zapier lists no Momindum-specific limit or error for this integration. What goes wrong comes from how Zapier itself works.
Here are four general limits to know. They do not show while you build; they appear once the Zap is live and real scorings go through it. If one of them hits you, open our Zapier troubleshooting page.
Nothing from before
A Zap only reacts to what happens after it is switched on. Scorings added before are never picked up; moving that history is a separate job.A Zap that restarts itself
A Zap that writes into the very place its own trigger watches can set itself off again and again, and burns through your tasks. Keep the two apart.Flood protection
If New Scoring suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.The same item twice
Zapier keeps track of what it has already seen on a polling trigger, so the same Momindum scoring does not start the Zap twice.
Need help automating Momindum with Zapier?
A person reads every message.
