[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M796JCRSNBH4TQYY9FS9E4DR":3,"skill-same:01M796JCRSNBH4TQYY9FS9E4DR":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M796JCRSNBH4TQYY9FS9E4DR","supabase-webhooks-events",null,"Implement Supabase database webhooks, pg_net async HTTP, LISTEN\u002FNOTIFY,\nand Edge Function event handlers with signature verification.\nUse when setting up database webhooks for INSERT\u002FUPDATE\u002FDELETE events,\nsending HTTP requests from PostgreSQL triggers, handling Realtime\npostgres_changes as an event source, or building event-driven architectures.\nTrigger with phrases like \"supabase webhook\", \"database events\",\n\"pg_net trigger\", \"supabase LISTEN NOTIFY\", \"webhook signature verify\",\n\"supabase event-driven\", \"supabase_functions.http_request\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-webhooks-events\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: supabase-webhooks-events\ndescription: |\n  Implement Supabase database webhooks, pg_net async HTTP, LISTEN\u002FNOTIFY,\n  and Edge Function event handlers with signature verification.\n  Use when setting up database webhooks for INSERT\u002FUPDATE\u002FDELETE events,\n  sending HTTP requests from PostgreSQL triggers, handling Realtime\n  postgres_changes as an event source, or building event-driven architectures.\n  Trigger with phrases like \"supabase webhook\", \"database events\",\n  \"pg_net trigger\", \"supabase LISTEN NOTIFY\", \"webhook signature verify\",\n  \"supabase event-driven\", \"supabase_functions.http_request\".\nallowed-tools: Read, Write, Edit, Bash(supabase:*), Bash(curl:*), Bash(psql:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, supabase, webhooks, events, triggers, pg_net, realtime]\n---\n\n# Supabase Webhooks & Database Events\n\n## Overview\n\nSupabase offers four complementary event mechanisms: **Database Webhooks** (trigger-based HTTP calls via `pg_net`), **`supabase_functions.http_request()`** (call Edge Functions from triggers), **Postgres LISTEN\u002FNOTIFY** (lightweight pub\u002Fsub), and **Realtime `postgres_changes`** (client-side event subscriptions). This skill covers all four patterns with production-ready code including signature verification, idempotency, and retry handling.\n\n## Prerequisites\n\n- Supabase project (local or hosted) with `supabase` CLI installed\n- `pg_net` extension enabled: Dashboard > Database > Extensions > search \"pg_net\" > Enable\n- `@supabase\u002Fsupabase-js` v2+ installed for client-side patterns\n- Edge Functions deployed for webhook receiver patterns\n\n## Step 1 — Database Webhooks with `pg_net` and Trigger Functions\n\nDatabase webhooks fire HTTP requests when rows change. Under the hood, Supabase uses the `pg_net` extension to make async, non-blocking HTTP calls from within PostgreSQL.\n\n### Enable pg_net and Create the Trigger Function\n\n```sql\n-- Enable the pg_net extension (one-time)\nCREATE EXTENSION IF NOT EXISTS pg_net WITH SCHEMA extensions;\n\n-- Trigger function: POST to an Edge Function on every new order\nCREATE OR REPLACE FUNCTION public.notify_order_created()\nRETURNS trigger AS $$\nBEGIN\n  PERFORM net.http_post(\n    url    := 'https:\u002F\u002F\u003Cproject-ref>.supabase.co\u002Ffunctions\u002Fv1\u002Fon-order-created',\n    headers := jsonb_build_object(\n      'Content-Type', 'application\u002Fjson',\n      'Authorization', 'Bearer ' || current_setting('app.settings.service_role_key', true)\n    ),\n    body   := jsonb_build_object(\n      'table',  TG_TABLE_NAME,\n      'type',   TG_OP,\n      'record', row_to_json(NEW)::jsonb,\n      'old_record', CASE WHEN TG_OP = 'UPDATE' THEN row_to_json(OLD)::jsonb ELSE NULL END\n    )\n  );\n  RETURN NEW;\nEND;\n$$ LANGUAGE plpgsql SECURITY DEFINER;\n```\n\n### Attach Triggers for INSERT, UPDATE, DELETE\n\n```sql\n-- Fire on new rows\nCREATE TRIGGER on_order_created\n  AFTER INSERT ON public.orders\n  FOR EACH ROW EXECUTE FUNCTION public.notify_order_created();\n\n-- Fire on status changes only (conditional trigger)\nCREATE OR REPLACE FUNCTION public.notify_order_status_changed()\nRETURNS trigger AS $$\nBEGIN\n  IF OLD.status IS DISTINCT FROM NEW.status THEN\n    PERFORM net.http_post(\n      url    := 'https:\u002F\u002F\u003Cproject-ref>.supabase.co\u002Ffunctions\u002Fv1\u002Fon-status-change',\n      headers := '{\"Content-Type\": \"application\u002Fjson\"}'::jsonb,\n      body   := jsonb_build_object(\n        'order_id',   NEW.id,\n        'old_status', OLD.status,\n        'new_status', NEW.status,\n        'changed_at', now()\n      )\n    );\n  END IF;\n  RETURN NEW;\nEND;\n$$ LANGUAGE plpgsql SECURITY DEFINER;\n\nCREATE TRIGGER on_order_status_changed\n  AFTER UPDATE ON public.orders\n  FOR EACH ROW EXECUTE FUNCTION public.notify_order_status_changed();\n```\n\n### Using `supabase_functions.http_request()` (Built-in Helper)\n\nSupabase provides a built-in wrapper that simplifies calling Edge Functions from triggers without managing headers manually:\n\n```sql\n-- This is the function Supabase auto-creates for Dashboard-configured webhooks\n-- You can also call it directly in your own trigger functions\nCREATE TRIGGER on_profile_updated\n  AFTER UPDATE ON public.profiles\n  FOR EACH ROW\n  EXECUTE FUNCTION supabase_functions.http_request(\n    'https:\u002F\u002F\u003Cproject-ref>.supabase.co\u002Ffunctions\u002Fv1\u002Fon-profile-update',\n    'POST',\n    '{\"Content-Type\": \"application\u002Fjson\"}',\n    '{}',  -- params\n    '5000' -- timeout ms\n  );\n```\n\n### Inspect pg_net Responses\n\n```sql\n-- Check recent HTTP responses (retained for 6 hours)\nSELECT id, status_code, content, created\nFROM net._http_response\nORDER BY created DESC\nLIMIT 10;\n\n-- Find failed requests\nSELECT id, status_code, content\nFROM net._http_response\nWHERE status_code >= 400\nORDER BY created DESC;\n```\n\n## Step 2 — Edge Function Webhook Receivers with Signature Verification\n\n### Webhook Receiver with Signature Verification\n\n```typescript\n\u002F\u002F supabase\u002Ffunctions\u002Fon-order-created\u002Findex.ts\nimport { createClient } from \"https:\u002F\u002Fesm.sh\u002F@supabase\u002Fsupabase-js@2\";\nimport { serve } from \"https:\u002F\u002Fdeno.land\u002Fstd@0.177.0\u002Fhttp\u002Fserver.ts\";\n\ninterface WebhookPayload {\n  type: \"INSERT\" | \"UPDATE\" | \"DELETE\";\n  table: string;\n  record: Record\u003Cstring, unknown>;\n  old_record: Record\u003Cstring, unknown> | null;\n}\n\n\u002F\u002F Verify webhook signature to prevent spoofing\nasync function verifySignature(\n  body: string,\n  signature: string,\n  secret: string\n): Promise\u003Cboolean> {\n  const encoder = new TextEncoder();\n  const key = await crypto.subtle.importKey(\n    \"raw\",\n    encoder.encode(secret),\n    { name: \"HMAC\", hash: \"SHA-256\" },\n    false,\n    [\"sign\"]\n  );\n  const signed = await crypto.subtle.sign(\"HMAC\", key, encoder.encode(body));\n  const expected = Array.from(new Uint8Array(signed))\n    .map((b) => b.toString(16).padStart(2, \"0\"))\n    .join(\"\");\n  \u002F\u002F Constant-time comparison\n  if (signature.length !== expected.length) return false;\n  let mismatch = 0;\n  for (let i = 0; i \u003C signature.length; i++) {\n    mismatch |= signature.charCodeAt(i) ^ expected.charCodeAt(i);\n  }\n  return mismatch === 0;\n}\n\nserve(async (req) => {\n  \u002F\u002F Verify signature if webhook secret is configured\n  const webhookSecret = Deno.env.get(\"WEBHOOK_SECRET\");\n  const rawBody = await req.text();\n\n  if (webhookSecret) {\n    const signature = req.headers.get(\"x-webhook-signature\") ?? \"\";\n    const valid = await verifySignature(rawBody, signature, webhookSecret);\n    if (!valid) {\n      return new Response(JSON.stringify({ error: \"Invalid signature\" }), {\n        status: 401,\n      });\n    }\n  }\n\n  const payload: WebhookPayload = JSON.parse(rawBody);\n\n  const supabase = createClient(\n    Deno.env.get(\"SUPABASE_URL\")!,\n    Deno.env.get(\"SUPABASE_SERVICE_ROLE_KEY\")!,\n    { auth: { autoRefreshToken: false, persistSession: false } }\n  );\n\n  \u002F\u002F Route by event type\n  switch (payload.type) {\n    case \"INSERT\": {\n      console.log(`New ${payload.table} row:`, payload.record.id);\n\n      \u002F\u002F Example: log event, send notification, update related table\n      await supabase.from(\"audit_log\").insert({\n        table_name: payload.table,\n        action: \"INSERT\",\n        record_id: payload.record.id,\n        payload: payload.record,\n      });\n      break;\n    }\n    case \"UPDATE\": {\n      console.log(`Updated ${payload.table}:`, payload.record.id);\n      \u002F\u002F Compare old and new to detect specific field changes\n      if (payload.old_record?.status !== payload.record.status) {\n        await supabase.from(\"notifications\").insert({\n          user_id: payload.record.user_id,\n          message: `Status changed to ${payload.record.status}`,\n        });\n      }\n      break;\n    }\n    case \"DELETE\": {\n      console.log(`Deleted from ${payload.table}:`, payload.old_record?.id);\n      break;\n    }\n  }\n\n  return new Response(JSON.stringify({ received: true }), {\n    headers: { \"Content-Type\": \"application\u002Fjson\" },\n  });\n});\n```\n\n### Idempotent Event Processing\n\nWebhooks may be delivered more than once. Use an idempotency table to prevent duplicate processing:\n\n```typescript\n\u002F\u002F supabase\u002Ffunctions\u002Fidempotent-handler\u002Findex.ts\nimport { createClient } from \"https:\u002F\u002Fesm.sh\u002F@supabase\u002Fsupabase-js@2\";\n\nserve(async (req) => {\n  const payload = await req.json();\n  const eventId = `${payload.table}:${payload.type}:${payload.record.id}`;\n\n  const supabase = createClient(\n    Deno.env.get(\"SUPABASE_URL\")!,\n    Deno.env.get(\"SUPABASE_SERVICE_ROLE_KEY\")!\n  );\n\n  \u002F\u002F Check if already processed (upsert pattern)\n  const { data: existing } = await supabase\n    .from(\"processed_events\")\n    .select(\"id\")\n    .eq(\"event_id\", eventId)\n    .maybeSingle();\n\n  if (existing) {\n    return new Response(\n      JSON.stringify({ skipped: true, reason: \"already processed\" }),\n      { status: 200, headers: { \"Content-Type\": \"application\u002Fjson\" } }\n    );\n  }\n\n  \u002F\u002F --- Your business logic here ---\n  console.log(`Processing event: ${eventId}`);\n\n  \u002F\u002F Mark as processed (with TTL for cleanup)\n  await supabase.from(\"processed_events\").insert({\n    event_id: eventId,\n    processed_at: new Date().toISOString(),\n  });\n\n  return new Response(JSON.stringify({ processed: true }), {\n    status: 200,\n    headers: { \"Content-Type\": \"application\u002Fjson\" },\n  });\n});\n```\n\n```sql\n-- Idempotency table\nCREATE TABLE public.processed_events (\n  id         bigint GENERATED ALWAYS AS IDENTITY PRIMARY KEY,\n  event_id   text UNIQUE NOT NULL,\n  processed_at timestamptz DEFAULT now()\n);\n\n-- Auto-cleanup old records (run via pg_cron or scheduled function)\nDELETE FROM public.processed_events\nWHERE processed_at \u003C now() - interval '7 days';\n```\n\n## Step 3 — Postgres LISTEN\u002FNOTIFY and Realtime as Event Source\n\n### Postgres LISTEN\u002FNOTIFY for Lightweight Pub\u002FSub\n\nLISTEN\u002FNOTIFY is PostgreSQL's built-in pub\u002Fsub. It does not persist messages and is best for ephemeral notifications between database functions or connected clients:\n\n```sql\n-- Trigger function that emits a NOTIFY on row change\nCREATE OR REPLACE FUNCTION public.notify_changes()\nRETURNS trigger AS $$\nBEGIN\n  PERFORM pg_notify(\n    'db_changes',\n    json_build_object(\n      'table', TG_TABLE_NAME,\n      'op',    TG_OP,\n      'id',    COALESCE(NEW.id, OLD.id)\n    )::text\n  );\n  RETURN COALESCE(NEW, OLD);\nEND;\n$$ LANGUAGE plpgsql;\n\nCREATE TRIGGER orders_notify\n  AFTER INSERT OR UPDATE OR DELETE ON public.orders\n  FOR EACH ROW EXECUTE FUNCTION public.notify_changes();\n```\n\n```typescript\n\u002F\u002F Listen from a Node.js backend using pg driver\nimport { Client } from \"pg\";\n\nconst client = new Client({ connectionString: process.env.DATABASE_URL });\nawait client.connect();\n\nawait client.query(\"LISTEN db_changes\");\n\nclient.on(\"notification\", (msg) => {\n  const payload = JSON.parse(msg.payload!);\n  console.log(`${payload.op} on ${payload.table}: id=${payload.id}`);\n});\n```\n\n### Realtime `postgres_changes` as Client-Side Event Source\n\nSupabase Realtime lets frontend clients subscribe to database changes without polling. Enable Realtime on your table first (Dashboard > Database > Replication).\n\n```typescript\nimport { createClient } from \"@supabase\u002Fsupabase-js\";\n\nconst supabase = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_ANON_KEY!\n);\n\n\u002F\u002F Subscribe to all changes on the orders table\nconst channel = supabase\n  .channel(\"orders-events\")\n  .on(\n    \"postgres_changes\",\n    {\n      event: \"*\",           \u002F\u002F or 'INSERT' | 'UPDATE' | 'DELETE'\n      schema: \"public\",\n      table: \"orders\",\n      filter: \"status=eq.pending\",  \u002F\u002F optional: RLS-style filter\n    },\n    (payload) => {\n      console.log(\"Change type:\", payload.eventType);\n      console.log(\"New row:\", payload.new);\n      console.log(\"Old row:\", payload.old);\n\n      \u002F\u002F React to the change\n      switch (payload.eventType) {\n        case \"INSERT\":\n          showToast(`New order #${payload.new.id}`);\n          break;\n        case \"UPDATE\":\n          updateOrderInUI(payload.new);\n          break;\n        case \"DELETE\":\n          removeOrderFromUI(payload.old.id);\n          break;\n      }\n    }\n  )\n  .subscribe((status) => {\n    console.log(\"Subscription status:\", status);\n  });\n\n\u002F\u002F Cleanup when done\n\u002F\u002F await supabase.removeChannel(channel);\n```\n\n### Event-Driven Architecture: Combining Patterns\n\nUse database triggers for server-side workflows and Realtime for client-side UI updates:\n\n```\n┌──────────────┐     INSERT      ┌──────────────────┐\n│   Client     │ ──────────────► │  orders table     │\n│  (browser)   │                 └────────┬─────────┘\n│              │                          │\n│  Realtime ◄──┼──── postgres_changes ────┤\n│  (UI update) │                          │\n└──────────────┘                          │ AFTER INSERT trigger\n                                          ▼\n                                 ┌──────────────────┐\n                                 │  pg_net HTTP POST │\n                                 │  → Edge Function  │\n                                 └────────┬─────────┘\n                                          │\n                                          ▼\n                                 ┌──────────────────┐\n                                 │  Send email       │\n                                 │  Update inventory │\n                                 │  Log to audit     │\n                                 └──────────────────┘\n```\n\n## Output\n\nAfter implementing these patterns you will have:\n\n- Database trigger functions calling Edge Functions via `pg_net` on row changes\n- Conditional triggers that fire only when specific columns change\n- Edge Function webhook receivers with HMAC signature verification\n- Idempotent event processing preventing duplicate side effects\n- LISTEN\u002FNOTIFY channels for lightweight inter-service communication\n- Realtime subscriptions for live client-side UI updates\n- An event-driven architecture combining server and client patterns\n\n## Error Handling\n\n| Error | Cause | Fix |\n|-------|-------|-----|\n| `pg_net` returns 404 | Edge Function not deployed or wrong URL | Run `supabase functions deploy \u003Cname>` and verify the URL matches |\n| Webhook not firing | Trigger not attached or table not in publication | Check `SELECT * FROM pg_trigger WHERE tgrelid = 'orders'::regclass;` |\n| Duplicate events processed | No idempotency layer | Add `processed_events` table with unique `event_id` constraint |\n| Realtime not receiving | Table not added to Realtime publication | Dashboard > Database > Replication > enable the table |\n| `net._http_response` shows 401 | Invalid or missing auth header | Verify `service_role_key` is set in `app.settings` or vault |\n| NOTIFY payload truncated | Payload exceeds 8000 bytes | Send only IDs in NOTIFY, fetch full record in the listener |\n| Auth hook errors | Function raises exception | Check Dashboard > Logs > Auth; ensure function returns valid JSONB |\n| Trigger silently fails | `SECURITY DEFINER` without `search_path` | Add `SET search_path = public, extensions;` to function |\n\n## Examples\n\nSee [examples.md](references\u002Fexamples.md) for local webhook testing with ngrok and curl.\n\nSee [signature-verification.md](references\u002Fsignature-verification.md) for Node.js HMAC signature verification.\n\nSee [event-handler-pattern.md](references\u002Fevent-handler-pattern.md) for a typed event dispatcher pattern.\n\n## Resources\n\n- [Database Webhooks](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fwebhooks) — configure via Dashboard or SQL\n- [pg_net Extension](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fextensions\u002Fpg_net) — async HTTP from PostgreSQL\n- [Edge Functions](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions) — Deno-based serverless handlers\n- [Realtime postgres_changes](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Frealtime\u002Fpostgres-changes) — client-side subscriptions\n- [Auth Hooks](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Fauth-hooks) — custom JWT claims and login events\n- [supabase-js Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Fsubscribe) — `channel().on()` API\n\n## Next Steps\n\nFor performance optimization of triggers and queries, see `supabase-performance-tuning`. For production hardening including RLS policies on webhook-accessed tables, see `supabase-security-basics`.\n","# Supabase Webhooks & Database Events\n\n## Overview\n\nSupabase offers four complementary event mechanisms: **Database Webhooks** (trigger-based HTTP calls via `pg_net`), **`supabase_functions.http_request()`** (call Edge Functions from triggers), **Postgres LISTEN\u002FNOTIFY** (lightweight pub\u002Fsub), and **Realtime `postgres_changes`** (client-side event subscriptions). This skill covers all four patterns with production-ready code including signature verification, idempotency, and retry handling.\n\n## Prerequisites\n\n- Supabase project (local or hosted) with `supabase` CLI installed\n- `pg_net` extension enabled: Dashboard > Database > Extensions > search \"pg_net\" > Enable\n- `@supabase\u002Fsupabase-js` v2+ installed for client-side patterns\n- Edge Functions deployed for webhook receiver patterns\n\n## Step 1 — Database Webhooks with `pg_net` and Trigger Functions\n\nDatabase webhooks fire HTTP requests when rows change. Under the hood, Supabase uses the `pg_net` extension to make async, non-blocking HTTP calls from within PostgreSQL.\n\n### Enable pg_net and Create the Trigger Function\n\n```sql\n-- Enable the pg_net extension (one-time)\nCREATE EXTENSION IF NOT EXISTS pg_net WITH SCHEMA extensions;\n\n-- Trigger function: POST to an Edge Function on every new order\nCREATE OR REPLACE FUNCTION public.notify_order_created()\nRETURNS trigger AS $$\nBEGIN\n  PERFORM net.http_post(\n    url    := 'https:\u002F\u002F\u003Cproject-ref>.supabase.co\u002Ffunctions\u002Fv1\u002Fon-order-created',\n    headers := jsonb_build_object(\n      'Content-Type', 'application\u002Fjson',\n      'Authorization', 'Bearer ' || current_setting('app.settings.service_role_key', true)\n    ),\n    body   := jsonb_build_object(\n      'table',  TG_TABLE_NAME,\n      'type',   TG_OP,\n      'record', row_to_json(NEW)::jsonb,\n      'old_record', CASE WHEN TG_OP = 'UPDATE' THEN row_to_json(OLD)::jsonb ELSE NULL END\n    )\n  );\n  RETURN NEW;\nEND;\n$$ LANGUAGE plpgsql SECURITY DEFINER;\n```\n\n### Attach Triggers for INSERT, UPDATE, DELETE\n\n```sql\n-- Fire on new rows\nCREATE TRIGGER on_order_created\n  AFTER INSERT ON public.orders\n  FOR EACH ROW EXECUTE FUNCTION public.notify_order_created();\n\n-- Fire on status changes only (conditional trigger)\nCREATE OR REPLACE FUNCTION public.notify_order_status_changed()\nRETURNS trigger AS $$\nBEGIN\n  IF OLD.status IS DISTINCT FROM NEW.status THEN\n    PERFORM net.http_post(\n      url    := 'https:\u002F\u002F\u003Cproject-ref>.supabase.co\u002Ffunctions\u002Fv1\u002Fon-status-change',\n      headers := '{\"Content-Type\": \"application\u002Fjson\"}'::jsonb,\n      body   := jsonb_build_object(\n        'order_id',   NEW.id,\n        'old_status', OLD.status,\n        'new_status', NEW.status,\n        'changed_at', now()\n      )\n    );\n  END IF;\n  RETURN NEW;\nEND;\n$$ LANGUAGE plpgsql SECURITY DEFINER;\n\nCREATE TRIGGER on_order_status_changed\n  AFTER UPDATE ON public.orders\n  FOR EACH ROW EXECUTE FUNCTION public.notify_order_status_changed();\n```\n\n### Using `supabase_functions.http_request()` (Built-in Helper)\n\nSupabase provides a built-in wrapper that simplifies calling Edge Functions from triggers without managing headers manually:\n\n```sql\n-- This is the function Supabase auto-creates for Dashboard-configured webhooks\n-- You can also call it directly in your own trigger functions\nCREATE TRIGGER on_profile_updated\n  AFTER UPDATE ON public.profiles\n  FOR EACH ROW\n  EXECUTE FUNCTION supabase_functions.http_request(\n    'https:\u002F\u002F\u003Cproject-ref>.supabase.co\u002Ffunctions\u002Fv1\u002Fon-profile-update',\n    'POST',\n    '{\"Content-Type\": \"application\u002Fjson\"}',\n    '{}',  -- params\n    '5000' -- timeout ms\n  );\n```\n\n### Inspect pg_net Responses\n\n```sql\n-- Check recent HTTP responses (retained for 6 hours)\nSELECT id, status_code, content, created\nFROM net._http_response\nORDER BY created DESC\nLIMIT 10;\n\n-- Find failed requests\nSELECT id, status_code, content\nFROM net._http_response\nWHERE status_code >= 400\nORDER BY created DESC;\n```\n\n## Step 2 — Edge Function Webhook Receivers with Signature Verification\n\n### Webhook Receiver with Signature Verification\n\n```typescript\n\u002F\u002F supabase\u002Ffunctions\u002Fon-order-created\u002Findex.ts\nimport { createClient } from \"https:\u002F\u002Fesm.sh\u002F@supabase\u002Fsupabase-js@2\";\nimport { serve } from \"https:\u002F\u002Fdeno.land\u002Fstd@0.177.0\u002Fhttp\u002Fserver.ts\";\n\ninterface WebhookPayload {\n  type: \"INSERT\" | \"UPDATE\" | \"DELETE\";\n  table: string;\n  record: Record\u003Cstring, unknown>;\n  old_record: Record\u003Cstring, unknown> | null;\n}\n\n\u002F\u002F Verify webhook signature to prevent spoofing\nasync function verifySignature(\n  body: string,\n  signature: string,\n  secret: string\n): Promise\u003Cboolean> {\n  const encoder = new TextEncoder();\n  const key = await crypto.subtle.importKey(\n    \"raw\",\n    encoder.encode(secret),\n    { name: \"HMAC\", hash: \"SHA-256\" },\n    false,\n    [\"sign\"]\n  );\n  const signed = await crypto.subtle.sign(\"HMAC\", key, encoder.encode(body));\n  const expected = Array.from(new Uint8Array(signed))\n    .map((b) => b.toString(16).padStart(2, \"0\"))\n    .join(\"\");\n  \u002F\u002F Constant-time comparison\n  if (signature.length !== expected.length) return false;\n  let mismatch = 0;\n  for (let i = 0; i \u003C signature.length; i++) {\n    mismatch |= signature.charCodeAt(i) ^ expected.charCodeAt(i);\n  }\n  return mismatch === 0;\n}\n\nserve(async (req) => {\n  \u002F\u002F Verify signature if webhook secret is configured\n  const webhookSecret = Deno.env.get(\"WEBHOOK_SECRET\");\n  const rawBody = await req.text();\n\n  if (webhookSecret) {\n    const signature = req.headers.get(\"x-webhook-signature\") ?? \"\";\n    const valid = await verifySignature(rawBody, signature, webhookSecret);\n    if (!valid) {\n      return new Response(JSON.stringify({ error: \"Invalid signature\" }), {\n        status: 401,\n      });\n    }\n  }\n\n  const payload: WebhookPayload = JSON.parse(rawBody);\n\n  const supabase = createClient(\n    Deno.env.get(\"SUPABASE_URL\")!,\n    Deno.env.get(\"SUPABASE_SERVICE_ROLE_KEY\")!,\n    { auth: { autoRefreshToken: false, persistSession: false } }\n  );\n\n  \u002F\u002F Route by event type\n  switch (payload.type) {\n    case \"INSERT\": {\n      console.log(`New ${payload.table} row:`, payload.record.id);\n\n      \u002F\u002F Example: log event, send notification, update related table\n      await supabase.from(\"audit_log\").insert({\n        table_name: payload.table,\n        action: \"INSERT\",\n        record_id: payload.record.id,\n        payload: payload.record,\n      });\n      break;\n    }\n    case \"UPDATE\": {\n      console.log(`Updated ${payload.table}:`, payload.record.id);\n      \u002F\u002F Compare old and new to detect specific field changes\n      if (payload.old_record?.status !== payload.record.status) {\n        await supabase.from(\"notifications\").insert({\n          user_id: payload.record.user_id,\n          message: `Status changed to ${payload.record.status}`,\n        });\n      }\n      break;\n    }\n    case \"DELETE\": {\n      console.log(`Deleted from ${payload.table}:`, payload.old_record?.id);\n      break;\n    }\n  }\n\n  return new Response(JSON.stringify({ received: true }), {\n    headers: { \"Content-Type\": \"application\u002Fjson\" },\n  });\n});\n```\n\n### Idempotent Event Processing\n\nWebhooks may be delivered more than once. Use an idempotency table to prevent duplicate processing:\n\n```typescript\n\u002F\u002F supabase\u002Ffunctions\u002Fidempotent-handler\u002Findex.ts\nimport { createClient } from \"https:\u002F\u002Fesm.sh\u002F@supabase\u002Fsupabase-js@2\";\n\nserve(async (req) => {\n  const payload = await req.json();\n  const eventId = `${payload.table}:${payload.type}:${payload.record.id}`;\n\n  const supabase = createClient(\n    Deno.env.get(\"SUPABASE_URL\")!,\n    Deno.env.get(\"SUPABASE_SERVICE_ROLE_KEY\")!\n  );\n\n  \u002F\u002F Check if already processed (upsert pattern)\n  const { data: existing } = await supabase\n    .from(\"processed_events\")\n    .select(\"id\")\n    .eq(\"event_id\", eventId)\n    .maybeSingle();\n\n  if (existing) {\n    return new Response(\n      JSON.stringify({ skipped: true, reason: \"already processed\" }),\n      { status: 200, headers: { \"Content-Type\": \"application\u002Fjson\" } }\n    );\n  }\n\n  \u002F\u002F --- Your business logic here ---\n  console.log(`Processing event: ${eventId}`);\n\n  \u002F\u002F Mark as processed (with TTL for cleanup)\n  await supabase.from(\"processed_events\").insert({\n    event_id: eventId,\n    processed_at: new Date().toISOString(),\n  });\n\n  return new Response(JSON.stringify({ processed: true }), {\n    status: 200,\n    headers: { \"Content-Type\": \"application\u002Fjson\" },\n  });\n});\n```\n\n```sql\n-- Idempotency table\nCREATE TABLE public.processed_events (\n  id         bigint GENERATED ALWAYS AS IDENTITY PRIMARY KEY,\n  event_id   text UNIQUE NOT NULL,\n  processed_at timestamptz DEFAULT now()\n);\n\n-- Auto-cleanup old records (run via pg_cron or scheduled function)\nDELETE FROM public.processed_events\nWHERE processed_at \u003C now() - interval '7 days';\n```\n\n## Step 3 — Postgres LISTEN\u002FNOTIFY and Realtime as Event Source\n\n### Postgres LISTEN\u002FNOTIFY for Lightweight Pub\u002FSub\n\nLISTEN\u002FNOTIFY is PostgreSQL's built-in pub\u002Fsub. It does not persist messages and is best for ephemeral notifications between database functions or connected clients:\n\n```sql\n-- Trigger function that emits a NOTIFY on row change\nCREATE OR REPLACE FUNCTION public.notify_changes()\nRETURNS trigger AS $$\nBEGIN\n  PERFORM pg_notify(\n    'db_changes',\n    json_build_object(\n      'table', TG_TABLE_NAME,\n      'op',    TG_OP,\n      'id',    COALESCE(NEW.id, OLD.id)\n    )::text\n  );\n  RETURN COALESCE(NEW, OLD);\nEND;\n$$ LANGUAGE plpgsql;\n\nCREATE TRIGGER orders_notify\n  AFTER INSERT OR UPDATE OR DELETE ON public.orders\n  FOR EACH ROW EXECUTE FUNCTION public.notify_changes();\n```\n\n```typescript\n\u002F\u002F Listen from a Node.js backend using pg driver\nimport { Client } from \"pg\";\n\nconst client = new Client({ connectionString: process.env.DATABASE_URL });\nawait client.connect();\n\nawait client.query(\"LISTEN db_changes\");\n\nclient.on(\"notification\", (msg) => {\n  const payload = JSON.parse(msg.payload!);\n  console.log(`${payload.op} on ${payload.table}: id=${payload.id}`);\n});\n```\n\n### Realtime `postgres_changes` as Client-Side Event Source\n\nSupabase Realtime lets frontend clients subscribe to database changes without polling. Enable Realtime on your table first (Dashboard > Database > Replication).\n\n```typescript\nimport { createClient } from \"@supabase\u002Fsupabase-js\";\n\nconst supabase = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_ANON_KEY!\n);\n\n\u002F\u002F Subscribe to all changes on the orders table\nconst channel = supabase\n  .channel(\"orders-events\")\n  .on(\n    \"postgres_changes\",\n    {\n      event: \"*\",           \u002F\u002F or 'INSERT' | 'UPDATE' | 'DELETE'\n      schema: \"public\",\n      table: \"orders\",\n      filter: \"status=eq.pending\",  \u002F\u002F optional: RLS-style filter\n    },\n    (payload) => {\n      console.log(\"Change type:\", payload.eventType);\n      console.log(\"New row:\", payload.new);\n      console.log(\"Old row:\", payload.old);\n\n      \u002F\u002F React to the change\n      switch (payload.eventType) {\n        case \"INSERT\":\n          showToast(`New order #${payload.new.id}`);\n          break;\n        case \"UPDATE\":\n          updateOrderInUI(payload.new);\n          break;\n        case \"DELETE\":\n          removeOrderFromUI(payload.old.id);\n          break;\n      }\n    }\n  )\n  .subscribe((status) => {\n    console.log(\"Subscription status:\", status);\n  });\n\n\u002F\u002F Cleanup when done\n\u002F\u002F await supabase.removeChannel(channel);\n```\n\n### Event-Driven Architecture: Combining Patterns\n\nUse database triggers for server-side workflows and Realtime for client-side UI updates:\n\n```\n┌──────────────┐     INSERT      ┌──────────────────┐\n│   Client     │ ──────────────► │  orders table     │\n│  (browser)   │                 └────────┬─────────┘\n│              │                          │\n│  Realtime ◄──┼──── postgres_changes ────┤\n│  (UI update) │                          │\n└──────────────┘                          │ AFTER INSERT trigger\n                                          ▼\n                                 ┌──────────────────┐\n                                 │  pg_net HTTP POST │\n                                 │  → Edge Function  │\n                                 └────────┬─────────┘\n                                          │\n                                          ▼\n                                 ┌──────────────────┐\n                                 │  Send email       │\n                                 │  Update inventory │\n                                 │  Log to audit     │\n                                 └──────────────────┘\n```\n\n## Output\n\nAfter implementing these patterns you will have:\n\n- Database trigger functions calling Edge Functions via `pg_net` on row changes\n- Conditional triggers that fire only when specific columns change\n- Edge Function webhook receivers with HMAC signature verification\n- Idempotent event processing preventing duplicate side effects\n- LISTEN\u002FNOTIFY channels for lightweight inter-service communication\n- Realtime subscriptions for live client-side UI updates\n- An event-driven architecture combining server and client patterns\n\n## Error Handling\n\n| Error | Cause | Fix |\n|-------|-------|-----|\n| `pg_net` returns 404 | Edge Function not deployed or wrong URL | Run `supabase functions deploy \u003Cname>` and verify the URL matches |\n| Webhook not firing | Trigger not attached or table not in publication | Check `SELECT * FROM pg_trigger WHERE tgrelid = 'orders'::regclass;` |\n| Duplicate events processed | No idempotency layer | Add `processed_events` table with unique `event_id` constraint |\n| Realtime not receiving | Table not added to Realtime publication | Dashboard > Database > Replication > enable the table |\n| `net._http_response` shows 401 | Invalid or missing auth header | Verify `service_role_key` is set in `app.settings` or vault |\n| NOTIFY payload truncated | Payload exceeds 8000 bytes | Send only IDs in NOTIFY, fetch full record in the listener |\n| Auth hook errors | Function raises exception | Check Dashboard > Logs > Auth; ensure function returns valid JSONB |\n| Trigger silently fails | `SECURITY DEFINER` without `search_path` | Add `SET search_path = public, extensions;` to function |\n\n## Examples\n\nSee [examples.md](references\u002Fexamples.md) for local webhook testing with ngrok and curl.\n\nSee [signature-verification.md](references\u002Fsignature-verification.md) for Node.js HMAC signature verification.\n\nSee [event-handler-pattern.md](references\u002Fevent-handler-pattern.md) for a typed event dispatcher pattern.\n\n## Resources\n\n- [Database Webhooks](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fwebhooks) — configure via Dashboard or SQL\n- [pg_net Extension](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fextensions\u002Fpg_net) — async HTTP from PostgreSQL\n- [Edge Functions](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions) — Deno-based serverless handlers\n- [Realtime postgres_changes](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Frealtime\u002Fpostgres-changes) — client-side subscriptions\n- [Auth Hooks](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Fauth-hooks) — custom JWT claims and login events\n- [supabase-js Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Fsubscribe) — `channel().on()` API\n\n## Next Steps\n\nFor performance optimization of triggers and queries, see `supabase-performance-tuning`. For production hardening including RLS policies on webhook-accessed tables, see `supabase-security-basics`.\n",{"name":5,"tags":24,"author":32,"license":15,"version":33,"description":34,"allowed-tools":35,"compatible-with":36},[25,26,27,28,29,30,31],"saas","supabase","webhooks","events","triggers","pg_net","realtime","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Implement Supabase database webhooks, pg_net async HTTP, LISTEN\u002FNOTIFY,\nand Edge Function event handlers with signature verification.\nUse when setting up database webhooks for INSERT\u002FUPDATE\u002FDELETE events,\nsending HTTP requests from PostgreSQL triggers, handling Realtime\npostgres_changes as an event source, or building event-driven architectures.\nTrigger with phrases like \"supabase webhook\", \"database events\",\n\"pg_net trigger\", \"supabase LISTEN NOTIFY\", \"webhook signature verify\",\n\"supabase event-driven\", \"supabase_functions.http_request\".\n","Read, Write, Edit, Bash(supabase:*), Bash(curl:*), Bash(psql:*), Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--supabase-pack--supabase-webhooks-events",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill supabase-webhooks-events",{"tool":52,"command":53},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill supabase-webhooks-events",{"tool":55,"command":56},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill supabase-webhooks-events","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-webhooks-events\u002FSKILL.md",true,[],[61,68,75,82,89,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]