In short
n8n connects to OmniChannels.ai in two ways. An AI Agent node can use our messaging tools through the MCP Client Tool node pointed at https://mcp.broadnet.me/mcp with a Bearer token. Fixed workflows use an HTTP Request node to call the REST API and a Webhook node to receive delivery statuses and inbound messages. There is no dedicated n8n node; both routes use n8n's built-in nodes.
What you can do
Send an OTP or confirmation the same way every time
When a form, app or database step produces a code or booking, an HTTP Request node sends it by SMS or WhatsApp through the REST API, with no AI involved.
Send a WhatsApp template when a new row is added
When a new row appears in a sheet or database that n8n watches, send an approved WhatsApp template with the row's values as its variables, to contacts who have opted in.
Alert the team when a delivery fails
A Webhook node receives delivery statuses; when one is FAILED or REJECTED, n8n posts an alert to your team chat or opens a ticket instead of resending automatically.
Keep message status in your own records
Store the message ID returned by each send, then update the matching record as SENT, DELIVERED and READ statuses arrive, ignoring late or duplicate events.
Let an AI Agent answer delivery questions
An AI Agent with read-only MCP tools looks up templates and delivery reports and answers your team's questions in a chat workflow.
Try asking
“Which messages to 966500000000 failed this week, and why?”
Draft with AI, send after approval
An AI Agent drafts an Arabic and English message, a team member approves it, and a fixed HTTP Request node sends the approved text.
Try asking
“Draft a short WhatsApp reminder in Arabic and English for tomorrow's appointments, for me to approve.”
How it connects
For AI workflows, attach an MCP Client Tool node to an AI Agent node, set the endpoint to https://mcp.broadnet.me/mcp with Streamable HTTP transport, and store your key in a Bearer Auth credential. Choose only the tools the agent needs: n8n workflows usually run unattended, so nobody approves each tool call.
For fixed workflows, an HTTP Request node calls the REST API at https://api.broadnet.me with a Bearer Auth credential. Single SMS takes a JSON body; bulk and most other channel sends take multipart form data, which the node supports. A Webhook node, whose production URL our team or your account admin sets as the webhook on your account, receives delivery statuses and inbound messages.
- MCP: MCP Client Tool node, Streamable HTTP, Bearer Auth credential
- API: HTTP Request node with JSON or form-data body
- Events: Webhook node production URL configured on your account
- Use fixed HTTP Request steps for OTPs and order notifications
- Older n8n versions offer only SSE for MCP; update n8n if yours does
Set it up
- 1
Request API access
Request test access and receive an API token. Test sends go only to your own verified numbers.
Guide: Quickstart: send your first message - 2
Store the token as a credential
Create a Bearer Auth credential in n8n holding your API token or MCP key, so it stays out of exported workflows.
Guide: Authentication - 3
Add the sending step
For an AI Agent, attach an MCP Client Tool node with the endpoint https://mcp.broadnet.me/mcp and only the tools it needs. For a fixed workflow, add an HTTP Request node that POSTs to the channel's send path.
Guide: Use the MCP server with n8n - 4
Receive delivery statuses
Add a Webhook node with method POST, activate the workflow, and send its production URL to our team or your account admin.
Guide: Webhooks and delivery statuses - 5
Test with your own number
Run the workflow against your verified number and check that the send and its status events appear in the executions list.
Vendor documentation
n8n is a trademark of its owner. OmniChannels.ai is not affiliated with or endorsed by n8n; this page describes a connection built with n8n's own MCP, HTTP or webhook features.
