OpenPO Zapier integrationAutomate OpenPO with Zapier.
The OpenPO Zapier integration gives you 4 triggers, 1 action and 0 searches on the sheets of your supply chain workspace: new, deleted or edited rows can start a Zap, and Zapier can add a row to any sheet from another app.
Verified Trustpilot reviews · AI, automation & growth agency
What the OpenPO Zapier integration actually does
OpenPO is a collaboration platform where companies and their partners manage orders, stock and logistics, organised in spaces and sheets. The Zapier side connects those sheets to your other tools without code: a Zap (the automation you build on Zapier) reacts to changes in a sheet, or fills one from elsewhere.
Three results come up most. Nobody misses a new line: New Row starts the Zap when a row lands in a sheet, and the next step tells the buyer, the warehouse or the supplier. Changes that travel: Update Cell follows the fields you pick, and Remove Row reports deleted rows, so another tool stays in step with OpenPO. Orders that arrive on their own: Create Row adds a row to a sheet when a form, a shop or a CRM records something.
The limits are worth knowing upfront. All four triggers work by polling, so nothing reacts instantly. There is one action only: Zapier cannot edit or delete an existing row, and it has no search step to find one. A fourth trigger, Get Fields, returns the fields of a sheet rather than a business event, which makes it a niche tool. Every operation also asks for a space name and a sheet name, so your workspace has to be organised before you automate it.
For the wider picture, see n8n vs Zapier and our Zapier review.
Zapier vocabulary in one minute
Seven words carry the whole page. Each is explained once here, then used as is.
- Zap
- The automation itself: 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 that event and nothing else.
- Action
- What the Zap does after it starts: the step that creates, sends or writes something on your behalf.
- Task
- The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself, with no wait for a check.
- Filter
- A step that lets the Zap continue only when the incoming item meets your condition, and stops it there otherwise.
- Connection
- Your OpenPO account linked to Zapier once, then reused by every step of every Zap that touches OpenPO.
What an OpenPO Zap really costs
Zapier bills tasks, not Zaps. The four OpenPO triggers never cost a task, and Zapier checking your sheets costs nothing either, however often it looks.
- TriggerNever costs a task
- Action that succeeds1 task each
- Action that failsNot counted
- Free plan100 tasks a month, two-step Zaps only
Each action that succeeds counts once: a Zap that posts a new row to a channel and then emails a supplier uses two tasks per row. An action that fails is not counted. OpenPO is not reserved to paid plans, so it works on the free plan, with 100 tasks a month and unlimited Zaps. The catch: the free plan only builds two-step Zaps, one trigger and one action. A second action or a filter makes it multi-step, and that needs a paid plan. As every OpenPO trigger is a polling one, the interval grid below sets how fast your Zaps react.
Connect OpenPO to Zapier in 3 steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. You need an OpenPO account first, plus access to any space or sheet you do not own and want a Zap to read or fill.
- 02
Pick OpenPO
Type OpenPO in the search box of the dialog, select it, then click Add connection. Zapier opens a new tab so that you sign in directly on OpenPO's own side.
- 03
Sign in and grant access
Log in to OpenPO in that tab and allow Zapier to use the account. The connection is then saved once and offered again in every later step that uses OpenPO.
Your first OpenPO Zap
GoalEach new row in an OpenPO order sheet is shared with the team and sent to the supplier.
- 01
Build: choose the trigger
Create a Zap, pick OpenPO as the starting app and New Row as the event. Select your connection, then the space name and the sheet name to watch.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent rows of that sheet, so you map the next steps on a real order rather than a blank.
- 03
Add the channel message
Add the action of your team chat and map the columns of the row into the message, so the people who handle orders see the line without opening OpenPO.
- 04
Add the supplier email
Add the email action and map the same row into the body. This second action turns the Zap into a multi-step Zap, so it needs a paid plan.
- 05
Test and publish
Test each step once and read what came back in both tools. When the message and the email look right, click Publish to switch the Zap on.
OpenPO triggers
4 events start a Zap when something happens in OpenPO. Zapier checks for them at the interval your plan allows.
Get Fields
Polling triggerIn Zapier“Returns the fields for selection.”
Returns the fields of the sheet you point it at, the columns rather than the rows. Zapier's own description says only that it returns fields for selection, so treat it as a utility, not as a signal that something happened in your orders.
New Row
Polling triggerIn Zapier“Triggers when a new row is added”
Starts a Zap each time a row is added to the sheet you choose, and passes its columns to the following steps. It is the natural starting point for an OpenPO Zap, since a new row usually means a new order, a new shipment or a new line of stock.
Remove Row
Polling triggerIn Zapier“Triggered when deleting rows”
Fires when rows are deleted from the chosen sheet. That makes it the way to tell another tool that an order line, a shipment or an item no longer exists in OpenPO, instead of letting the copy drift out of date.
Update Cell
Polling triggerIn Zapier“Triggered when modifying cells”
Reacts when cells are modified in the sheet, but only in the fields you select when setting it up. You can follow a single column or several at once, depending on what matters to the next step.
OpenPO actions
OpenPO gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Row
ActionIn Zapier“Creates a new row in a sheet within your workspace.”
Adds a new row to a sheet of your workspace, with the columns filled from earlier steps. You name the space and the sheet, then map the values.
When an OpenPO Zap breaks
Zapier attaches no help article to OpenPO and its listing documents no limit of its own. The breakdowns below come from how Zapier works, applied to shared sheets.
The usual suspects are Zaps that feed themselves and imports that land all at once. If a Zap behaves oddly, our Zapier troubleshooting page is the next stop.
Rows already there are ignored
A Zap only reacts to what happens after you publish it. Rows that were in the sheet before are never picked up: moving that backlog is a separate job.A sheet that feeds itself
New Row and Create Row on the same sheet: each new row starts the Zap, which adds a row, which starts it again, and your task count drains fast.A bulk import held back
Paste a large batch of rows at once, after an import or a migration, and Zapier's flood protection can hold the batch back instead of running it.Each row handled once
Zapier remembers what a polling trigger has already returned, so the same row does not start New Row twice, even if the sheet is checked again.
Need help automating OpenPO with Zapier?
A person reads every message.
