Connect WhatsApp API to n8n
Use WireWeb as the WhatsApp messaging layer inside n8n. Trigger sends from forms, CRM updates, payment events, ecommerce workflows, and custom webhooks, then route replies back into your automation.
n8n setup pattern
Outbound message workflow
- Start with a trigger: form submission, CRM update, order event, schedule, or webhook.
- Add a Set node to prepare phone number, session ID, and message text.
- Add an HTTP Request node that calls the WireWeb send endpoint.
- Store the returned message ID in your database, CRM, or sheet.
Inbound reply workflow
- Create an n8n Webhook trigger URL.
- Paste that URL into WireWeb as your webhook destination.
- Use phone number matching to find the related CRM record.
- Route the reply to Slack, email, a support desk, or a bot branch.
HTTP Request node example
POST https://api.wireweb.co.in/v1/messages/send
Headers:
Content-Type: application/json
X-API-Key: {{$env.WIREWEB_API_KEY}}
Body:
{
"session_id": "ww_sess_123",
"to": "{{$json.phone}}",
"type": "text",
"message": "Hi {{$json.first_name}}, your order {{$json.order_id}} is confirmed."
}High-value n8n workflows
Lead response
Send a WhatsApp reply when a lead lands from a website form, Facebook ad, or CRM import.
Order updates
Notify customers when Shopify, WooCommerce, or a custom store changes order status.
Payment reminders
Trigger reminders when an invoice becomes due or a failed payment needs customer action.
Support escalation
Route customer replies to Slack, email, or a ticketing system when a keyword or status matches.
Appointment reminders
Send messages from calendar events, booking systems, or spreadsheet rows.
Webhook bridge
Use n8n to translate WireWeb webhook events into CRM notes, database rows, or bot decisions.
n8n implementation notes
Use production webhook URLs
When receiving replies, use the production n8n webhook URL in WireWeb so the flow keeps working after testing.
Keep secrets out of nodes
Store the WireWeb API key in n8n credentials or environment variables instead of hardcoding it in workflow JSON.
Make workflows idempotent
Store message IDs and webhook event IDs so retries do not create duplicate CRM notes or duplicate outbound messages.