Set up Universal WhatsApp Replier
Import the inactive workflow kit and run its supplied synthetic example. Enter API credentials directly in your client-owned n8n Credentials vault, never in Aria's form.
What your client supplies
- A client-owned WhatsApp Business Platform (Cloud API) account with a dedicated number
- An n8n instance with a supported Code node; credentials in the client's vault only
- A scheduling source when the booking module is on — availability is never invented
- Opt-in records and approved templates before any follow-up is sent
Product-specific provider and API checklist
n8n workspace — Required for the scoped production use
Imports and runs the inactive workflow starters.
- Your client-owned n8n URL and workspace owner
Credential destination: No credential is required to test the synthetic starter.
- Import the supplied JSON workflow.
- Run the synthetic test and keep it inactive.
WhatsApp Business Platform / Cloud API — Required for the scoped production use
The channel the replier listens on and replies through, with a dedicated business number.
- Meta business verification, a WhatsApp Business Platform account, and a dedicated number
- Approved message templates for follow-ups and the client-owned webhook subscription
- Decision on whether per-message fees are included in the monthly fee or passed through at cost
Credential destination: Client-owned n8n Credentials vault only.
- Connect the channel adapter to a test number first.
- Run the full test pack, including handover and opt-out paths, before going live.
Scheduling / calendar source (optional) — Optional
Source of truth for open slots when the booking module is on; availability is never invented.
- Calendar or booking system name, API documentation, and service/provider mapping
- Permitted scopes and a named booking owner
Credential destination: Client-owned n8n Credentials vault only.
- Return source-confirmed slots only.
- Test lookup misses, stale availability, and double-booking protection.
AI provider (optional) — Optional
Adds language understanding beyond the deterministic intent rules after the demo is understood.
- Chosen provider/model and account/API documentation
- Approved prompt, data-handling policy, and cost owner
Credential destination: n8n Credentials vault only.
- Create the provider credential in n8n.
- Connect it only after the synthetic test, output schema, and prompt review are approved.
Lead sheet / CRM (optional) — Optional
Stores collected enquiry details for quote requests and lead capture, and alerts the team.
- Sheet or CRM name, vendor API documentation, field mapping, and permitted scopes
- Team alert destination and consent/message policies
Credential destination: Client-owned n8n Credentials vault only.
- Test a synthetic event, error path, and duplicate protection.
- Verify the human alert path before activation.
Installation and API connection are separately quoted
Ask Aria to contact you for installation, provider API wiring or a managed usage-cost quote. Purchasing a kit does not activate integrations, calls, broadcasts or schedules.