https://retellai.com/?utm_source=discord&utm_medium=seo logo
HubSpot calling error
# ❓・bug-report
m
Usually HubSpot workflow calling via retell works, but I just received an error as follows with no additional info: "There was a problem completing this action. We didn't get a response from the connected app." https://cdn.discordapp.com/attachments/1465059795223711947/1465059796167295168/image.png?ex=6977bac2&is=69766942&hm=a9083e425c79f85aca592f9738513d09aaf1e4c8c7cecd8886687761454456c4&
f
I can help troubleshoot this! The error usually means either: The Retell API timed out or didn't respond There's a connectivity issue between HubSpot and Retell The phone number or call parameters were invalid Question: Was this a one-time error or is it happening consistently? Also, did anything change recently in your Retell configuration or the phone number you're calling?
m
consistently. no change to configs.
f
Thanks for clarifying. Since it's consistent and nothing changed in your configs, this points to either an API connection issue on Retell's end or a webhook timeout problem in HubSpot. I'd be happy to dig into this for you and get it resolved. I can check the API logs, test the connection, and fix whatever's causing the block. Would you be open to discussing this privately so I can take a closer look at your setup?
m
prefer to do it publicly. i'm not sure who you are.
s
Hi @mush error typically indicates a timeout or connection issue between HubSpot and Retell AI. Verify your retell connection with hubspot and check your API key if it is valid or not
m
retell shows connected to hubspot within the hubspot app. there's no further way to diagnose anything relating to a timeout. can you help dive deeper to troubleshoot why this stopped wworking and confirm it will work next time? it used to work just fine, and then stopped working a couple days ago (no changes made on my end) https://cdn.discordapp.com/attachments/1465059795223711947/1465335312728199198/image.png?ex=6978bb5b&is=697769db&hm=cf4c97557c748ecf1022e54443cf6e22c1a1edaa64f22fb225557f26635614a7&
s
Did you tried to disconnect and then reconnect
m
no - is that the only troubleshooting step or can you review the logs?