Nago Issues to keep connection to external service...
# support
s
Dear Support, It appears that your platform is experiencing integration issues with services such as Slack and Google Calendar. I have attempted to connect several services, but after running the assistant setup—whether via chat or call assistant—I receive a notification that Nango is not functioning properly. I have tested both the Slack tool ('slack_send_message_tool') and your Google Calendar tools ('google_calendar_check_availability_tool' and 'google_calendar_tool', etc.). These problems seem to occur primarily during initial setup of connections, especially if no connection exists yet via “Integrations.” This may also be challenging for your QA team, since many of them already have an active connection. It seems that during the initial Nango dialogue with an external service, the connection works, but afterward it does not appear in the integration overview (meaning you cannot disconnect these connections—only attempt to reconnect). The community has also been discussing this issue. I have been struggling with this for several days and have debugged the situation as described. When can a fix be expected? I would prefer not to have to rely on a workaround using Make.com. Not want to waste time for testing with web hooks and API setups as well. Also not sure if this is currently working (for new users). A call ID I cannot provide, but the other information. 2 screenshots attached. One is after the tango connection and the other ist the chat error message of nango. Please also see this entry by another user, which suggests this is a general issue: Error with Google Calendar Connection: “Missing Nango config...” https://vapi.ai/community/m/1422628864772931655 Thank you, Stefan #1211483291191083018 https://cdn.discordapp.com/attachments/1422849567019368561/1422849567484809347/PastedGraphic-1-3.png?ex=68de2b6c&is=68dcd9ec&hm=d84a5ec255f718306065f62b63dd7e5b5142342f3436a4cd9396078d2c46c167& https://cdn.discordapp.com/attachments/1422849567019368561/1422849567891787787/PastedGraphic-2-1.png?ex=68de2b6c&is=68dcd9ec&hm=8cf22bb63303fecfcd3b524aa44969bbf0bca0e65db3cdbf268435bfa020496e&
v
Thanks for sharing, Stefan. I’ve seen similar issues where the Nango handshake works initially but the config doesn’t persist, so tools like Slack or Google Calendar fail during assistant setup. A quick test is to reconnect directly via the Integrations panel first, then run the assistant—this helps confirm if it’s a storage issue or tool call error. Could you try that and let me know what result you get? From there, I can assist you directly to fix or apply a stable workaround. @Stefan. Stallmann
s
THX for replying. But this it NOT working. For sure, I tried to reconnect both via Slack and Google Calendar. No step further ...
v
Thanks for confirming, I understand reconnecting didn’t solve it. In this case, we can take another approach by checking the Nango config and fixing the way the connection is stored. I can handle this directly for you and make sure the Slack and Google Calendar integrations work as expected. Just share the access details you’re comfortable with, and I’ll take care of the setup.
@Stefan. Stallmann
g
I have the same problem, can someone help me?
n
same issue
how to fix?
@User any update?
m
I'm having the same issue.
c
Hi Stefan. Stallmann, To connect to Google Calendar and manage events, ensure you've configured the OAuth2 credentials. You can set this up via the [dashboard > Build > Provider Keys](https://dashboard.vapi.ai/keys#:~:text=Google%20Calendar). If you're experiencing issues with missing configuration, double-check that the credentials are correctly input and saved in the Vapi dashboard. For using the Google Calendar tool directly from your assistant, you can utilize the full CRUD operations via the `/tool`[ API endpoint](https://docs.vapi.ai/api-reference/tools/list). If the connection issue persists, consider re-authenticating this setup. For further assistance on OAuth2 and configuration, you can refer to the [March 20, 2025](https://docs.vapi.ai/changelog/2025/3/20) and [March 28, 2025](https://docs.vapi.ai/changelog/2025/3/28) changelogs for additional context.
3 Views