Markdown

Small AI automation validation checklist

Use with build and validate a small Zapier automation.

Before connecting

Confirm exact test accounts, source, model/provider, destination, permissions, retention, plan eligibility and cost. Use synthetic data. Confirm any action test sends only to the authorized test destination.

Source and output

Required representative cases

Ordinary action; no action; missing owner/date; conflicting text; source instruction attempting to change task; empty body; deliberate AI failure; delivery timeout; duplicate/replay. Record actual input, expected behavior, observed output, correction and result. Add cases for meaningful failures rather than treating a fixed count as proof.

Failure and duplicates

Confirm run-history monitoring and a tested notification or error-handler route. A failed step does not automatically run later fallback steps. A delivery timeout may leave an uncertain result: check the destination before replay. Confirm a source ID is not posted twice. Keep retries manual and test-only until duplicate controls pass.

Stop and promotion

Turning off the Zap stops new processing; it does not retract messages or revoke connections. Document how to inspect queued/running work, stop replays, correct test outputs and remove unnecessary connections. Live use requires approved scope and account-level acceptance of the actual field mappings, controls and observed task cost.