Report: Google Gemini API (Veo) Integration Issue with Make
Date: July 13, 2025
1. Overview of the Problem
The user is attempting to automate video creation using the Google Gemini API (specifically its video generation feature, Veo 2/3) via Make (formerly Integromat), and then post these generated videos to Instagram.
The primary issue encountered is two-fold:
- Initial Challenge (Technical Compatibility): The Gemini API, when generating a video, provides a URL to the video file. Instagram’s API, however, typically requires the direct upload of the video file itself, not just a URL. This necessitates an intermediary step to download the video from the provided URL before uploading it to Instagram.
- Persistent API Error (Core Issue): A more critical and persistent problem has arisen during the Gemini API call within Make. The user consistently receives a
403 PERMISSION_DENIEDerror with the following message:"Generative Language API has not been used in project 542708778979 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/generativelanguage.googleapis.com/overview?project=542708778979 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry."The user’s actual Google Cloud Project ID is934992392394. Crucially, the user explicitly states they do not own or have access to any Google Cloud Project with the ID542708778979. Despite this, the error message continues to reference this unknown project ID.
2. Troubleshooting Steps Already Attempted
The user has diligently performed the following troubleshooting steps:
- Verified Generative Language API Enablement: Confirmed that the “Generative Language API” is enabled within their correct Google Cloud Project (
934992392394). - API Key Regeneration: Generated new API keys specifically within project
934992392394multiple times. - API Key Restriction Configuration: Applied API restrictions to the newly generated keys, limiting them to the “Generative Language API” for enhanced security.
- Make Connection Update: Deleted all existing Google Gemini AI connections within Make and created entirely new connections using the freshly generated API keys from project
934992392394. - Isolated Testing: Attempted to run a brand new, simple Make scenario with only the Google Gemini AI module and the new connection, but the same error persists.
- Account and Project Verification: Double-checked that they are logged into the correct Google account and that project
934992392394is actively selected in the Google Cloud Console when performing all Google Cloud-related actions.
3. Analysis of the Persistent Issue
The continued appearance of the 403 PERMISSION_DENIED error referencing an unknown project ID (542708778979 ), even after exhaustive troubleshooting, strongly suggests that the issue is not a misconfiguration on the user’s part regarding their owned Google Cloud Project (934992392394 ) or API key.
Based on recent reports from other users in Google AI developer forums (as identified in external searches), this specific error pattern (403 with an unrecognized project ID for Generative Language API, especially with Veo) has been reported by others.
Likely Cause: It appears there might be an internal routing or association issue on Google’s backend when API calls are made to the Generative Language API (particularly for features like Veo) via third-party platforms like Make. The system seems to be, for certain requests or accounts, implicitly attempting to route or validate the request through an internal or default Google Cloud Project (542708778979 ) that is not owned by the user, and where the necessary API is not enabled for that specific internal project’s use .
This indicates a potential bug or an undocumented behavior in Google’s API gateway or the specific integration’s interaction with it.
4. Recommended Next Steps
Given that the user has performed all reasonable troubleshooting on their end, the resolution requires intervention or further diagnosis from the service providers:
- Report to Google AI Developers Forum:
- Create a detailed post on the Google AI Developers Forum (
https://discuss.ai.google.dev/). - Include the full error message, both your project ID (
934992392394) and the unknown project ID (542708778979), and a clear description of all troubleshooting steps taken. Emphasize that you do not own the referenced project. This allows Google’s engineering team to investigate the routing issue on their side.
- Contact Make Support:
- Open a support ticket with Make.
- Provide them with the same comprehensive details: the exact error, your project IDs, the fact that you’re using their Google Gemini AI module for Veo, and the extensive troubleshooting you’ve already performed. Make may have specific internal knowledge or workarounds for this particular Google API behavior.
By reporting this issue through the appropriate channels, Google and Make can work to identify and resolve the underlying problem that is preventing successful API calls.
