Restore n8n workflow from Supabase backup file

Questions
1

Describe the problem/error/question

Hi everyone,
I previously deployed my n8n workflows using ClawCloudRun free hosting together with Supabase. Unfortunately, ClawCloudRun suddenly discontinued its free plan, and I did not manage to migrate to another hosting provider before the deadline.
As a result, I am now facing a data recovery problem. At the moment, the only thing I was able to download is a backup file from my Supabase database.
I would like to ask for advice on how I can restore my n8n data and workflows from this backup, or whether it is still possible to recover the instance in another environment.
Has anyone experienced a similar situation, or can anyone suggest the best way to proceed?
Any guidance would be greatly appreciated. Thank you.

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 2.22.6
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app):Docker
  • Operating system:
2

Hey @energyharvester, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@King_Samuel_David, @Bishant_Baniya - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

3

Hi @energyharvester Welcome!
If Supabase was n8n’s own database, that dump holds everything and you only need a fresh instance pointed at a restored copy of it. Check that first:

grep -c workflow_entity your-backup.sql

If that returns 0, n8n was running on the container’s SQLite and the dump only has data your workflows wrote, not the workflows themselves.
If the table is there, restore the dump into any Postgres (a new Supabase project is fine), then start n8n against it:

DB_TYPE=postgresdb
DB_POSTGRESDB_HOST=<host>
DB_POSTGRESDB_PORT=5432
DB_POSTGRESDB_DATABASE=<database>
DB_POSTGRESDB_USER=<user>
DB_POSTGRESDB_PASSWORD=<password>
DB_POSTGRESDB_SCHEMA=public

Workflows come back exactly as they were. Credentials sit in the database encrypted with N8N_ENCRYPTION_KEY, which n8n generated into ~/.n8n/config on the old container, so unless you set that key yourself you will need to re-enter credentials after the restore.

For picking where to redeploy: