Hi, I need help resolving a persistent Supabase authorization issue.
I’m using the correct API credentials and keys, but every request to the agency or any other table returns:
Authorization failed - please check your credentials: permission denied for table agency
permission denied for table agency
RLS, policies are disabled, and credentials all appear to be set correctly, but the error continues.
Would appreciate guidance on what else I should check or any known issues that might cause this. Thank you!
First test with curl or Postman so you know sure credentials are correct.
Then may be several points to identify the issue(cloud/self-hosted, Docker, npm etc… depending on installation or node versions ) that can lead to wrong env variable configurations.
In terms of credentials, when I was configuring the connection, it showed “Connection tested successfully.”
Does this not fully validate that the credentials are correct?
I also set the credentials directly in the environment variables, so they should be accurate.
Just wondering if this should be enough, or if there are other checks I should perform.
Additionally, I recently found that Supabase has updates regarding API keys.
Is there any chance that these changes could be causing this issue?
A “Connection tested successfully” message in n8n does confirm that the credentials are accepted for a basic connection, but it does not guarante that all permisssions and access levels are correct for every operation you might perform. The test typicaly checks if the credentials can authenticate, but it may not veify access to specific tables or actions (like reading/writing to the agency table).
Soo , even wth a successsful test, you can still encounterr permissioon errors during workflow execution if the API key lacks the necessary privileges or if there are other configuration issues.
