n8n
Connect n8n workflows to BlueNexus via MCP, giving your AI nodes access to users' connected services.
Setup
Option 1: MCP Node (Recommended)
If your n8n instance supports MCP nodes:
- Add an MCP Client node to your workflow
- Set the Server URL to
https://api.bluenexus.ai/mcp - Configure authentication:
- OAuth: n8n handles the DCR and OAuth flow automatically
- Bearer Token: Use a Personal Access Token (see below)
Option 2: Personal Access Token
For simpler setup:
- Create a PAT at app.bluenexus.ai > Settings > Sessions with scope
universal-mcp-read-write - In n8n, configure the MCP node with:
- Server URL:
https://api.bluenexus.ai/mcp - Authentication: Bearer Token
- Token: Your PAT
- Server URL:
Option 3: HTTP Request Node
You can also call the MCP endpoint directly using n8n's HTTP Request node:
URL: https://api.bluenexus.ai/mcp
Method: POST
Headers:
Authorization:Bearer YOUR_PATContent-Type:application/jsonX-Response-Format:json
Body (to list available tools):
{
"jsonrpc": "2.0",
"method": "tools/list",
"params": {},
"id": "1"
}
Body (to call the agent):
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "use-agent",
"arguments": {
"prompt": "What's on my Google Calendar today?"
}
},
"id": "2"
}
Connecting Services
Ensure the user's services are connected in the BlueNexus dashboard at app.bluenexus.ai > Connections.
Example Workflow
A typical n8n workflow with BlueNexus:
- Trigger (Schedule, Webhook, etc.)
- MCP Client / HTTP Request → Call
use-agentwith a prompt - Process response → Extract data from the MCP result
- Output (Send email, update spreadsheet, post to Slack, etc.)
Troubleshooting
Connection timeout: Ensure your n8n instance can reach api.bluenexus.ai on port 443.
401 Unauthorized: Check your PAT is valid and has the universal-mcp-read-write scope.
Tool call errors: Verify the target service is connected and active in the BlueNexus dashboard.