Database Webhooks fail with "schema supabase_functions does not exist

[RENRUN-droid]

Project ref: sedxxfikegepmyouasdm

When creating a Database Webhook (Integrations > Database Webhooks > Create a new hook), I get:

"Failed to create webhook: Failed to run sql query: ERROR: 3F000: schema "supabase_functions" does not exist"

I confirmed pg_net is enabled (extensions schema). The error is identical before and after enabling it. This looks like the internal supabase_functions schema/trigger function was never provisioned for this project. Could someone confirm whether this needs manual provisioning on Supabase's side?

Already opened support ticket SU-485198 (free plan, no guaranteed response) but was told community channels are faster for this kind of issue.

[GaryAustin1]

You need to enable webhooks in the integrations tab.

[RENRUN-droid]

Thanks, but I already checked Integrations > Database Webhooks > Overview
— there's no "Enable" toggle or button there, only a status line:
"Required extensions: pg_net — INSTALLED".

I ran read-only diagnostics to confirm:

select schema_name from information_schema.schemata
where schema_name = 'supabase_functions';
→ Success. No rows returned

pg_net extension is installed (v0.20.4) and its background worker is
running (visible in pg_stat_activity), but the supabase_functions schema
and its http_request() function — which Database Webhooks trigger
functions rely on — were never provisioned on this project.

This looks like an incomplete provisioning of the Database Webhooks
integration itself, not a missing extension. Support ticket SU-485198
is open on this. Would appreciate any pointer on how to trigger that
provisioning manually, or if this needs to be fixed on Supabase's side.

[GaryAustin1]

Check upper right for Install Integration

[PepBunny]

Before spending more time on pg_net, worth checking whether that schema exists at all:

select schema_name from information_schema.schemata where schema_name = 'supabase_functions';

If that comes back empty, no amount of toggling the extension brings it back. The error reads like an extension problem but it is about a schema your project may never have been given, and the webhooks UI is calling a trigger function that lives inside it.

If the row is there, then you are back to permissions on whatever the function creates, and has_schema_privilege tells you more than the error does.