Zapier Copilot built it. The second booking still fails.

I am not anti-Copilot. I am anti-shipping the draft. A large share of rescue work now starts with “we generated the Zap last week.” The Zap is on. The calendar still has holes.

What Copilot usually gets right

• Trigger app and the obvious create/update action.
• A Path named after the words you typed (“if new lead, notify Slack”).
• Field names that exist in the sample Zapier pulled.

That is enough for a demo. It is not enough for a form that sometimes omits company, a Calendly cancel, or a second submit with the same email.

What breaks on run two

Find vs create

Copilot often inserts Create contact because that is what you asked for. Run two with the same email creates a duplicate. You wanted Find or create (or search + update). Check the HubSpot/GHL step: if there is no search by email, that is the bug, not “Zapier is flaky.”

Empty fields and required API fields

The sample had a phone number. The next lead did not. A Formatter or a required CRM field throws. Copilot mapped the sample, not the sparse live payload. Fix: make the field optional in the CRM, or add a Formatter “default if empty,” or a Filter that routes incomplete leads to a holding list instead of failing the Zap.

Paths that never fire

Paths are compared as text. Copilot writes “Yes” and the form sends “true”, or “New Patient” vs “new_patient”. The fallback Path is missing, so the Zap stops after the trigger with no error you notice unless you open Zap History. Add an “always” fallback Path that posts to Slack: “unmatched status: {{status}}.”

The cancel / reschedule path

Booking tools fire created, canceled, and rescheduled as different events — or as one event with a status field. Copilot builds “new booking → confirm SMS.” Cancel still sends “see you tomorrow,” or never deletes the job folder. If you have Aryeo, Calendly, or similar in the stack, you need three explicit routes, not one happy Zap.

A checklist before you pay for more Copilot credits

1. Turn the Zap off. Run two tests: new email, then the same email again. You want one CRM record, not two.
2. Run a test with a blank optional field (phone, company). The Zap should not error.
3. If you have statuses, fire one that is not in the Path list. Something should still log.
4. If the product has cancel/reschedule, those are separate Zaps or Paths. If they are missing, the draft is not done.

When to hire a person anyway

If the Zap has more than one Path, a lookup table, or two CRMs, Copilot will keep producing a plausible graph. You will keep finding holes in History. Send me the Zap (or a screenshot of the outline) and two History rows: the one that worked and the one that did not. I patch the find/create, the empty fields, and the missing cancel path — then write down what not to regenerate.