cli: Schema supabase_functions does not exist (local development)
Bug report
Describe the bug
When trying to create a Database Webhook function in my local Supabase Studio, I get the following error:
Failed to create hook: schema "supabase_functions" does not exist
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- Start local supabase dev environment
supabase start(while Docker is running) - Open the local Supabase Studio (http://localhost:54323/project/default)
- On the left menu, go to Database
- Select Webhooks, enable them in Alpha and create a test webhook
- See error
Failed to create hook: schema "supabase_functions" does not exist
Expected behavior
The Database Webhook should have been created correctly
Screenshots

System information
- OS: Windows 10
- Browser (if applies) Chrome
- Version of Supabase CLI: 1.40.1 (latest available in Scoop as of today)
Additional points
- When doing it on the cloud instance, the Database Webhook is created correctly. If I then go to Table Editor => Schema
supabase_functions-> TablehooksI see it empty. Is this correct? From the error above I assumed created Webhooks would be stored there. I see the Webhook in Database => Webhooks though. - Are Webhooks captured as part of migrations and added to the sql file when a new migration is created?
Thanks!
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (3 by maintainers)
@Pictor13 @kingraphaii I got this issue but it was solved by enabling webhooks in destination database.
Yes, you can enable it via config.toml. For eg.
Is there a way to enable webhooks programmatically or via the sql script?
I am running
supabase migration upon my test container using imagesupabase/postgres:15.1and the migration requiring webhooks is failing every time.In the platform, navigate to “Database” from sidebar -> “Webhooks” under platform section & enable it
Its not happening to me locally but in GitHub actions. This is the migration command
and my
ci.yamllooks like thisAnd the error I get on running the migration is
Hi @mousindev , did you ever find a solution to this on local dev?
Hi, thanks for the fix! I see Scoop is still few versions behind (1.40.1) as of now compared to NPM updated yesterday to 1.42.7. Any timeline on when will Scoop be updated?
Thanks!