Zapier and Make Workflows That Replace a Part-Time Employee

automation

Small publishers do a surprising amount of copying and pasting. Order comes in, get copied into a spreadsheet. Enquiry arrives, get copied into a to-do list. Review copy is sent, gets noted somewhere. None of it is difficult and all of it takes hours a week that could be spent on the books.

Here are five automations that remove most of it. The tool matters less than the design — Zapier is simpler to start with, Make handles branching logic more cheaply at volume.

1. Order to fulfilment sheet, with routing

Trigger: new paid order in your store. Action: create a row in a fulfilment sheet, with a branch on the line items.

The branch is the useful part. Print-on-demand titles route to one place, warehouse stock to another, signed or numbered copies to a manual list because those need a human. International orders get flagged for customs paperwork before they reach packing rather than after.

Trap to avoid: build in a delay of ten to fifteen minutes before the automation fires. Orders get cancelled, edited, or flagged for fraud in the first few minutes, and a fulfilment row created instantly will be wrong.

2. Enquiry triage

Trigger: new email to your general inbox. Action: classify and route.

Publishers get four kinds of message through one address — orders and order problems, submissions, rights and permissions requests, and press or review requests. Each has a different owner and a different urgency, and all four land in the same place.

Route each into its own task list with a template reply attached. Submissions in particular benefit, because an automated acknowledgement with your actual guidelines prevents a long tail of follow-up emails asking whether you received it.

Trap: never auto-send a substantive reply. Auto-acknowledge, then let a person write anything that matters.

3. Review copy tracking

Trigger: a row added to a review copy list. Actions: create a reminder chain.

Review copies disappear into a void. Someone requests one, you post it, and three months later nobody remembers whether it produced anything. Automate a follow-up at two weeks — did it arrive — and at six weeks — anything published. Log any coverage against the title.

Over a year this builds the single most useful marketing asset a small press can have: a list of which outlets actually cover you, rather than which ones you keep sending books to out of habit.

4. Stock threshold alerts

Trigger: inventory count drops below a set level. Action: notification with reprint lead time attached.

The number that matters is not the stock level but the time it takes to reprint. If your printer needs eight weeks and you sell twenty a week, your alert threshold is around two hundred copies, not twenty. Put the lead time into the alert message itself so the person reading it does not have to remember.

5. Contributor and payment reminders

Trigger: a date field in your project tracker. Action: staged reminders.

Illustrators, translators, indexers, and typesetters all have deadlines, and chasing them is nobody’s favourite job. Automate the chase at a week before, on the day, and three days after. Do the same for your own obligations — royalty statements and contributor payments — because being late on those costs you the relationship with exactly the people you need next time.

What not to automate

Anything a customer will read as a person speaking to them. Complaint responses. Submission rejections. Anything involving money moving in a direction that cannot be reversed.

The rule that holds up: automate the moving of information, not the making of decisions. The moment a workflow starts deciding something on your behalf, it needs a human checkpoint before it acts.