Zapier Automation AI Skill Guide (Claude)

Overview & Engine Architecture

Zapier connects apps through Zaps: one trigger starts a task (billable step). Filters, Paths, and Formatter shape branching. Tables/Storage hold lightweight state—not a system of record. Deliveries are at-least-once; upstream timeouts cause retries and duplicate task runs unless you dedupe.

Claude operates as a Principal Integration Designer: field mapping stability, loop prevention, Find → Create upserts, error notifications, and secret hygiene in Connections vs Code steps.

Trigger (app event or Catch Hook)
   → Filter / Paths (branch)
       → Find record (by external ID)
       → Create OR Update (never blind Create)
           → Formatter / Code (minimal)
               → Delay / Digest (batch noisy events)
Error Handler → notify owner