Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Memberships

Brendan's AI Community

21.9k members • Free

AI Automation Club Elite ⚡

219 members • $34/m

NextGen Lite

2.3k members • Free

AI Automation Club

247 members • Free

Automatable

442 members • $70/m

AI Accelerator

16.3k members • Free

AI Navigator

568 members • Free

AI Automation Champions

850 members • Free

n8n AI Agents

903 members • Free

9 contributions to AI Automation Society
timestamp issue
I’m working on a voice-powered booking system that uses Retell AI to talk to callers and n8n as the backend. Retell collects all the booking details, confirms the exact UK date and time with the caller, and then sends one clean function call into n8n, for example: Book a table for four under Michael on 25/11/2025 at 2 PM. n8n’s Calendar Agent is then supposed to interpret this text and create, update, or cancel the event in Google Calendar. What’s going wrong Even though Retell now always sends explicit UK-format dates (dd/mm/yyyy) after confirming with the caller, the Calendar Agent inside n8n sometimes reinterprets that date — usually by shifting the year backwards (e.g., 2025 → 2024) or otherwise assuming a different date before creating the Google Calendar event. There are no node errors; the workflow technically “works”, but the booked date in Google Calendar is sometimes wrong unless the caller corrects it manually during the conversation. A typical example Retell sends: Book a table for four under Paul on 26/11/2025 at 11 AM. But the Calendar Agent replies with: “Do you mean Wednesday 27/11/2024?” Which is obviously not what was said. This behaviour suggests the LLM inside the Calendar Agent is unnecessarily re-interpreting an already explicit date. What I've already tried I rewrote the Retell system message completely (the new 26 November version): Anchors today’s date Forces future-only dates Requires explicit dd/mm/yyyy internal conversion Confirms the exact UK date verbally with the caller before sending anything to n8n Ensures Retell never sends vague phrases like “next Tuesday” in the backend call I also updated the n8n Calendar Agent system message: If chatInput already contains a numeric UK date, it should trust that date 100% It should not convert “26/11/2025” into anything else It should only reject dates that are actually in the past Removed all automatic reinterpretation of relative dates when an explicit one is provided Removed availability checks unless the caller explicitly asks for it
0 likes • 17d
@Ridwan Bryan Thanks Ridwan. I’ve implemented strict date confirmation on the Retell side and tightened the n8n agent so it trusts explicit dd/mm/yyyy. It’s already performing much better now. If I still get edge cases, I’d definitely appreciate a second pair of eyes. Thanks again!
1 like • 17d
@Lucas Davis Thanks Lucas — agreed, structured fields are definitely the most stable long-term approach. I may go that direction later. For now I’ve tightened Retell and n8n so explicit dd/mm/yyyy is always respected, but I’ll revisit this if I need a fully structured setup. Really appreciate the offer!
Twilio Keeps Using a Ghost TwiML App Instead of My TwiML Bin
Hey everyone, I’m stuck on something strange and hoping someone has seen this before. I switched my number’s inbound handler to a simple TwiML Bin to dial Retell’s SIP server. The number is definitely set to: Configure with: TwiML Bin A call comes in: Retel SIP dial (my TwiML Bin) Primary handler fails: Retel SIP dial No webhook No Studio Flow No Functions No Proxy No TwiML Apps (confirmed the TwiML Apps page is completely empty) The problem: Twilio still routes every call to a TwiML App URL that doesn’t exist anymore. In the call logs I see Twilio POSTing to this old handler: https://handler.twilio.com/twiml/EH2961c93e597b35174275e1ec153e1f10 But this TwiML App is NOT in my account and isn’t assigned anywhere. Every inbound call hits this ghost URL, then the SIP leg instantly returns “Busy”, and the call ends immediately. I’ve tried reselecting the Bin, saving again, switching to webhook and back, recreating the Bin—nothing changes. Where is Twilio pulling this old TwiML App from, and how do I force it to actually use the TwiML Bin that’s selected? Thanks!
Call receptionist agent (Retell + Twilio) app error
Hey everyone, I’m trying to connect our Twilio BYOC trunk (bci-tech-trunk.sip.twilio.com) with our Retell voice agent so it can answer incoming calls. When we call the Twilio number, it connects but plays: “We’re sorry, an application error has occurred. Goodbye.” Twilio’s logs show Error 11200 (HTTP 404) — “Cannot POST /v2/handle-call” fromhttps://api.retellai.com/v2/handle-call?agent_id=agent_7ce1************03d&retell_api_key=key_2***********049.I also tried switching it to GET, but the same issue happens. We’ve checked all the Twilio settings — BYOC trunk, SIP domain, transport set to TLS, and tested /v2/handle-call, /v2/handle-call/twilio, and /v2/create-phone-call. Secure media has been tested on and off, same result. Could someone confirm what the correct Twilio webhook endpoint should be for this setup, and whether inbound SIP from Twilio should authenticate via IP/TLS trust instead of credentials? Troubleshooting I’ve Tried - Verified Twilio BYOC trunk and SIP domain setup - Tested both HTTP GET and POST - Tried multiple Retell endpoint paths (/v2/handle-call, /v2/handle-call/twilio, /v2/create-phone-call) - Confirmed origination target = sip:sip.retellai.com;transport=tls - Tested with Secure Media enabled and disabled - Retell webhook in place: https://bci-tech-trunk.pstn.twilio.com Still getting the same “application error” message and 404 logs from Retell’s API. Environment details: - Integration type: Twilio BYOC (SIP trunking) - Retell Workspace: BCI Tech - Agent ID: agent_7ce1************03d - Twilio Domain: bci-tech-trunk.sip.twilio.com - Secure Media: tested ON/OFF - Browser: Chrome - OS: Chrome OS Thanks for the help!
0 likes • Nov 11
@Kendra Esther That would be great please and thank you!
0 likes • Nov 11
@Chad Samuel Thanks for the insight! Yeah, we thought the same at first — but it turns out Retell doesn’t actually use /v2/handle-call for Twilio SIP connections. That endpoint only handles HTTP-based calls, not SIP traffic. After checking with Retell support, they confirmed the proper setup is via SIP trunking, routing calls directly to sip:sip.retellai.com instead of posting to an HTTP webhook. Looks like we were just sending the call the wrong way around. We’re reconfiguring Twilio now to route over SIP only — hopefully that clears the 404 and gets the AI answering properly. I’ll update once tested!
Help needed to prep workflows for commercial use ongoingly.
Hi community! We are not fixed on any particular kind of help but open to what can be offered. Ultimately our goal is to set up 4 core workflows that we can then sell as part of the ai business solutions agency i am trying to build. Aren't we all! The work flows are a personal assistant, social media content creator/poster, lead scraper and cold email outreach campaign systems. We will eventually look at a cold call/call response workflow too but for now just the first 4. All workflows have been taken from mainly Nates templates initially and built out from there. We would like to find someone we can work with ad hoc on an ongoing basis to just help us where needed and in the first instance help us make these workflows as good as possible and explain certain areas so we understand the technical side a bit more to be able to manage and maintain them. Is this something anyone here could help with and could we perhaps jump on a video call for 10 mins first to just chat through possibilities? This might give you a better understanding of what we are looking for and us an idea of what you can offer/costs etc. I am on UK time for any zoom/teams/google meet video calls. Thank you and I look forward to hearing from you! Best Chris
1 like • Sep 2
@Georgeline Parker A quick call would be great. DM me and we can arrange a time. I am looking at around 6pm CET as in Spain currently.
1 like • Sep 2
@Kai Huxmann Hi Kai, you are right there is more to this than meets the eye! I am sure you can tell. We need support for 4 distinct workflows at the moment to bring them to a pro level ready for deployment in a real company setting for another business of mine that rents properties. We then want to use the systems for other businesses as part of an ai automation agency selling these systems but at that stage we would look to have a UI dashboard for one or all of them tied together. Hope that helps and perhaps a 10 min video call tomorrow if you have time? DM me and we can go from there. As per my previous answer I am in Spain so 6pm CET would be Ideal..just back from the beach then! Ha!
Email agent debugging
Hi everyone, I’m working on an Email Agent workflow that integrates with Gmail via n8n. At one point, everything was working as intended: Send Email — Worked perfectly Reply to Email— Was functioning reliably Summarise Emails — Also worked well Delete Email — Never worked correctly (wrong message deleted once, then failed) My goal is to restore full functionality for Send, Reply, and Summarise and only troubleshoot Delete later. Current Setup The workflow uses the following Gmail nodes: Get Many Messages (returns 3 emails, limit set, not simplified) Send Email (fields dynamically populated by AI) Reply to Email (uses ID extracted from Get Many Messages) Delete Email (same, but currently deprioritized) Tool routing and inputs are managed via a separate GPT-powered “main agent” that: Routes the user’s request to this Email Agent Dynamically generates fields like to, subject, body, and id using AI What Changed? Recently, summarizing and replying both started failing with: “Bad request - please check your parameters” or “OpenAI: Rate limit reached” The send function was still working… until even that failed during our latest testing. I suspect the issue is either: Tool names mismatching between system message and n8n node labels Message id not being passed correctly between GetManyMessages and the reply/delete nodes Or AI not generating required fields under some conditions What I’ve Tried: Confirmed correct settings: Return All = Off Limit = 3 Simplify = Off Sender filter = removed completely Ensured Send Email uses: js CopyEdit To: {{ $json.to }} Subject: {{ $json.subject || 'No Subject' }} Message: {{ $json.body || 'No message provided.' }} Ensured Reply and Delete use: js CopyEdit Message ID: {{ $json.id }} All inputs are generated via AI; no hardcoded expressions like $json.response[0].id What I Need Help With Why summarize and reply are failing even when Get Many Messages returns emails correctly How best to pass id from GetManyMessages → ReplyToEmail
1-9 of 9
Chris Peters
3
16points to level up
@chris-peters-1549
Recently graduated in Computer Science and looking to start using ai and automation tools for my property business and then for others.

Active 6d ago
Joined Apr 7, 2025
Norwich
Powered by