https://vapi.ai/ logo
Join Discord
Powered by
Error while working with the dynamic Google Calend...
# support
a
I am using the Nango service to obtain the connection ID and sending it via the VAPI Update Assistant API in the "credentials" object:
Copy code
"credentials": [
  {
    "provider": "google.calendar.oauth2-authorization",
    "authorizationId": "<nango_connection_id>"
  }
]
Then, I attach the google_calendar_tool and google_calendar_check_availability_tool to that assistant. When I test the assistant, I receive the following error:
Copy code
{
  "error": {
    "message": "Request failed with status code 404",
    "data": {
      "error": {
        "message": "No connection matching the provided params of 'connection_id' and 'provider_config_key'. Please make sure these values exist in the Nango dashboard {\n  \"connectionId\": \"99b2023a-c80e-4606-8241-1002baeb52cf\",\n  \"providerConfigKey\": \"google-calendar\"\n}",
        "code": "unknown_connection",
        "payload": {
          "connectionId": "99b2023a-c80e-4606-8241-1002baeb52cf",
          "providerConfigKey": "google-calendar"
        }
      }
    }
  }
}
I checked the Nango dashboard, and it contains both the given connection ID and providerConfigKey. What I need to fix? It looks like there should be a way to pass my Nango account token to VAPI so that it can find the details for the given connection ID.
m
Facing a similar issue. Just bumping this
c
Could you please share a call id where this error occurred?
a
@User @User here you go - 5c315d83-14ab-4c8d-9af8-bc6f4535264b
c
Can you please verify that the connection exists through the API?
Copy code
curl -X GET "https://api.nango.dev/connection/99b2023a-c80e-4606-8241-1002baeb52cf?provider_config_key=google-calendar" \
  -H "Authorization: Bearer YOUR_NANGO_SECRET_KEY"
a
@User @User yes, I am getting the details and connection exists. My question is how you will you call this api without YOUR_NANGO_SECRET_KEY key. How to send that NANGO_SECRET_KEY to the VAPI.
k
Use Nango to handle the OAuth2 flow, get the connectionId, and pass that connectionId to your VAPI assistant credentials, this lets vapi access the API without directly sending your NANGO_SECRET_KEY.
a
@Kings_bigđź’« that's what I am doing but getting the above mentioned error
k
Share call_id
a
@Kings_bigđź’« already shared in the above message - here you go - 5c315d83-14ab-4c8d-9af8-bc6f4535264b
c
Hey Ankur, thanks for sharing your details. Our team will look into it and get back to you soon with an update.
The issue is not with the assistant's ability to use the authorizationId - it's doing that correctly. The problem is that the Nango connection with ID 99b2023a-c80e-4606-8241-1002baeb52cf doesn't exist or has been deleted from the Nango dashboard. This can happen when: 1. **Connection Expired**: The OAuth connection to Google Calendar expired and was automatically removed from Nango 2. **Manual Deletion**: Someone manually deleted the connection from the Nango dashboard 3. **Sync Issues**: There's a mismatch between what Vapi thinks exists and what actually exists in Nango 4. **Wrong Nango Environment**: The system might be pointing to the wrong Nango environment (dev vs prod) The solution here is to reconnect google calendar which will create a new Nango connection ID, check Nango dashboard to make sure it exists, then the system should update to the newest credentials. Let us know if you encounter the same error after the changes
a
@User @User Yeah, I already tried reconnecting google and verify everything again. But issue still persists.
c
Can you share a call id where the issue occurred? We will review the logs to see if the auth is failing
a
Here you go - here you go - 5c315d83-14ab-4c8d-9af8-bc6f4535264b
m
Hi everyone, I was wondering if this issue has been resolved? @Kings_bigđź’«
c
Ankur could you please reconnect it once more then try again? We would like to check if the logs are still encountering the error.
MaxwellZhou if you also have this issue with nango, could you please reconnect it and run a test call afterwards? Also please share a call id
a
Yes, I have connected it again. but still getting the same error again. @User @User
{ "error": { "message": "Request failed with status code 404", "data": { "error": { "message": "No connection matching the provided params of 'connection_id' and 'provider_config_key'. Please make sure these values exist in the Nango dashboard {\n \"connectionId\": \"910bc5b0-ef03-4dfe-a1eb-f9fa3813353c\",\n \"providerConfigKey\": \"google-calendar\"\n}", "code": "unknown_connection", "payload": { "connectionId": "910bc5b0-ef03-4dfe-a1eb-f9fa3813353c", "providerConfigKey": "google-calendar" } } } } } this is what I am getting
I still haven't received an answer to this question: How is Vapi able to get the connection details using the connection ID when I haven't shared the Nango API key with Vapi, since there is no place to set that up in Vapi?
c
Vapi uses its own built-in Nango integration for handling authentication. This means the connection is managed on our side, not through a Nango API key that you provide. Because of this setup, you can’t customize where the auth is coming from. If you connect your Google account (or another service) directly with Vapi, the authentication is stored securely through Vapi’s Nango integration. This ensures the same security level as your current setup, without requiring you to manage a separate Nango key.
a
so why its not working? I am generating the nango connection id for my users calendar and passing it when updating the assistant. @User @User
c
This isn’t working because you’re generating the connection ID from your own Nango account. Vapi uses its own Nango account to store Google credentials. To fix this, connect your Google account through the Vapi dashboard → Integrations page. Once connected there, your credentials will be stored under Vapi’s Nango account and available to your assistants.
a
@User @User That will work only for the one google calendar. But in my case, I want to give the option to user to connect their own google calendar each assistant.
c
The best way to manage this would be to create an org for each user, that way only one credential is tied to one org. You might want to also make a feature request to our roadmap suggesting multiple google credential handling for one org. This would make a great addition to our platform and make it more powerful than it already is. If you would like to see that feature on our platform, feel free to add it to the feature request list here -->
PreviousNext
Powered by