Linework Zapier integrationAutomate Linework with Zapier.
The Linework Zapier integration gives you 7 triggers, 0 actions and 0 searches. Bookings, cancellations, reschedules, deposits and new clients leave your tattoo studio's schedule for your other tools; Zapier reads Linework, it never writes into it.
Verified Trustpilot reviews · AI, automation & growth agency
What the Linework Zapier integration does for your studio
Linework is booking software for tattoo businesses: appointments, cancellations, no-shows and the day-to-day running of the studio. Through Zapier, what happens in that schedule can reach the rest of your tools without anyone retyping it. The integration is one-way: seven triggers that send Linework events out, on the free plan.
Every booking in your calendar. New Appointment fires as soon as a session is booked, and the next step can create the matching event in the calendar your team already reads.
Deposits logged as they come in. New Deposit Checkout Completed fires when a deposit is recorded, so a spreadsheet gets a new line without anyone copying it.
Changes nobody misses. Appointment Canceled and Appointment Rescheduled tell your team chat the moment a slot opens up or moves.
Six of the seven triggers are instant. The exception is Appointment Starts, which Zapier checks on a timer. And here is what Zapier cannot do with Linework: anything inside it. There is no action and no search, so no Zap can book, move or cancel an appointment, add a client, or look one up. There is no trigger for a no-show either. If you are weighing that one-way setup against other platforms, and what each would let you write back into Linework, see our Make vs Zapier page.
Zapier words you will meet on this page
Seven terms, each in plain words. Once explained, they are used as is.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. All seven Linework operations are triggers: they start Zaps, nothing more.
- Action
- What the Zap does once it has started. With Linework, every action happens in another app, since Linework has none.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is counted in tasks.
- Instant vs polling
- An instant trigger is pushed by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap go on only when the incoming data meets your condition, and stops it there otherwise.
- Connection
- Your Linework account linked to Zapier once, then offered to every Linework trigger in every Zap you build.
What a Linework Zap really costs
Zapier bills tasks, and only successful actions create them. Linework only triggers, so its own share is always free.
- Premium appNo, Linework runs on the free plan
- Free plan100 tasks a month, two-step Zaps
- Triggers7: 6 instant, 1 polling
- Failed actionNot billed
A trigger never costs a task, however often Zapier checks. The tasks come from the actions in your other apps: a booking that creates a calendar event uses one, and adding a chat message makes it two. A failed action is not charged. The free plan gives 100 tasks a month and two-step Zaps only, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below only concerns Appointment Starts; the six other Linework triggers are instant and ignore it.
Connect Linework to Zapier in three steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. You need a Linework account, plus access to any studio data you do not own yourself but want the Zap to read.
- 02
Pick Linework
Type Linework in the search box of the dialog and select it from the results. Then click Add connection; a new browser tab opens on the Linework sign-in screen, ready for your login.
- 03
Sign in and grant access
Log into Linework in that tab and allow Zapier to reach the account. The connection is stored once, and each Linework trigger you add later offers it in its account menu.
Your first Zap: put every new booking in your calendar
GoalEach appointment booked in Linework that meets your condition becomes an event in your calendar, so the whole team sees the studio's schedule in one place.
- 01
Start with New Appointment
Create a Zap, pick Linework and New Appointment as the trigger, then your connection. Test it: Zapier brings back the three most recent bookings so you map from a real one.
- 02
Add a filter
Click the plus icon and add Filter. Fill its three boxes: the booking field to look at, the rule, and the value to compare with. A text rule only works on text.
- 03
Create the event
Add a step in your calendar that creates an event, and map the booking's details into it. With the filter, the Zap is multi-step, so it needs a paid plan; without it, the free plan is enough.
- 04
Test, then publish
Run each step once and look at the event that came out. When it is right, publish the Zap to switch it on. Bookings made before that moment are not copied over.
The Linework triggers
7 events start a Zap when something happens in Linework, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
Appointment Canceled
Instant triggerIn Zapier“Triggers when an appointment is canceled.”
Starts your Zap the moment a booking is called off in Linework. The details of the canceled session come with the run, so the steps after it know which slot just opened up.
Appointment Completed
Instant triggerIn Zapier“Triggers when a checkout is completed for appointment.”
Fires when the checkout of an appointment is completed in Linework. It follows that checkout step, not simply the end of the booked time.
Appointment Rescheduled
Instant triggerIn Zapier“Triggers when an appointment gets rescheduled.”
Reacts whenever an appointment is moved to another time. The run carries the booking with its new slot, ready for the next step to update whatever depended on the old one.
Appointment Starts
Polling triggerIn Zapier“Triggers when a reminder is sent a specified time before an appointment starts.”
Tied to Linework's reminders: it fires when a reminder goes out a set time before a session begins. You choose that gap in Time before, the only required field.
New Appointment
Instant triggerIn Zapier“Triggers when a new appointment is scheduled.”
Runs as soon as a new session is booked in Linework. Each run hands the booking to the next steps, which is all you need to copy it into a calendar, a sheet or a message.
New Client
Instant triggerIn Zapier“Triggers when a client is created.”
Goes off whenever a client is created in Linework. Their details flow to the next steps, so the person can exist in your other tools without being typed in twice.
New Deposit Checkout Completed
Instant triggerIn Zapier“Triggers when a deposit is recorded.”
Watches for deposits: the Zap starts each time one is recorded in Linework. The deposit comes with the run, ready to be logged elsewhere or acknowledged to the client.
When a Linework Zap breaks
Zapier links no help article to Linework, and no app-specific limit is documented. What breaks comes from how Zapier itself works.
Four cases explain most surprises. When one hits, our Zapier troubleshooting page is the place to start.
Earlier bookings are not sent
A Zap only reacts to what happens after it is switched on. Appointments, deposits and clients that already existed stay out, and moving them is a separate job.A loop through another app
Linework has no actions, so a Zap cannot write back into it. A loop can still happen elsewhere, if a Zap writes into the place another Zap's trigger watches.A sudden flood is held back
When a trigger suddenly sends a huge batch, after a bulk import of clients for example, Zapier's flood protection can hold those runs back.A reminder that fires once
On Appointment Starts, Zapier remembers what it has already seen, so the same reminder does not start the Zap twice.
Need help automating Linework with Zapier?
A person reads every message.
