Integrations / n8n
Send SMS and place calls from an n8n AI agent
n8n connects to Hail in two ways. The first is an HTTP Request tool on the AI Agent node. The second is the MCP Client node with the Hail MCP server. Both use the same account.
Option 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
}Option B: MCP Client node
Set the MCP Client Tool node to the Hail MCP server. Approve the OAuth screen one time. The agent can then use send_sms, send_email, and place_call.
MCP endpoint: https://mcp.hail.so Auth: OAuth (one-click approval)
Receive inbound messages
Start a workflow from an n8n Webhook node. Register the URL of the node with Hail. Inbound SMS and email then start the workflow.
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?
With MCP, you do not put an API key in n8n. Use the HTTP Request tool when you want exact control of the request that 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.
Run the examples
The examples above run as written with a Hail account and an API key. You pay for usage.
Create account