The acceptance test plan defines the 22 scenarios that must be verified before any version of the n8n WhatsApp AI Agent is considered production-ready. All tests must be executed using fictitious data and a dedicated test WhatsApp number — never against the live business number with real customers. For each test case, record the date the test was run, the stack version under test, the actual result observed, and the evidence collected (typically a screenshot or log excerpt). This record is part of the release documentation and must be retained alongside the release notes.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/DevMauricio03/n8n-whatsapp-ai-agent/llms.txt
Use this file to discover all available pages before exploring further.
Test cases
The table below lists all 22 acceptance test cases organised by area: messaging behaviour, AI responses, human handoff, business hours, data synchronisation, security, operations, and backup.| ID | Scenario | Expected result |
|---|---|---|
| MSG-01 | Send a greeting message | A brief response in Spanish |
| MSG-02 | Send three messages in rapid succession | A single response that groups all the content |
| MSG-03 | Send a valid audio message | Correct transcription and response |
| MSG-04 | Send an invalid audio message | Controlled error with no invented response |
| MSG-05 | Send an image or sticker | Ignored or handled according to the defined policy |
| AI-01 | Ask about a service | Guidance without inventing information |
| AI-02 | Ask for general pricing | The correct resource is sent |
| AI-03 | Provide an existing case reference number | Only authorised information is returned |
| AI-04 | Provide a non-existent case reference number | The contact is informed that no record was found |
| AI-05 | Ask an out-of-scope question | The agent limits its response to its defined scope |
| HH-01 | A human agent responds in Chatwoot | The Redis handoff key is created |
| HH-02 | The customer writes during an active handoff | The AI does not respond |
| HH-03 | The handoff TTL expires | Automatic AI mode resumes |
| HH-04 | Redis is unavailable | The automation fails safely without crashing |
| TIME-01 | Message received during business hours | The AI executes normally |
| TIME-02 | Message received outside business hours | An out-of-hours notice is sent; the AI does not execute |
| TIME-03 | Message received on a weekend | The out-of-hours policy is applied |
| DATA-01 | Update the source XLSX file | The bd_clientes table is updated in the agent database |
| DATA-02 | XLSX contains a duplicate row for an existing reference | The existing record is updated, not duplicated |
| SEC-01 | Webhook receives an incomplete payload | No secrets are leaked and the overall flow does not break |
| OPS-01 | All services are restarted | Data and configuration persist correctly after restart |
| BAK-01 | Restore backup in an isolated environment | All services and data are successfully recovered |
Minimum pre-release test set
Before every release — including minor configuration changes and pricing updates — execute at least these nine test cases and confirm they all pass. Do not deploy to production with any of these in a failing state:
- MSG-01 — basic greeting and response
- MSG-02 — message grouping behaviour
- AI-03 — case reference lookup with a known record
- HH-01 — human handoff Redis key creation
- HH-02 — AI silence during active handoff
- TIME-01 — AI executes during business hours
- TIME-02 — out-of-hours message sent outside business hours
- DATA-01 — XLSX sync updates the database
- OPS-01 — data and configuration persist through a restart