zapier-workflow-builder

Start by defining the trigger event, desired outcome, filters, volume, and apps involved. Then design the Zap with a filter as step 2 and Formatter steps for data transformation, since both cost zero tasks. Finally, generate a Copilot prompt or follow step-by-step setup instructions.

Only completed action steps count as tasks, including AI by Zapier, Code by Zapier, and Webhooks steps. Triggers, filters, formatters, delays, paths, loops, sub-zap calls, digests, and storage steps are all free, so placing filters early reduces costs.

Use Code by Zapier for deterministic transforms like splitting email lists, date math, and URL parsing where the answer must be exactly right every time. Use AI by Zapier for summarization, drafting, and extraction where interpretation is needed.

Choose Autoreplay for transient failures like API timeouts and rate limits, since it retries up to 3 times automatically. Choose custom error handlers when you need immediate Slack notification or alternate logic on failure, but note that Zaps with error handlers cannot use Autoreplay.

Prevent loops by adding a guard field such as processed_by_zap = true and filtering on it. For Google Sheets, use the Trigger Column setting to fire only on specific column changes, and never let two Zaps read and write the same data without loop guards.

Copilot cannot connect app accounts, so users must authenticate each app themselves. Complex field mappings often need manual refinement after the draft is built, and it cannot predict trigger behavior, so always test the Zap after building.