Unable to access my Supabase account or reset password — existing project still connected to n8n

[vascolino]

Hello,

I'm experiencing an issue accessing my Supabase account and would appreciate some guidance.

Background:

On October 29, 2026, I created a Supabase project called ginetos-encomendas to manage customer orders for a small pizza business.

The project is integrated with n8n and WhatsApp Business, and we have already configured database tables, SQL functions, API connections, and an automated ordering system.

The problem:

I can no longer access my Supabase dashboard.

• I am unsure whether I originally registered using email/password, Google, or GitHub.
• I have attempted to recover access using the "Forgot Password" option, without success.
• I cannot identify which authentication method or account was originally used.
• My n8n workflows still contain the existing Supabase API credentials and project URL.
• I do not want to create a new project or risk losing the existing database.

My questions:

1. Is there a way to identify the account associated with an existing Supabase project using its project URL or project reference?
2. Can Supabase Support help recover access to the original account after verifying ownership?
3. If the account was originally created using GitHub OAuth, how can I determine which GitHub account was used?
4. Can existing API credentials help establish project ownership, or are they strictly intended for database/API access?
5. What is the safest procedure to recover administrative access without affecting the existing database, API keys, or n8n integrations?

The project is part of an operational WhatsApp ordering system, so preserving its data and integrations is particularly important.

I can provide the project reference and additional details privately to an authorized Supabase Support representative if needed.

Thank you for your assistance.

[k1ng-arthur]

1. Supabase likely would not be able to tell you the email associated with an account based on project url as those are public anyway
2. Based on 1, haveing the project url does not verify ownership
3. Sign in with all the github accounts or look through your email to see any communication from Supabase
4. Depends on the API credentials, anything that is public like anon/publishable key would not work but something like secret key might work
5. Why not just create a Github/Chatgpt account with all possible emails then sign in. You would get linked to an existing email on the account if there. This is a brute force option though