Zapier for Photographers: Automate Enquiries, Contracts and Reminders

Build four Zaps: one logs each enquiry in a sheet and has an AI step draft your reply for you to check, one creates the contract, folder and calendar entry when you mark a job booked, one sets reminder dates, and one sends them. A wedding uses about 17 to 22 tasks, so Professional fits and Free does not.

Zapier moves information between apps and an AI step writes text; neither should decide anything that matters. Keep the decisions with you: the AI step drafts a reply for you to read, the contract step prepares a document for you to approve, and the reminders come from calendar entries you can move in seconds. And if your studio software already has forms, contracts and workflows, use those first.

Follow me on Instagram@sagnikteaches

Decide which job lives in your studio software and which in Zapier

All-in-one tools such as HoneyBook and Dubsado include forms, contracts and workflow automations, though not always on every plan: HoneyBook's pricing page lists automations from its Essentials plan up. HoneyBook's help pages also describe AI that drafts a reply automatically when a new lead arrives through its contact or lead form. If you use a tool like that, each job below should live inside it unless there is a gap:

Connect on LinkedInSagnik Bhattacharya

The HoneyBook or Dubsado comparison covers that choice and what each costs. The rest of this tutorial assumes a lighter stack that many solo photographers run: a website form, a Google Sheet as the CRM, Gmail, Google Calendar, Google Docs and Drive, and an e-signature step if you use one. Zapier's editor names change slightly over time, so where I give an action name, look for the closest match in the editor if it differs.

Subscribe on YouTube@sagnikteaches

Set up the Enquiries sheet first, with one column per field and a Status column that moves through New, Replied, Call booked, Proposal sent, Booked, Signed and Lost. The columns are: Received, Names, Email, Phone, Event type, Event date, Venue, Guests, Hours wanted, Budget band, Heard about us, Message, Status, Folder link, Contract link and Notes.

Zap 1: enquiry form to sheet row, first reply and AI draft

Form design matters more than any Zap setting. Use a date picker so the event date arrives in one format. A typed "3/4/27" is ambiguous between day-first and month-first, and it will put a calendar event in the wrong month later. Make email and event date required, and offer a budget band as a dropdown.

Then build the Zap in this order. Each step shows the app, the action, and what to map.

1. Trigger: your form app, new submission. Website builders, Jotform, Typeform and Google Forms each have one; Zapier labels it "New Submission", "New Entry" or similar. Submit a test enquiry so Zapier has sample data. Triggers do not use tasks.
2. Google Sheets, Create Spreadsheet Row in the Enquiries sheet. Map every field and set Status to New. Log every enquiry, even incomplete ones, so nothing vanishes. (1 task)
3. Filter by Zapier: continue only if Email contains "@" and Event date exists. Filters use no tasks, and an incomplete enquiry stops here with its row already saved.
4. Gmail, Send Email: a short acknowledgement. "Thanks, [first name]. Your message has reached me and I reply personally within one working day. In the meantime, here is my pricing guide: [link]." (1 task)
5. AI by Zapier, draft the reply from the form data, using the instruction below. (counted as 3 tasks for planning)
6. Gmail, Create Draft: To is the enquirer's email, Subject is "Re: your enquiry for [event date]", Body is the AI output. The draft waits in your Drafts folder; you read it, add one personal line and send. (1 task)

The instruction for the AI step is where this succeeds or fails. In the Zap you insert each bracketed item by picking it from the trigger's data.

You are writing a first reply for a wedding photographer to a couple who filled in
my enquiry form. Use only the details below. Write 110 to 140 words, first person,
warm and plain. Mention the venue and date once. Never state which services I offer,
whether the date is available, or any price. If they asked a question you cannot answer
from the details, say I will come back to it on a call. End by suggesting a 20-minute
call and leave the times blank as [times].
Details: Names [Names]; Event [Event type]; Date [Event date]; Venue [Venue];
Guests [Guests]; Hours wanted [Hours wanted]; Message [Message]

A first run can return something like this (illustrative):

Hi [first name], thank you for getting in touch about your wedding at [venue] on [date]. Eight hours of coverage with around 90 guests sounds like a lovely, relaxed day. You asked whether I work with a second photographer: yes, I do, and it is a popular choice for a day that size. Would a 20-minute call on [times] suit you? I will check my diary and come back to you shortly. Warm wishes, [your name]

Three edits are needed before it goes. "Yes, I do" states a service the AI cannot know about, and the instruction said not to; the fix is to replace it with "I'll cover that on our call". "Lovely, relaxed day" is a guess about a day the model knows nothing about. And "I will check my diary" quietly promises a response time, so either keep it true or cut it. Each fault is small, and together they are how an automated reply ends up promising things you never offered. If you want a deeper look at how AI steps behave, the tutorial on adding AI steps to Zapier covers classify, summarise and draft steps.

Optional: check the date against your calendar first

Add a calendar search step before the AI step: look for an action in Google Calendar that finds events, and search your "Bookings" calendar for the event date. Then add a Paths step with two branches. If an event is found, the branch sets an availability line to "I'm already booked that day, so I'll suggest alternatives on a call". If not, it sets "That date looks open in my diary, though I will confirm after we speak". Pass the line into the AI instruction as a new detail. The search step uses 1 task per enquiry; Paths use none, but need a paid plan. Never let the AI decide availability by itself.

Zap 2: booked status to contract, client folder and calendar date

This Zap runs when you change a row's Status to Booked, after the couple has said yes. It prepares the paperwork; it does not send anything until you approve.

1. Trigger: Google Sheets, New or Updated Spreadsheet Row. Set the trigger column to Status, so only changes to that cell wake the Zap.
2. Filter by Zapier: continue only if Status is exactly "Booked" and Contract link is empty. The second condition stops a second contract going out when you edit another cell later.
3. Google Drive, Create Folder: named "[Names] [Event date]" inside your Clients folder. (1 task)
4. Google Docs, Create Document from Template: your contract template, with placeholders such as names, date, venue, package, fee, retainer and balance due date. Save the copy into the new folder. (1 task)
5. Human in the Loop by Zapier: an approval request to yourself. "Contract for [Names] is ready: open it, check it, approve." Set the timeout so the run ends if you do not respond, which means an unapproved contract can never send itself. (count it as 1 task for planning, then check)
6. Gmail, Send Email: the contract link, a line on how to sign and what the retainer secures. (1 task)
7. Google Calendar, Create Detailed Event: in your Bookings calendar, on the event date, titled "Wedding: [Names], [Venue]". (1 task)
8. Google Sheets, Update Spreadsheet Row: write the folder link, the contract link and today's date back to the row. (1 task)

On Professional, Human in the Loop approvals can only go to you, which is what a solo photographer wants. If you use an e-signature app with a Zapier connection, replace steps 4 and 6 with the app's action that sends a document from a template for signature, which is one task instead of two. The DocuSign tutorial shows that pattern for one popular tool.

One rule is not negotiable: Zapier fills in names, dates and fees; it does not write clauses. The template carries the wording on rights, usage, cancellation and liability, and it should be checked once by a qualified adviser. The contract template tutorial shows how to use AI to draft and then check that wording, outside the Zap.

Zaps 3 and 4: reminders that run from a calendar, not a delay

A wedding is booked months or more than a year ahead, which makes the reminders the awkward part. Zapier has a Delay step, and Zapier's help pages list it among the steps that do not use tasks, but I avoid month-long waits for a practical reason: a Zap run sitting in a queue is hard to see, and it is awkward to change when a couple moves their date. A calendar entry is easy to see and takes seconds to drag. So the calendar becomes the timer.

Zap 3 sets the reminders when you change Status to Signed:

1. Trigger: Google Sheets, New or Updated Spreadsheet Row, trigger column Status.
2. Filter by Zapier: continue only if Status is exactly "Signed".
3. Gmail, Send Email: a welcome and what happens next. (1 task)
4. Formatter by Zapier, Date/Time, Add/Subtract Time from Date, then Google Calendar, Create Detailed Event, four times over, once per reminder. Formatter uses no tasks; each event is 1 task. (4 tasks)
5. Google Sheets, Update Spreadsheet Row: Status becomes "Reminders set". (1 task)

That last step changes Status, which wakes both sheet-triggered Zaps again. Their filters ("exactly Booked" and "exactly Signed") stop those runs at no cost, which is why every Zap triggered from the sheet needs a filter.

Each event goes in a separate "Client reminders" calendar, starts at 9am, has the client's email address in the Location field, and holds the full email text in the Description. Here is a four-reminder schedule for a wedding:

Zap 4 sends them and has only two steps:

1. Trigger: Google Calendar, event start (look for "Event Start" or "Event Started" in the editor), on the Client reminders calendar.
2. Gmail, Send Email: To is the event's location field (Zapier may label it Location or Where), Subject is its title, Body is its description. (1 task per reminder)

Because Zap 4 is a trigger plus one action, it is the only one in this set that fits the Free plan's two-step limit as written. For what happens after the wedding, including gallery reminders, see the gallery delivery tutorial.

What one wedding costs in tasks, and where the Free plan stops

Zapier bills in tasks. Triggers and filter steps do not count, and each successful action step does. Formatter and Paths use none. The table counts the setup above for one wedding that goes from enquiry to the thank-you email. The AI step is counted as 3 tasks, because Zapier's pages have given 1, 3 or 5 depending on the model tier and the tiers have been renamed since, so check your usage page after a week.

An enquiry that never books costs 2 tasks, or 6 with the AI draft. Take a studio with 120 enquiries and 24 weddings a year. The 96 lost enquiries cost 192 to 576 tasks and the 24 weddings cost 408 to 528, which is 600 to 1,104 tasks a year, or 50 to 92 in an average month. (The reminder tasks fall in the months before each wedding rather than at booking, but the yearly total is the same.) In a busy January with 30 enquiries and six bookings, the 24 lost enquiries use 48 to 144 tasks and the six bookings 78 to 108 (13 to 18 each, because their four reminders run later), so roughly 126 to 252 tasks plus reminders for any weddings coming up. That is above Free's 100 tasks a month, and far inside Professional's 750.

Task counts are not the real constraint here. Features are, as the table of limits shows:

With pay-per-task switched on, extra tasks cost 1.25 times your plan's per-task rate, and Zaps stop at three times the limit; with it off, they pause at the limit. On Free, a held run in a busy week means a couple waits for their acknowledgement until the month rolls over, which is a poor first impression.

A simple sum on cost: Professional billed annually is $239.88 a year. If your time is worth $50 an hour, it pays for itself at 4.8 hours saved in the year. Start on Free if you like: build Zap 4 and a two-step form-to-sheet Zap, learn how task usage looks, and upgrade when you add the contract Zap. If you bring your own API key, Zapier has listed the AI step at one task instead of three or five, though the model provider bills API use separately from any ChatGPT or Claude subscription.

Dummy enquiries to run before a real couple does

Run every test with your own email address as the client's, so nobody real receives a half-built message. Use a made-up wedding two years ahead.

1. Complete enquiry. Check the sheet row, the acknowledgement, the Gmail draft and that no step shows an error in Zap History.
2. Incomplete enquiry. Switch off the "required" setting for a moment, or send test data without the date. The row should still appear while the filter stops the replies. If the row is missing, the order of steps is wrong.
3. Date already booked. If you added the calendar check, the draft should say so, and nothing should claim the date is free.
4. Duplicate submission. Submit the same details twice. You will get two rows. Check weekly, or add a lookup by email before the row step (one more task).
5. Booked. Change a test row to Booked. You should see the folder, a filled-in contract with no stray placeholders, an approval request, and no email until you approve.
6. Signed. Change it to Signed. Open the Client reminders calendar and check that each event is on the date it should be, at 9am, with the right Location. A wrong time zone setting between Zapier, your calendar and the sheet is the usual culprit.

