n8n support means that you are using a self-hosted n8n instance running on Railway, not an n8n Cloud account. Therefore, your workflows will not appear when you log in at n8n’s main website—they are stored inside the n8n database connected to your Railway project.

Try the following:

1. Log in to the Railway dashboard using the same email or GitHub account you originally used.
2. Check every Railway workspace/team available from the workspace selector.
3. Open the project containing the n8n service. It may also contain services named PostgreSQL or Redis.
4. Click the n8n service and go to Settings → Networking → Public Networking.
5. Open the existing *.up.railway.app domain. If no domain exists, click Generate Domain.
6. Sign in using the email and password you created when you first configured that n8n instance. Your normal n8n Cloud login may not be the same account.

If the page asks you to create a completely new owner account, or it opens with no workflows, do not complete the setup, redeploy the template or delete anything yet. This usually means n8n is no longer connected to its original database or storage.

In Railway, check:

• Whether the original PostgreSQL service is still present and running.
• Whether the n8n service still has its database variables, such as DB_TYPE and DB_POSTGRESDB_*.
• Whether a persistent Railway volume is still attached to the n8n service.

n8n uses SQLite by default unless PostgreSQL was configured. SQLite data and the encryption key are normally stored in n8n’s user-data folder. Railway’s normal service filesystem is temporary between deployments, so SQLite installations need a persistent volume to protect their data.

Do not delete the PostgreSQL service or volume, since this could permanently remove the workflows.

If you cannot see the Railway project at all, you are probably signed into a different Railway account or workspace. Check your email for old Railway deployment or billing messages to identify the correct login. Once the original project, database and volume are located, the automations should normally still be recoverable.