Build an SMS Gateway in n8n with RCSZilla Webhook Integration

Transform your n8n instance into a powerful SMS gateway with this comprehensive workflow that integrates RCSZilla for reliable message delivery. This automation creates a webhook-based API endpoint that accepts SMS requests from your existing business applications and routes them through RCSZilla's messaging infrastructure.

What this workflow does

The workflow operates as a complete SMS gateway service within n8n:

• Receives POST requests through a dedicated webhook endpoint
• Accepts essential parameters: recipient phone number, message content, consent verification, and optional metadata
• Automatically normalizes phone numbers to ensure proper formatting
• Defaults messaging channel to SMS while supporting both SMS and WhatsApp delivery
• Validates all required fields including phone number, message body, consent status, and channel validity
• Queues approved messages through the RCSZilla messaging service
• Returns structured JSON responses indicating whether requests were successfully queued or rejected with error details

Use cases

Perfect for businesses requiring automated SMS capabilities:

• CRM systems sending appointment confirmations and follow-up messages
• E-commerce platforms delivering order status updates and shipping notifications
• Booking applications confirming reservations and sending reminders
• Support desks providing ticket updates and resolution notifications
• Internal applications requiring consent-based SMS communication

Technical details

This workflow leverages key n8n nodes and integrations:

• Webhook node: Creates the API endpoint for receiving SMS requests
• RCSZilla community node: Handles message queuing and delivery through RCSZilla service
• Code node: Processes phone number normalization and validation logic
• IF node: Manages conditional routing based on validation results
• Respond to Webhook node: Returns formatted JSON responses

Requires the n8n-nodes-rcszilla community package, active RCSZilla account with API token, and either a connected Android device or configured provider route for message delivery.