xenogeneic-maroon•3mo ago
Mcp not working
I don’t know what’s going on here. I’m watching a video of a guy using n8n mcp so Vapi agent can send caller an email while they’re on the phone and I’m following it to the letter. it just doesn’t work
12 Replies
Thanks for sharing your setup. To help you further, could you please specify what exactly happens when you try to use the n8n MCP with your Vapi agent—do you see an error message, or does the email simply not send without any error? Any details or screenshots of the error would be helpful.
Sources:
- Vapi MCP Tool Documentation
- Vapi MCP Server Documentation
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
xenogeneic-maroonOP•3mo ago
My agent tells me it’s experiencing a technical error and cannot send the email. It also does not trigger the n8n mcp
adverse-sapphire•3mo ago
Ensure your Vapi assistant prompt asks for the caller’s email, confirm the n8n webhook URL is correctly set in Vapi, and check n8n logs to verify it receives data and the email node is properly configured, most issues stem from prompt clarity or misconfigured workflows.
xenogeneic-maroonOP•3mo ago
I’ve done all this
adverse-sapphire•3mo ago
Send your call id
xenogeneic-maroonOP•3mo ago
b15491fa-b985-40f7-821b-2bce1144be6e
ive even tried self hosting n8n on two separate hosting platforms
adverse-sapphire•3mo ago
Looking into it
automatic-azure•3mo ago
@thecurtis Hey! To help track down this issue, could you also share:
- The correct call ID
- When exactly this happened (the timestamp)
- What response you expected to get
- What response you actually got instead
This would really help us figure out what went wrong!
xenogeneic-maroonOP•3mo ago
I gave all of this information already
But I’ll try and explain it again
It would be helpful if I could could actually talk to someone. Like zoom call with screen share
Alright, so now I’ve got it working “some” of the time. It seems when I switch the model it works for a while then breaks.
I was using the 4o mini first as wasn’t working at all, I switched to 4o and was working for a bit then started breaking again. Then 4.1 and so on. Super interesting
Hey can you share the recent non-working call_ids as well?
xenogeneic-maroonOP•3mo ago
I actually think I’ve figured it out! I think I was making edits and testing too quickly for Vapi and n8n to keep up. I left it alone for an hour or so and tried again and it seemed fine.
I just made a couple more little tweaks so I’m gonna give it a bit. I did notice a funny little thing though. It’s 8:01pm in my local time zone now, but the agent thinks it’s the next day. In my prompt I have “the time is {{now}} Canada/Vancouver time zone”. Is this correct?
This solution directly addresses the root cause by:
1. Using the proper LiquidJS syntax that VAPI supports for time zone-aware date formatting
2. Leveraging the existing time zone handling that's already built into the system (as shown in the test cases)
3. Using the correct IANA time zone identifier which is what JavaScript's Intl API expects
4. Avoiding the UTC hardcoding in the basic {{now}} variable