PickPack Zapier integrationAutomate PickPack with Zapier.
The PickPack Zapier integration gives you 0 triggers and 1 action. That single action creates an order task in PickPack, so a sale, a form or a spreadsheet row in another app becomes a delivery job without anyone typing the order again.
Verified Trustpilot reviews · AI, automation & growth agency
What the PickPack Zapier integration does, and what it cannot
PickPack is a delivery management platform: it organises the orders your drivers or couriers have to carry out. Zapier is the service that chains apps together. The integration lets another app hand orders to PickPack: something happens there, and Zapier creates the matching task in your PickPack account.
Three results people set up. Shop orders turned into deliveries: a new order in your online shop runs Create Task, and the job is waiting in PickPack. Phone and form orders in the same queue: a booking form or a row added to a shared sheet goes through the same action, so orders taken by hand stop living in a separate list. A daily project filled on its own: with the Open Daily Projects option, each task joins a project that PickPack creates for the day, which keeps a day's deliveries together.
What Zapier does not do for this app. PickPack has no trigger on Zapier, so nothing that happens in PickPack can start a Zap: a delivered or failed task tells your other apps nothing through this integration. There are no searches either, so a Zap cannot look up an existing order, and there is no action to update or cancel a task once it is created. It is one-way traffic, from your tools into PickPack.
For a wider view of the platform, see Zapier review, and for the choice of tool, Make vs Zapier.
Zapier words, explained once
Before opening the editor, here is the vocabulary this page relies on. Each word is used as defined here from then on.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run every time that event comes back.
- Trigger
- The event in an app that starts the Zap. PickPack offers none, so your Zap always starts in another app.
- Action
- The step the Zap carries out once started. Here, the one PickPack action creates an order task for you.
- Task
- What Zapier bills: one action that went through. Each PickPack order created by a Zap counts as one of them.
- Polling vs instant
- Zapier checks a polling trigger on a timer; an instant trigger is reported by its app straight away. Your starting app decides which.
- Filter
- A step that lets the Zap carry on only when the incoming data meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap with more than one trigger and one action; a filter or a second action makes one, and it needs a paid plan.
What a PickPack Zap costs
PickPack is not a premium app on Zapier, so it works on the free plan. What you pay for is each task PickPack actually receives.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap shapeTwo steps: one trigger, one action
- One order sent to PickPackOne task
- Failed actionNot counted
The trigger of your starting app never costs a task, and a Create Task that fails is not counted. Each order that reaches PickPack is one task, so your monthly count simply follows your delivery volume. The free plan builds two-step Zaps only: your trigger plus Create Task. Put a filter in between, to send only orders that need delivery, and the Zap becomes multi-step, which needs a paid plan. How fast the Zap reacts depends on your starting trigger: if it is polling, the plan grid below applies; if it is instant, it does not.
Connect PickPack to Zapier in 3 steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your PickPack account linked once, then reused by every PickPack step.
- 02
Choose PickPack
Type PickPack in the dialog search, pick it, then click Add connection. You need a PickPack account, with write access to wherever the Zap should create tasks.
- 03
Sign in and allow access
A new tab opens on PickPack. Sign in with the account your operations team uses, then grant Zapier access. The connection is then offered in every Create Task step.
Your first Zap: shop orders that need delivery go to PickPack
GoalWhen an order arrives in your shop, keep only those to deliver and create the matching task in PickPack.
- 01
Start from your order tool
Create a Zap and pick the app where orders arrive, with its new-order event, as the trigger. PickPack has no trigger, so the Zap always starts outside it.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map PickPack on a real order with a real phone number.
- 03
Add a filter
Add a Filter step from the plus icon and set the field to look at, the rule and the value, so pickups in store never reach PickPack. This makes the Zap multi-step.
- 04
Set up Create Task
Add PickPack with
Create Task. Pick the timezone that applies to every date of the order, then map the phone number from the order. - 05
Test, then publish
Test the step once and check the task in PickPack. When it looks right, click Publish to switch the Zap on for the orders that follow.
The PickPack action
PickPack gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Task
ActionIn Zapier“Create Order Task”
Creates an order task in PickPack from the data of another app, ready to be dispatched to a driver.
When a PickPack Zap breaks
Zapier publishes no help article and no limit specific to PickPack. What goes wrong comes from the way Zapier works, and four cases cover most of it.
Each one comes from how Zapier works, not from PickPack, and most of them leave you with a task that simply never appears. When a run fails outright, Zapier troubleshooting lists the usual fixes.
Orders from before never arrive
A Zap only reacts to what happens after you switch it on. Orders already in your shop stay out; moving them into PickPack is a separate job.The Zap stops on a missing phone
Phone is a required field of Create Task. An order without a number cannot become a task, so that run stops and the delivery never shows up.A big import is held back
When your starting trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the runs back.Dates land at the wrong hour
The Timezone you pick applies to every date field of the task. Choose the one your orders are written in, or scheduled times shift.
Need help automating PickPack with Zapier?
A person reads every message.
