Lumino Zapier integrationAutomate Lumino with Zapier.
The Lumino Zapier integration gives you 3 triggers, 0 actions and 0 searches: three payment events that Lumino pushes to Zapier the moment they happen. Data flows out of Lumino only. Here is what each trigger does, what it costs and where it trips people up.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lumino Zapier integration is for
Lumino is a payments platform for merchants: it processes transactions, keeps the payment methods of your buyers and records what happens to each payment. On Zapier, it acts as a source of signals. Three events (a payment created, a payment refunded, a payment whose status changed) can each start an automation in your other tools.
Three results justify the setup. A sales log that fills itself: New Payment adds every fresh payment to a sheet or a database, so whoever closes the books stops exporting files by hand. A refund alert: Refunded Payment warns the people who need to know, partial refunds included, before a customer writes in to ask. A status tracker: Updated Payment passes each change of status to the tool where your team follows orders, so nobody has to refresh the Lumino dashboard to see what moved.
Now what Zapier does not do for Lumino. There is no action and no search: a Zap can read from Lumino but never write into it, so you cannot create a payment, issue a refund or look a payment up from Zapier. Everything starts in Lumino and ends somewhere else. The upside is that all three triggers are instant, which is rare and matters a lot on the free plan.
Before you commit, our Zapier review is a good first read, followed by the Make vs Zapier comparison.
Zapier vocabulary, the one-minute version
Seven words are enough to follow the rest of this page. Each one is explained once, here.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event that starts the Zap, such as a new Lumino payment. Once the Zap is switched on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
- Task
- The unit Zapier bills: one action your Zap completed successfully. Your plan is a count of these, and of nothing else.
- Instant vs polling
- An instant trigger is pushed by the app the moment the event happens. A polling trigger is checked by Zapier on a timer instead.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your Lumino account linked to Zapier once, then reused by every Zap step that needs Lumino.
What Lumino on Zapier really costs
Lumino is not a premium app, so it runs on the free plan. You pay in tasks, and the Lumino side of the Zap produces none.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps
- Lumino triggersAll 3 instant, no task cost
- Failed actionNot counted
A trigger never costs a task. Only the actions that follow do: each one that succeeds counts once, and one that fails is not counted. A Zap that logs a payment and then posts a message spends two tasks per payment. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below is the one Zapier applies to polling triggers; it does not apply to the three Lumino triggers, which are all instant.
Connect your Lumino account in three steps
- 01
Go to the Apps page
In your Zapier account, open Apps and click + Add connection. You need a Lumino account, plus access to any payments you do not own yourself but want the Zap to see.
- 02
Find Lumino
Type Lumino in the search box of the dialog that opens, select it in the results, then click Add connection. A new tab opens on the Lumino side for the sign-in.
- 03
Sign in and grant access
Log in to Lumino in that tab and allow Zapier to access the account. The connection then appears on your Apps page, and every Lumino Zap you build reuses it.
Your first Zap: log every new Lumino payment
GoalEvery payment created in Lumino that passes your filter lands as a new row in your spreadsheet, so the sales log fills itself without a single export.
- 01
Create the Zap
From your Zapier dashboard, start a new Zap. With a filter in the middle it becomes a multi-step Zap, so it needs a paid plan; drop the filter and the two remaining steps fit the free plan.
- 02
Pick the trigger
Choose Lumino as the app and New Payment as the event, then select the Lumino connection you created a moment ago in the list.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent payments of the account, so you map the next step on a real payment rather than a guess.
- 04
Add the filter
Click the plus icon under the trigger and pick Filter. Set the three boxes: the field to look at, the rule, and the value to compare with. Only the payments that pass go on.
- 05
Add the action
Pick your spreadsheet app and its new-row event, then drag the payment details Lumino sent into the columns of your sheet.
- 06
Test and publish
Test the action once and check the row it created. Then click Publish: from that moment, each new Lumino payment adds its own row.
Lumino triggers in Zapier
3 events start a Zap when something happens in Lumino, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
New Payment
Instant triggerIn Zapier“Triggers when a new payment is created.”
Starts the Zap each time a payment is created in Lumino, and hands the payment details to the steps that follow. It is the natural starting point for anything that counts, logs or celebrates incoming money, since every transaction begins here.
Refunded Payment
Instant triggerIn Zapier“Triggers when a payment is refunded (full or partial).”
Goes off when a payment is refunded, whether the refund covers the full amount or only part of it. The Zap receives the refunded payment and can warn whoever handles the follow-up, from accounting to customer service.
Updated Payment
Instant triggerIn Zapier“Triggers when a payment status is updated.”
Fires whenever the status of an existing payment changes in Lumino. It is the one to watch when the outcome of a payment matters more than its creation, because each move of status reaches the Zap as its own event.
When a Lumino Zap breaks
Zapier attaches no help article to Lumino and documents no limit of its own. The problems come from how Zapier works in general.
Three cases explain most surprises with a Lumino Zap. They rarely show up as an error message; they show up as a missing row or a task counter climbing faster than expected. If none of them matches, open Zapier troubleshooting.
Past payments never arrive
A Zap only reacts to what happens after you publish it. Payments already recorded in Lumino are not picked up; moving that history is a separate job.A big batch gets held back
When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.Refund counted as a full one
Refunded Payment also fires on partial refunds. A Zap that treats every refund as a full one will put wrong figures in your records.
Need help automating Lumino with Zapier?
A person reads every message.
