Integrations / n8n
n8n: let an AI agent send SMS or place calls
n8n reaches Hail two ways: an HTTP Request tool on the AI Agent node, or the MCP Client node pointed at Hail's MCP server. Both drive the same account.
01Option A: HTTP Request tool
Add an HTTP Request tool to your AI Agent node with these settings. The agent fills to and body from the conversation.
Method: POST
URL: https://api.hail.so/sms
Authentication: Generic > Header Auth
Name: Authorization
Value: Bearer hl_live_9fa2...
Body (JSON):
{
"to": "{to}",
"body": "{body}",
"recipient_consent": true
}02Option B: MCP Client node
Point the MCP Client Tool node at Hail's MCP server and approve the OAuth screen once. send_sms, send_email, and place_call appear as tools the agent can use.
MCP endpoint: https://mcp.hail.so Auth: OAuth (one-click approval)
03Receive inbound
Start a workflow from a plain n8n Webhook node and register its URL with Hail, so inbound SMS and email trigger flows.
POST https://api.hail.so/webhooks
{
"target_url": "https://your-n8n.example/webhook/hail",
"event_types": ["sms.received", "email.received"]
}Questions
Which option should I pick?
MCP is fastest and needs no key handling in n8n. Pick the HTTP tool when you want exact control over the request the agent can make.
Can non-agent workflows use the same account?
Yes. Any n8n workflow can call the REST API directly with the same key and the same balance.
Ship it with a real number
Sign up, grab a key, and the examples above run as written. Pay per use, no subscription.
Get started →More frameworks
LangGraph · CrewAI · OpenAI Agents SDK · Vercel AI SDK · Claude