MYFUNDBOX Zapier integrationAutomate MYFUNDBOX with Zapier.
MYFUNDBOX Zapier integration: 1 trigger, 0 actions, 0 searches. MYFUNDBOX can start a Zap (an automation on Zapier) each time a payment goes through, and nothing more. What happens next, a row, a message, an email, is done by the other apps you add.
Verified Trustpilot reviews · AI, automation & growth agency
What the MYFUNDBOX Zapier integration actually does
It turns a payment in MYFUNDBOX into a starting signal for other apps. MYFUNDBOX is a platform to accept, process and manage subscription billing. On Zapier it offers one event, New Payment, which fires when a payment is successfully done. Every Zap you build with it starts there and continues somewhere else.
Three results you can build on that single trigger. A payment log that keeps itself: each successful payment adds a row to your spreadsheet, so the list of who paid is never one export behind. A heads-up for the team: each payment posts a message in your team chat, and nobody has to open MYFUNDBOX to know it came in. A new record in your database: each payment becomes an entry there, ready for whatever you do with it next.
Now the limits. MYFUNDBOX has no action on Zapier, so a Zap cannot create, change or cancel anything inside MYFUNDBOX. It has no search either, so another app's Zap cannot look up a payment or a subscriber there. And New Payment is a polling trigger: Zapier checks for new payments on a timer instead of being told the moment one happens. On the free plan that check runs every 15 minutes.
So the integration is a one-way feed out of MYFUNDBOX. If you are still choosing between tools, see our Make vs Zapier comparison.
The Zapier words you need, in one minute
Eight terms come back on every Zapier screen. Here they are in plain English, so the rest of the page reads without a dictionary.
- 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. Once the Zap is on, Zapier waits for it. With MYFUNDBOX, it is New Payment.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, always in another app here.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number 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 the ones it has not seen.
- Instant trigger
- A trigger the app reports itself, the moment the event happens, so nothing waits for the next check. MYFUNDBOX has none.
- 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 it one, and it then needs a paid plan.
What a MYFUNDBOX Zap really costs
MYFUNDBOX is not a premium app, so it works from the free plan. The trigger is free; what you pay for, in tasks, is what the other apps do afterwards.
- Premium appNo, works on the free plan
- Tasks on the free plan100 per month
- Steps per Zap on the free plan2 (one trigger, one action)
- Cost of New Payment0 tasks
New Payment never costs a task, and neither do Zapier's checks, however often they run. Each action that succeeds afterwards counts as one task, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. How often New Payment is checked depends on your plan, as the grid shows.
Connect MYFUNDBOX to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is made once, then every Zap that starts on a MYFUNDBOX payment reuses it.
- 02
Find MYFUNDBOX and add it
Type MYFUNDBOX in the search box of the dialog, pick it from the results, then click Add connection. A new tab opens so you can sign in to the account.
- 03
Sign in and grant access
Sign in to MYFUNDBOX in that tab and grant Zapier access to 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: every payment logged in a spreadsheet
GoalEach successful MYFUNDBOX payment adds a row to your spreadsheet. Two steps only, so this Zap runs on the free plan.
- 01
Pick the trigger
Create a Zap, choose MYFUNDBOX as the app that starts it and New Payment as the event. Select your MYFUNDBOX connection, or add it now.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent payments of the connected account, so you map the next steps on a real one.
- 03
Add the spreadsheet action
Choose your spreadsheet app and its new-row action, then map the payment fields you want into the columns. Check at the test which fields the payment really carries.
- 04
Test, then publish
Test the action once and open the sheet to read what came back. If the row looks right, click Publish to switch the Zap on.
The MYFUNDBOX trigger
1 event starts a Zap when something happens in MYFUNDBOX. Zapier checks for them at the interval your plan allows.
New Payment
Polling triggerIn Zapier“Triggers when the payment is successfully done.”
Starts your Zap when a payment in MYFUNDBOX is successfully done, so the apps that follow can record it, announce it or file it somewhere useful.
When a MYFUNDBOX Zap breaks
Zapier links no help article to MYFUNDBOX, so the cases below are the general limits of every Zap, seen through New Payment.
Each case has a clear fix once you know where to look. For a step-by-step method, see our Zapier troubleshooting guide.
Earlier payments are not sent
A Zap only reacts to what happens after you switch it on. Payments already in MYFUNDBOX stay out of your sheet; moving that backlog is a separate job.A payment arrives after a wait
New Payment is a polling trigger. Zapier checks on a timer set by your plan, every 15 minutes on Free, so a payment shows up at the next check.A big batch 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 payment, not twice
On a polling trigger, Zapier keeps track of what it has already seen, so the same payment does not start the Zap twice.
Need help automating MYFUNDBOX with Zapier?
A person reads every message.
