Luminous Zapier integrationAutomate Luminous with Zapier.
The Luminous Zapier integration gives you 9 triggers, 3 actions and 1 search across sales orders, purchase orders, stock, products, companies and contacts. Here is what each one does, what it costs in tasks, and the two details that catch most people out.
Verified Trustpilot reviews · AI, automation & growth agency
What the Luminous Zapier integration does for an online store
Luminous is an inventory tool for ecommerce brands: it follows stock across sales channels and warehouses, handles wholesale and keeps a small CRM of companies and contacts. Connecting it to Zapier lets its orders, stock movements and customer records reach your other tools, and lets those tools send companies, products and sales orders back in.
Three results come up most. An order log that keeps itself: New Sales Order copies each order into a sheet or a reporting tool, so nobody re-keys orders for the sales figures. A product catalogue kept in one place: Create / Update Product pushes products from another system into Luminous and updates the existing one when the SKU already exists, instead of piling up duplicates. A buying team that hears about purchase orders without asking: New Purchase Order passes each new purchase order to whoever receives the goods.
What Zapier does not do for Luminous: none of the nine triggers is instant, so every one waits for Zapier's next check. New Inventory Consumed goes further: Luminous groups that data by day and SKU, so it only reflects consumption up to the end of the previous day. There is no action for contacts or purchase orders, no delete, and the single search only finds companies.
If you are still choosing a platform, start with our Zapier review, then compare with n8n vs Zapier.
The Zapier words used on this page
Eight words carry everything below. Each is explained here once, then used as is.
- Zap
- The automation you build in Zapier: one trigger first, then one or more actions that run every time the trigger happens.
- Trigger
- The event in an app that starts the Zap, such as a new Luminous sales order. With the Zap on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you in an app.
- Task
- The unit Zapier bills: one action your Zap completed successfully. The number on your plan counts these and nothing else.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer and keeps only what is new. An instant trigger is pushed by the app as soon as it happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app, so the following steps can use what it found.
- Connection
- Your Luminous account linked to Zapier once, then reused by every step of every Zap that touches Luminous.
What Luminous on Zapier really costs
Luminous is not a premium app, so it works from the free plan up. The bill is counted in tasks, and only actions produce them.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps
- Luminous triggers9, all polling
- Failed actionNot counted
The trigger never costs a task, and neither do Zapier's checks on Luminous, however often they run. Each action that succeeds counts once; an action that fails is not counted. A Zap with two actions spends twice what a one-action Zap does. The free plan gives 100 tasks a month and unlimited Zaps, limited to two steps: one trigger and one action. A filter, a second action or the Find Company search makes the Zap multi-step, which needs a paid plan. The interval grid below applies to all nine Luminous triggers, since every one of them is a polling trigger.
Connect your Luminous account in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Luminous account, plus read or write access to anything you do not own but want the Zap to touch.
- 02
Choose Luminous
Type Luminous in the search box of the dialog, pick it from the results, then click Add connection. A new tab opens on the Luminous side for the sign-in.
- 03
Sign in and grant access
Log in to Luminous in that tab and allow Zapier to access the account. The connection then shows on your Apps page, and every Luminous step in every Zap reuses it.
Your first Zap: log every Luminous sales order
GoalEach new sales order created in Luminous that passes your filter lands as a row in your spreadsheet, ready for the sales figures without any export.
- 01
Create the Zap
From your Zapier dashboard, start a new Zap. The filter in the middle makes it a multi-step Zap, which needs a paid plan; without the filter, the two remaining steps fit the free plan.
- 02
Set the trigger
Choose Luminous as the app and New Sales Order as the event, then select the Luminous connection you added earlier from the list.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent sales orders of the account, so the mapping is done on a real order rather than a guess.
- 04
Add the filter
Click the plus icon under the trigger and choose Filter. Fill in the three boxes: the field to look at, the rule, and the value to compare with. Only the orders that pass reach the sheet.
- 05
Add the action
Pick your spreadsheet app and its new-row event, then drag the order details sent by Luminous into the matching columns of the sheet.
- 06
Test, then publish
Test the action once and check the row it wrote. Then click Publish: from that moment, each new sales order adds its own row.
Luminous triggers in Zapier
9 events start a Zap when something happens in Luminous. Zapier checks for them at the interval your plan allows.
Company Update
Polling triggerIn Zapier“When any company information is updated”
Runs the Zap when any piece of information on an existing company changes in the Luminous CRM. The updated company record travels to the next steps, so another tool can follow the change.
Contact Update
Polling triggerIn Zapier“When any contact information is updated.”
Reacts to an edit on an existing contact, the people attached to a company in Luminous. Whatever field changed, the whole updated contact reaches the Zap.
New Company
Polling triggerIn Zapier“Triggers when a new company is created”
Fires on each company added to the Luminous CRM, whether someone typed it in or a Zap created it. It is the natural start for anything that has to know about a new wholesale account.
New Contact
Polling triggerIn Zapier“Triggers when a new company contact is created”
Starts the Zap when a new contact is created for a company in Luminous. The contact comes with its link to the company, so the next step knows which account it belongs to.
New Inventory Consumed
Polling triggerIn Zapier“Triggers when inventory is consumed from a sale, adjustment, assembly or disassembly. Due to how the data is grouped by day and sku, the data will only be current as of end-of-day yesterday”
Reports stock that went out through a sale, an adjustment, an assembly or a disassembly. Luminous groups this data by day and by SKU before handing it over, so each item is a daily total rather than a single movement.
New Stock Update
Polling triggerIn Zapier“Triggers when the current stock changes for any SKU”
Goes off whenever the current stock of any SKU changes. Unlike the consumption trigger, it follows the live stock level, so it is the one to use when the number on hand matters.
New Purchase Order
Polling triggerIn Zapier“Triggers when a new purchase order is created.”
Triggers when a purchase order is created in Luminous, the order you place with a supplier. The purchase order reaches the next steps as soon as Zapier's check finds it.
New Product
Polling triggerIn Zapier“Triggers when a new product is created.”
Fires each time a new product appears in Luminous, including those created by a Zap through Create / Update Product. The product record is then available to every step that follows.
New Sales Order
Polling triggerIn Zapier“Triggers when a new sales order is created”
Each sales order created in Luminous starts the Zap and carries its details along. Orders created by the Create Sales Order action are included too.
Luminous actions in Zapier
Luminous gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Company
ActionIn Zapier“Creates a new company in the Luminous CRM”
Adds a company to the Luminous CRM from data caught by an earlier step.
Create / Update Product
ActionIn Zapier“Creates a new product in the system. If a product with the same SKU already exists, the product will be updated.”
Creates a product in Luminous, or updates the existing one when a product with the same SKU is already there.
Create Sales Order
ActionIn Zapier“Creates a new sales order in the system”
Creates a sales order in Luminous, so stock and order tracking start from an order placed elsewhere.
The Luminous search in Zapier
1 search step looks for data that already exists in Luminous, so a later step can use it.
A search step finds something that already exists in Luminous and passes it to the next steps. In the editor, searches sit at the bottom of the Action event list, under a SEARCH heading. Luminous has one, Find Company, and adding it makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when the search does not return exactly one company.
Find Company
SearchFind or createIn Zapier“Find a company in the Luminous CRM”
Looks a company up in the Luminous CRM and hands it to the steps after it. The editor also lists Find or Create Companies: it is this same search with the create box ticked, not a separate operation.
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 and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns Find Company into a find-or-create. The setting above disappears, and the step asks for what is needed to create the missing company.
- If multiple search results are found?Three ways out when several companies match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When a Luminous Zap breaks
Zapier attaches no help article to Luminous and records no limit specific to it. The trouble comes from how Zapier works with every app.
Four cases explain most surprises with a Luminous Zap. They rarely look like an error: more often a missing order, stale stock figures or a task counter racing up. If none of them fits, go to Zapier troubleshooting.
Existing orders never come through
A Zap only reacts to what happens after it is published. Orders, products and companies already in Luminous are not picked up; moving them is a separate job.Two Zaps feeding each other
Create Sales Order in a Zap started by New Sales Order fires the Zap again, then again. The loop burns through your monthly tasks fast.A bulk import held back
When a trigger suddenly returns a huge batch, after a catalogue import or a migration, Zapier's flood protection can hold those items back instead of running them all.An edit that never shows
Zapier tracks what it has already seen on a polling trigger, so the same order or product never starts a New trigger twice, even after an edit.
Need help automating Luminous with Zapier?
A person reads every message.
