Kutetailor Zapier integrationAutomate Kutetailor with Zapier.
The Kutetailor Zapier integration gives you 2 triggers, 0 actions and 0 searches. It works outward only: a new custom order or a status change in Kutetailor starts a Zap, and your other tools (sheets, chat, email, invoicing) take it from there, straight away.
Verified Trustpilot reviews · AI, automation & growth agency
What the Kutetailor Zapier integration is good for
Kutetailor is an order management platform for made-to-order production, where teams create orders and follow their status. On Zapier it acts as a source of events: when an order is saved or its status moves, Kutetailor tells Zapier at once, and the rest of your tools react without anyone copying order details by hand.
Three results workshops usually build. A live order log: New Order adds a row to a shared sheet for every order saved, so the office and the workshop read the same list. Status updates customers can see: Update Status sends an email or a text through another app when an order changes stage. A cleaner handover to accounting: each new order creates a draft in your invoicing tool, ready to check.
What Zapier does not do here. Kutetailor has no action and no search on Zapier, so a Zap cannot create an order in Kutetailor, change its status or look one up. Everything flows out of Kutetailor, never back in. Orders saved before your Zap was published are not replayed either. In short, Kutetailor tells the world what happened, and the rest of the work lives in the apps that listen to it.
If you are new to building these flows, our Zapier training is a good place to start, and the n8n vs Zapier comparison is worth a read before choosing a platform.
Zapier vocabulary in one minute
Seven words come back across this page. Here is what each one means in practice.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, like a new order in Kutetailor. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or creates something in another app. Kutetailor itself has none.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment the event happens.
- Filter
- A step that lets the Zap go on only when the data that arrived meets your condition, and stops it everywhere else.
- Search step
- A step that looks up something that already exists in an app so later steps can use it. Kutetailor offers none.
What a Kutetailor Zap really costs
Kutetailor is not a premium app on Zapier, so it runs on the free plan.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap sizeTwo steps: one trigger, one action
- Premium appNo, works on the free plan
- TriggersBoth instant, the interval grid does not apply
Both Kutetailor triggers are free: a trigger never costs a task, and waiting for events costs nothing either. What you pay for is the action in the other app, one task each time it succeeds; a failed action is not billed. Both triggers are instant, so the plan interval grid does not apply to them. The free plan stops at one trigger and one action, so a Zap that filters only some statuses, or both logs and emails, needs a paid plan.
Connect Kutetailor to Zapier in 3 steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. A connection is your Kutetailor account linked once, then reused by every Zap that listens to it.
- 02
Pick Kutetailor
Type Kutetailor in the search box of the dialog, select it, then click Add connection. A new tab opens on the Kutetailor side so you can sign in there.
- 03
Sign in and grant access
Log in to Kutetailor in that tab and allow Zapier to use the account. You need your own account, plus access to the orders you did not create but want your Zaps to hear about.
Your first Zap: keep customers posted when an order moves
GoalEvery time an order status changes in Kutetailor, the customer gets a short email about it.
- 01
Create the Zap
Start a new Zap, choose Kutetailor as the app that starts it and Update Status as the event. Connect your Kutetailor account when Zapier asks for it.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent items of the connected account, so you can map fields on a real order rather than an empty one.
- 03
Pick the statuses
A filter that lets through only the status you want to announce keeps customers from receiving every internal step. It makes the Zap multi-step, which needs a paid plan.
- 04
Write the email
Add the email step and map into it the order details the customer needs to see. Test it once on yourself and read what came back.
- 05
Publish
Click Publish to switch the Zap on. Status changes from then on start it straight away, whatever your plan; earlier ones are ignored.
Kutetailor triggers on Zapier
2 events start a Zap when something happens in Kutetailor, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Order
Instant triggerIn Zapier“Triggers when a new order is saved on kutetailor.”
Starts your Zap each time an order is saved in Kutetailor, and hands its details to the steps that follow. It is the entry point for anything that should happen once per order: logging, invoicing, telling the workshop.
Update Status
Instant triggerIn Zapier“Triggers when an order status is updated.”
Wakes the Zap whenever an existing order moves to another status in Kutetailor, rather than when it is first created. This is the event to follow when the progress of the work matters more than its arrival.
When a Kutetailor Zap breaks
Zapier links no help article to Kutetailor. The cases below are the general limits every Zap shares, read through an order tool.
Because Kutetailor only sends events out, most problems sit in the step that receives them. Our Zapier troubleshooting page is the next place to look.
No backlog
A Zap reacts only to orders saved or changed after you publish it. Earlier orders never start it; moving them to another tool is a separate job.Too many status messages
Update Status fires on every change. Without a filter on the new status, a customer can receive a message for each internal step of their order.Bulk imports held back
Loading many orders at once can produce a sudden flood of events, and Zapier's flood protection can hold that batch back instead of running it all.Loops through other apps
If the receiving app feeds orders back into Kutetailor by some other route, the Zap can set itself off again and burn through your task count fast.
Need help automating Kutetailor with Zapier?
A person reads every message.
