Mainstack Zapier integrationAutomate Mainstack with Zapier.
The Mainstack Zapier integration gives you 1 trigger, 0 actions and 0 searches. That single trigger, Invoice Paid, is instant: the moment a client settles an invoice, a Zap can log it, announce it or thank the payer in another app. Here is how, and what it costs.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mainstack Zapier integration actually does for you
Mainstack lets creators, entrepreneurs and businesses show their work and sell products and services, with payment options around the world. Its Zapier integration does one thing: it tells Zapier when an invoice has been paid, so a payment can start work in another app without you checking your dashboard or copying the amount anywhere.
A payment log that fills itself. Invoice Paid starts a Zap each time money comes in, and the Zap adds a row with the invoice details to the spreadsheet where you follow revenue.
A team that hears about the money. The same trigger can post a short note in your team chat, so whoever handles delivery knows the client has paid and can start.
A thank-you that goes out on its own. Paired with your email tool, Invoice Paid can send the payer a personal message once their invoice is settled.
The trigger is instant: Mainstack tells Zapier as soon as the invoice is paid, so the polling interval of your plan never applies, even on the free one.
What Zapier does not do here: there is no action and no search for Mainstack. A Zap cannot create an invoice, change a product or look up a client in Mainstack; it can only react to a paid invoice. If you are still weighing platforms, see our n8n vs Zapier comparison.
The Zapier words you will meet on this page
A handful of terms come back on every Zapier page. Here they are in ordinary words.
- Zap
- The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts your Zap. Mainstack has exactly one: an invoice that has been paid.
- Action
- What the Zap does after it starts. With Mainstack, the action always happens in another app you connect.
- Task
- The unit Zapier bills. One action your Zap finishes successfully is one task; your plan counts those.
- Instant vs polling
- Instant: the app reports the event itself. Polling: Zapier checks on a timer. Invoice Paid is instant.
- Filter
- A step that lets the Zap carry on only when what arrived matches the condition you set, and stops it otherwise.
- Connection
- Your Mainstack account linked to Zapier once, then reused by every Zap that starts from a paid invoice.
What Mainstack really costs in Zapier
Mainstack is not a premium app, so it works from the free plan. The bill is counted in tasks, and only finished actions count.
- Free plan100 tasks a month, unlimited Zaps, two-step Zaps only
- Premium appNo, Mainstack runs on the free plan
- BilledEach successful action in the other app; the trigger is free
The trigger never costs a task: a paid invoice arriving from Mainstack is free. You pay for each action that succeeds in the other app, so logging a payment and messaging the team costs two tasks per invoice. A failed action is not billed. The free plan stops at two steps, one trigger and one action. The grid below is Zapier's polling interval by plan; it does not apply to Invoice Paid, which is instant on every plan.
Connect your Mainstack account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Mainstack account, plus access to anything you do not own yourself but want the Zap to read.
- 02
Pick Mainstack
Type Mainstack in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Mainstack side, where the rest happens.
- 03
Sign in and grant access
Log in to Mainstack in that tab and allow Zapier to reach the account. The connection is saved once, and every later Zap that starts from Mainstack picks it from a menu.
Your first Mainstack Zap, step by step
GoalEach time a client pays a Mainstack invoice, add a row with the payment details to the spreadsheet where you track revenue.
- 01
Create the Zap
Start a new Zap and pick Mainstack as the app that starts it, with Invoice Paid as the event. Choose the connection you saved earlier.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent paid invoices from your account, so you map the next step on a real payment.
- 03
Add the spreadsheet step
Add your spreadsheet app as the action, pick the event that adds a row, and drag each invoice field into the column where it belongs.
- 04
Test the action
Run the action test once and open the spreadsheet to check the new row. This two-step Zap fits inside the free plan as it stands.
- 05
Publish
Click Publish to switch the Zap on. Because the trigger is instant, each new payment goes through straight away; invoices paid before are not replayed.
The Mainstack trigger: what can start a Zap
1 event starts a Zap when something happens in Mainstack, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Invoice Paid
Instant triggerIn Zapier“Triggers when an invoice has been paid.”
Each time one of your Mainstack invoices is paid, this trigger hands the paid invoice to Zapier. It is the only event Mainstack exposes, so every Mainstack Zap starts here.
When a Mainstack Zap breaks
Zapier lists no help article and no app-specific limit for Mainstack. What goes wrong comes from how Zapier itself works.
Four situations account for most surprises. None throws a dramatic error; they show up as missing rows or a task count that climbs faster than planned. If one has you stuck, the Zapier troubleshooting page is the place to start.
Earlier payments are never sent
A Zap only reacts to what happens after you publish it. Invoices paid before that moment stay in Mainstack; filling in the backlog is a separate job.A huge batch is held back
If a lot of invoices come through at once, the trigger can return a huge batch. Zapier's flood protection may hold it back instead of running every item.A second action needs a paid plan
The free plan builds two-step Zaps only. A filter or a second action turns the Zap into a multi-step one, which needs a paid plan.Nothing can be changed in Mainstack
Mainstack has no action on Zapier. A Zap can read paid invoices but cannot create, edit or cancel anything in Mainstack; that work stays in the app.
Need help automating Mainstack with Zapier?
A person reads every message.
