Skip to content
Veo 2 and callin.io...
 
Notifications
Clear all

Veo 2 and callin.io: Any success stories?

9 Posts
3 Users
0 Reactions
4 Views
Anthony_Roger
(@anthony_roger)
Posts: 10
Active Member
Topic starter
 

Describe the problem/error/question

I've made two successful calls to the VEO API, which returned a URI. The issue is that this URI results in a 403 error, indicating a GCP project that I do not possess. I'm quite confused about the origin of this project ID, as it's not linked to any API key nor is it part of my current workflows.

I'm unsure how to troubleshoot this since I cannot access the project in question.
Thanks for any guidance.

image

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your callin.io setup

  • callin.io version:
  • Database (default: SQLite):
  • callin.io EXECUTIONS_PROCESS setting (default: own, main):
  • Running callin.io via (Docker, npm, callin.io cloud, desktop app):
  • Operating system:
 
Posted : 27/05/2025 8:55 pm
Grot
 Grot
(@grot)
Posts: 13
Active Member
 

Hi, could you share your workflow.

n8n attach workflow

 
Posted : 27/05/2025 10:21 pm
Anthony_Roger
(@anthony_roger)
Posts: 10
Active Member
Topic starter
 
 
Posted : 28/05/2025 3:14 am
King_Samuel_David
(@king_samuel_david)
Posts: 55
Trusted Member
 

It appears you might need to enable this within your Google Console.

Are you using callin.io cloud or a self-hosted instance?

Best regards,

Samuel

 
Posted : 28/05/2025 4:01 am
Anthony_Roger
(@anthony_roger)
Posts: 10
Active Member
Topic starter
 

Thanks Samuel, I've checked and the issue is that Gemini is indeed enabled in GCP. The error message refers to another GCP project that I don't have access to. What I'm struggling to understand is where this GCP project is originating from, as I don't reference it in any of my API calls. I've even searched for that project ID in GCP, and it doesn't exist. I'm using the cloud version of callin.io.

 
Posted : 28/05/2025 11:09 am
King_Samuel_David
(@king_samuel_david)
Posts: 55
Trusted Member
 

Okay, if you are using the cloud version, it's likely in your workspace. Did you have to set up a client ID and secret, or was the login button present to authenticate with the credentials? I believe you might have used httpQueryAuth.

You could try changing the generic credential type and modifying the authentication type. This would involve creating an app and assigning the correct permissions, which would likely resolve the issue.

or perhaps predefined

and follow this: Google OAuth2 single service | callin.io Docs

Once set up and the Gemini API is added, you should be all set.

Hope this helps,

Samuel

 
Posted : 28/05/2025 1:49 pm
Anthony_Roger
(@anthony_roger)
Posts: 10
Active Member
Topic starter
 

First, thank you, Samuel! I really appreciate the pointer, as I spent an excessive amount of time trying to fix the issue.

So, first, I believe your solution may resolve the problem. It seems this Gemini model only accepts OAuth or a service account. When I used my API key in my query, I might have bypassed some controls, as I received results, but it was blocked at the end. (I was charged by Google for some successful calls but couldn't access the file…)

Now, for the next issue: I've been trying to set up OAuth2 and have followed all the steps listed on your site. The problem lies with the Google API documentation, which doesn't specify the scope I need for my app. I found three scopes (two restricted, one none) but haven't had any luck setting them up. If anyone has recommendations regarding the scope required to access VEO 2, I would be extremely grateful.

 
Posted : 28/05/2025 3:10 pm
King_Samuel_David
(@king_samuel_david)
Posts: 55
Trusted Member
 

Hey

Just to confirm it’s not my site, haha, but callin.io am just being a community member trying to help others out.

Alot of people do say similar things, like you must been working here for ages, no i’ve just been in IT my whole life haha I don’t directly work for callin.io yet.

So just to confirm, does the scopes appear as error message now? normally you can just add the Gemini api, and enable it. I believe this should add most the scopes needed. (I could be wrong)

But is this all enabled now? and you see the error in callin.io for scopes, when making request?

Am uk based, veo 2 isn’t avaible yet to us

:frowning:

Best regards,

Samuel

 
Posted : 28/05/2025 4:43 pm
Anthony_Roger
(@anthony_roger)
Posts: 10
Active Member
Topic starter
 

Thanks Samuel. So I checked the callin.io supported scope and gemini isn’t there. So instead of Oauth I had to revert back to a service account. I used the predefined credential, got my API calls working with my AI Studio key but still get this error message. I guess the model being somewhat new, it isn’t supported yet by callin.io so will need to wait I guess. Thanks anyway for all the help, I think we exhausted all paths.

 
Posted : 28/05/2025 5:20 pm
Share: