Supabase Credential - Database and Backend
What is a Supabase Credential
Section titled “What is a Supabase Credential”A Supabase credential allows your workflows to interact with your Supabase project, including PostgreSQL database, user authentication, file storage, and serverless functions.
Configuration Fields
Section titled “Configuration Fields”| Field | Description | Example |
|---|---|---|
| Project URL | Your Supabase project URL | https://abc123.supabase.co |
| Anon Key | Anonymous public key | eyJhbG... |
| Service Role Key | Service role key (full access) | eyJhbG... |
How to Get the Credentials
Section titled “How to Get the Credentials”- Go to supabase.com and sign in
- Select your project (or create a new one)
- In the sidebar, go to Project Settings (gear icon)
- Select API in the settings section
- Copy the following values:
- Project URL: Your project’s URL
- anon public key: The anonymous key (safe for frontend)
- service_role secret key: The service key (backend only)
Key Differences
Section titled “Key Differences”- Anon Key: Respects Row Level Security (RLS) policies. Safe for frontend use. Access is limited according to the security rules you define.
- Service Role Key: Bypasses all RLS policies. Has full access to all data. For server-side use only.
For Floogos, use the Service Role Key since workflows run on the server.
Troubleshooting
Section titled “Troubleshooting”Connection Error
Section titled “Connection Error”- Verify the Project URL is correct and ends with
.supabase.co - Confirm your project is active (inactive projects are paused)
Authentication Error
Section titled “Authentication Error”- Verify you’re using the correct key (anon vs service_role)
- Keys are JWTs, make sure to copy the complete value
Table Access Denied
Section titled “Table Access Denied”- If using the Anon Key, check the table’s RLS policies
- With the Service Role Key, there should be no access restrictions
Project Paused
Section titled “Project Paused”- Free projects are paused after inactivity
- Reactivate the project from the Supabase dashboard
Security
Section titled “Security”- Never expose the Service Role Key in frontend or public repositories
- The Anon Key is safe for frontend but configure proper RLS policies
- Use the Service Role Key only in server environments
- Configure RLS policies to protect your data
- Monitor usage from the Supabase dashboard
- Rotate keys if you suspect they were compromised (from Project Settings > API)