# n8n Client Automation QA Checklist

**Version:** 0.1 MVP  
**Publisher:** OperatorForge AI  
**Website:** https://operatorforge-ai.pages.dev  
**Use case:** Pre-delivery testing for client automations built in n8n, Make, Zapier, or custom webhook flows.

## Quick pass

- [ ] Confirm the workflow goal in one sentence.
- [ ] Identify every trigger and every output.
- [ ] Run one happy-path test with realistic data.
- [ ] Run one missing-data test.
- [ ] Run one duplicate-data test.
- [ ] Confirm retries do not create duplicate records/messages.
- [ ] Confirm credentials are stored safely.
- [ ] Confirm notifications go to the correct internal owner.
- [ ] Confirm client-facing copy has no placeholders.
- [ ] Confirm timezone, currency, dates, and phone formats.
- [ ] Turn on workflow-level error notifications.
- [ ] Add a rollback note.
- [ ] Save screenshots or run logs for the handoff.

## Full QA sections

1. Scope lock
2. Credential and access safety
3. Test data matrix
4. Trigger testing
5. Node-by-node validation
6. Client-facing copy review
7. Idempotency and duplicate protection
8. Error handling and observability
9. Security and privacy
10. Production launch

## Test data matrix

| Scenario | Input | Expected output | Actual output | Pass/fail | Evidence link |
|---|---|---|---|---|---|
| Happy path | Complete realistic record | Correct downstream action |  |  |  |
| Missing required field | Blank email/phone/name | Safe error or internal alert |  |  |  |
| Duplicate submission | Same lead twice | No duplicate spam / merge logic works |  |  |  |
| Invalid format | Bad email/phone/date | Validation catches issue |  |  |  |
| Slow external API | Delayed response | Retry or alert works |  |  |  |
| Permission failure | Revoked/expired credential | Clear internal alert |  |  |  |
| Client edge case | Client-specific exception | Expected handling |  |  |  |

## Handoff email template

Subject: Automation QA complete — [Workflow Name] is ready

Hi [Client Name],

I finished pre-delivery QA for **[Workflow Name]**.

Tested scenarios:

- Happy path with realistic data
- Missing/invalid field handling
- Duplicate submission/retry behavior
- Downstream record/message creation
- Error notification path
- Production credential and activation check

Current status: **Ready for production monitoring / ready to activate / ready after your approval**.

If anything unexpected happens, disable the workflow here: [link or instructions]. The manual fallback is: [fallback].

I recommend we monitor the first [3–5] live runs and then move it to normal maintenance.

Best,  
[Your Name]

## Full checklist

Read the web version: https://operatorforge-ai.pages.dev/guides/n8n-client-automation-qa-checklist.html

OperatorForge AI launch kit: https://operatorforge-ai.pages.dev/