# Workflow Reliability Checklist Sample

This is a sanitized sample of the handoff format for a focused n8n, Make, Zapier, webhook, CRM, API, Airtable, or AI workflow reliability pass.
It is not a client deliverable and does not contain private workflow data.

## Input

- Target: workflow, webhook path, CRM sync, automation scenario, AI agent handoff, Airtable base, Google Sheets sync, or internal tool integration
- Reported issue: duplicate runs, missed records, bad retries, broken webhook, bad payload mapping, flaky browser step, failed CRM update, unclear error path, or messy client handoff before rollout
- Available material: exported workflow JSON, sample payload, staging endpoint, test sheet/base, sanitized logs, screenshots, acceptance checklist, or a guided limited-access session

## Reliability Pass

1. Map the happy path and the main failure path.
2. Identify inputs, outputs, owner systems, side effects, retry behavior, and duplicate risk.
3. Build or review a small fixture set: valid payload, missing field, duplicate record, timeout/error response, and unexpected value.
4. Run the safest possible smoke checks against staging, sample data, or exported config first.
5. Deliver a concise handoff with what passed, what failed, and what needs owner/vendor access.

## Checks

- Trigger: webhook, schedule, form submit, CRM event, sheet update, or manual run fires only when expected
- Payload shape: required fields, IDs, timestamps, currencies, emails, URLs, arrays, and null values are handled
- Dedupe/idempotency: repeated payloads do not create unwanted duplicate contacts, deals, tickets, rows, or messages
- Retry/error path: timeout, 4xx, 5xx, rate limit, vendor outage, and partial failure behavior is visible
- Mapping: CRM stages, owners, tags, status fields, custom fields, and normalized names are consistent
- Logs: each run leaves enough timestamp, input ID, output ID, and error detail for a human to debug later
- Secrets: API keys, OAuth, cookies, tokens, recovery codes, and credentials are never pasted into docs or email
- Handoff: next owner can rerun the smoke check without guessing the order of operations

## Output

A useful first pass should produce one of these:

- a fixed mapping, filter, retry, dedupe, or handoff issue in one defined workflow path;
- a reliability checklist with pass/fail notes and sample payloads;
- a fixture pack that a delivery team can rerun before client review;
- a concise risk note naming the exact owner/vendor access still needed.

## Acceptance Check

Run the same defined path after the change:

- valid sample reaches the expected destination exactly once;
- missing or invalid sample fails visibly without corrupting downstream data;
- duplicate sample does not create unwanted duplicate output;
- logs and handoff notes identify the run, input, result, and remaining risk.

## Boundaries

- No CAPTCHA bypass, account abuse, hidden scraping, or stealth automation.
- No stored secrets, OAuth tokens, cookies, recovery codes, private keys, card data, bank data, tax data, or payout information.
- Production credentials, paid tools, OAuth approvals, contracts, billing, KYC, tax, and final rollout approval stay with the human account owner.

## Handoff

Deliverables for a first pass:

- workflow path summary;
- fixture list and expected result;
- pass/fail table;
- mapping, retry, dedupe, logging, or error-path notes;
- exact change applied or recommended;
- remaining owner/vendor actions before production rollout.