Divi Checkout Zapier integrationAutomate Divi Checkout with Zapier.
Divi Checkout Zapier integration: 2 triggers, 0 actions and 0 searches. Each new order or new product in your Divi Checkout store can start a Zap that hands it to a spreadsheet, a CRM or your team chat, without copying anything by hand.
Verified Trustpilot reviews · AI, automation & growth agency
What the Divi Checkout Zapier integration is for
The Divi Checkout Zapier integration links the checkout module of your Divi site to Zapier, a tool that chains apps together without code. When an order or a product appears in Divi Checkout, Zapier picks it up and passes it to your other tools, so nobody has to retype it.
Three results cover most uses. First, a sales log that fills itself: New Order adds each sale to a spreadsheet your accountant can open. Second, a sale alert for the team: the same trigger can post a message in your chat tool, so the person who ships the goods knows right away that there is work. Third, a catalog that stays in sync: New Product copies every product you add into a stock sheet or a product list held elsewhere.
Now the limits. Divi Checkout only sends data out: there is no action, so a Zap cannot create an order, a product or a discount inside it. There is no search either, so a Zap cannot look up an existing order. Both triggers work by polling, which means Zapier checks the store on a timer, and on the free plan that check comes every 15 minutes. An order placed just after a check waits for the next one.
Still weighing Zapier against other platforms? Read our Make vs Zapier comparison next to the Zapier review.
The Zapier words used on this page
Seven terms come back throughout the page. Here they are in plain language.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap, such as a new Divi Checkout order. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, here always in another app.
- 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, keeping only the items it has not seen yet. Both Divi Checkout triggers work this way.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
What a Divi Checkout Zap costs
Zapier bills tasks. The Divi Checkout trigger is free; only what the Zap does next counts.
- Trigger0 tasks
- Successful action1 task each
- Free plan100 tasks a month, 2-step Zaps
- Premium appNo, works on the free plan
Each action that succeeds is one task, and a failed action is not counted. Checking the store for new orders costs nothing, however often Zapier looks. A Zap that writes each order to one sheet uses one task per order; add a chat message and it is two. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stays at two steps, one trigger and one action. A filter, say to keep only large orders, makes it multi-step and needs a paid plan. Divi Checkout is not a premium app, so it runs on the free plan, where checks come every 15 minutes.
Connect Divi Checkout to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. Search for Divi Checkout in the dialog and pick it. You need a working Divi Checkout account first.
- 02
Sign in to Divi Checkout
Click Add connection. A tab opens on Divi Checkout: sign in with the account that runs the store. If the site belongs to a client or a colleague, get access from them before this step.
- 03
Grant access
Let Zapier use the account. The connection then appears on the Apps page, and every Zap step that uses Divi Checkout reuses it without asking you to sign in again.
Your first Divi Checkout Zap: every order in a sales sheet
GoalEach time a customer completes a purchase through Divi Checkout, add a row with the order details to a shared sales sheet.
- 01
Create the Zap
In Zapier, start a new Zap. The editor opens on an empty trigger card at the top, waiting for an app and an event to watch.
- 02
Pick the trigger
Choose Divi Checkout, then
New Order, and select the connection you made earlier. Both Divi Checkout triggers are polling ones, so on the free plan Zapier looks at the store every 15 minutes. - 03
Test with a real order
Run the test. Zapier brings back the three most recent orders of the store, so you can pick a real one and see which details come through.
- 04
Add the spreadsheet step
Add the sheet as the action and match each column to an order detail from Divi Checkout. Test it once and look at the row it creates before going on.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new order lands in the sheet at the next check, for one task per order.
The 2 Divi Checkout triggers
2 events start a Zap when something happens in Divi Checkout. Zapier checks for them at the interval your plan allows.
New Order
Polling triggerIn Zapier“Triggers when a new order is created.”
Starts the Zap when a customer places a new order through Divi Checkout. The order then travels to wherever you need it: a sales sheet, a CRM, an invoicing tool or a message to whoever packs the box.
New Product
Polling triggerIn Zapier“Triggers when a new product is created.”
Fires when you add a product in Divi Checkout. Instead of updating a second catalog by hand, the Zap copies each new item there as soon as Zapier spots it on its next check.
When a Divi Checkout Zap breaks
Zapier lists no help article and no specific limit for Divi Checkout. What goes wrong comes from Zapier's general rules.
Four situations account for most surprises. Read them before you publish. If a Zap still misbehaves, head to our Zapier troubleshooting page.
Past orders never show up
A Zap only reacts to what happens after it is switched on. Orders and products already in Divi Checkout are not picked up; moving them is a separate job.An order arrives a few minutes late
Both triggers are polling ones. On the free plan Zapier checks every 15 minutes, so an order can wait up to that long before the Zap runs.A big batch is held back
If many products appear at once, after an import for example, Zapier's flood protection can hold the batch back instead of running each one.The same order twice? Not here
Zapier remembers what it has already seen on a polling trigger, so one order does not start the Zap twice, even across several checks.
Need help automating Divi Checkout with Zapier?
A person reads every message.