Then watch it. Zapier switches a Zap off automatically when 95% of its runs error over seven days, and a broken form connection can do exactly that in a quiet week. Open Zap History every Monday, and compare the enquiry notifications in your inbox with the new rows in the sheet. The tutorial on stopping automations breaking silently adds more checks.

Jobs a Zap should never do for you

• Send a contract unseen. Keep the approval step, however confident you become.
• Answer "are you free on that date?" A yes is a commitment. The calendar check informs your reply; it does not make it.
• Set or change a price. Prices come from your own price list, not from a model's guess.
• Handle a date change or a sensitive message. A postponement, a bereavement or a complaint needs your own words. Move the reminder events by hand.
• Collect more than you need. The AI step sends the enquiry text to a model, so do not ask the form for health or family details, and say in your privacy wording that you use automation and AI tools.

Each of these keeps your voice at the points where a couple decides whether to trust you. Everything else, the copying, the folders, the dates and the nudges, is the part a Zap is good at.

Zapier questions photographers ask before building

Is the Zapier Free plan enough for a photographer?

Free gives 100 tasks a month and two-step Zaps only: a trigger and one action, checked every 15 minutes, with no filters, paths or formatter steps. That covers a form-to-sheet Zap and a reminder sender, but not the contract and reminder-setting Zaps. Professional removes those limits and starts at $19.99 a month billed annually.

Does the AI step cost extra tasks?

It can. Zapier's pages have quoted 1, 3 or 5 tasks for an AI step depending on the model tier (one task if you bring your own API key), and the tiers have been renamed, so count 3 when planning and check your usage page after a week. At 120 enquiries a year that is about 360 tasks, small next to a 750-a-month allowance.

What happens if I hit my task limit in wedding season?

On Free, runs are held until the allowance resets. On Professional with pay-per-task switched off, Zaps pause at the limit. With it switched on, extra tasks bill at 1.25 times the plan's per-task rate until Zaps stop at three times the limit. Check your usage weekly in busy months.

Should I use Zapier or my studio software's automations?

Use the software's own automations for anything that happens inside it. They are simpler to maintain and keep the project history in one place. Use Zapier for the gaps between tools, such as a website form, a spreadsheet, a calendar and an e-signature app that do not talk to each other.

Further reads

• Native Integrations vs Zapier: Which Should Connect Your Apps? — When a built-in integration beats a Zap.
• AI Agent for Photographers: Enquiry to Booking Without the Inbox — An AI agent for the enquiry-to-booking path.
• AI Proposal Generator for Photographers: Quotes, Contracts, Pricing Guides — Draft the proposals and pricing guide the Zaps will send.
• When Does Zapier Get Too Expensive? Finding the Tipping Point — Where the tipping point sits as task counts grow.
• AI for Photographers: Same-Day Quotes and Shot Lists From a Brief — Brief in, quote out the same day: a worked furniture-workshop shoot with an extraction prompt, a timed shot list, a priced quote and the pre-send checks.
• AI for Tailors: One Wedding-Suit Job From Quote to Final Fitting — One wedding suit from first enquiry to pick-up: what the AI drafts, what the tailor checks, and the dates, sums and texts in between.
• How to Use AI in a Photography Business: Start With Admin, Not Editing — Rank admin, marketing and editing by payback and risk, then start with three admin jobs: enquiry replies, shoot briefs and delivery emails.
• Wedding Photographer Timeline Template: A Day Schedule Built With AI — One wedding walked end to end: a timeline template, an AI draft, and the venue, planner and couple checks that catch the clashes before the day.
• Does Dubsado Have AI? What to Use Alongside It for Client Admin — Dubsado lists AI form building, a call notetaker and email summaries. Here is what they do, what they cost, and what ChatGPT or Zapier adds beside them.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Zapier plans, task-usage and Delay help pages; Zapier's app directory listing for Google Calendar; HoneyBook's help pages on drafting emails with HoneyBook AI and its pricing page, all as listed in October 2026. Action names in Zapier's editor change, so check them as you build.