Integration Guide

This guide will help you set up a webhook integration between Supabase and HookFlo, allowing you to receive real-time alerts when database changes, authentication events, and other activities occur in your Supabase project.

Supabase uses a combination of database triggers and Postgres functions to deliver webhook events. HookFlo seamlessly integrates with both Supabase’s built-in webhooks and custom webhook implementations.

Prerequisites

A HookFlo account with an active project
A Supabase project with admin access
Basic understanding of Supabase database and functions

Integration Overview

The integration process follows these key steps:

Set up a webhook in HookFlo
Configure notification channels (email/Slack)
Connect Supabase to HookFlo
Test the integration

Setting Up Your HookFlo Webhook

After logging into HookFlo, follow these steps to create and configure your Supabase webhook:

Create a Webhook

Setting Up Your Webhook Endpoint

Setup Notification Channel

Configure Email Notifications

Configure Slack Notifications

Connect your Webhook with application

Configure Application

Configuring Supabase

Now that your HookFlo webhook is set up, you need to configure Supabase to send events to it:

Setup Supabase Webhook

Access Supabase Webhooks

Create a Database Webhook

Configure Webhook Details

Enable HTTP Extension (If Needed)

Configure Http Extension

For webhooks to function correctly, Supabase needs the HTTP extension enabled. Most projects created after December 2022 have this extension enabled by default.

To check or enable it:

Go to the SQL Editor in your Supabase dashboard
Run the following SQL command:

create extension if not exists http with schema extensions;

Click Run to execute the command

Select Tables to Monitor

Choose Database Tables

Testing Your Integration

To ensure your integration is working properly:

Generate Test Events

Run Test Events

Verify in HookFlo

Validate Alert Delivery

Advanced Configuration

Using SQL for Custom Webhook Triggers

For more control over your webhooks, you can use SQL to create custom triggers:

-- Create a function that will trigger the webhook
create or replace function public.handle_webhook_event()
returns trigger as $$
declare
  webhook_url text := 'https://api.hookflo.dev/webhook/supabase/[your-webhook-id]';
begin
  perform net.http_post(
    webhook_url,
    json_build_object(
      'table', TG_TABLE_NAME,
      'schema', TG_TABLE_SCHEMA,
      'event', TG_OP,
      'record', case when TG_OP = 'DELETE' then old else new end,
      'old_record', case when TG_OP = 'UPDATE' then old else null end
    )::text,
    'application/json',
    array[
      ('x-webhook-id', '[Your webhook ID from HookFlo]'),
      ('x-webhook-token', '[Your webhook token from HookFlo]')
    ]
  );
  return new;
end;
$$ language plpgsql security definer;

-- Create a trigger on your table
create trigger on_users_changed
  after insert or update or delete on public.users
  for each row execute procedure public.handle_webhook_event();

This approach gives you fine-grained control over what data is sent and when.

Customizing Notification Templates

HookFlo allows you to fully customize your notification templates:

Email Template Example:

Subject: [{{event}}] New activity on {{table}}

Hello,

The following {{event}} event occurred on the {{table}} table:

Record ID: {{record.id}}
Time: {{timestamp}}

Details:
{{#each record}}
- {{@key}}: {{this}}
{{/each}}

Best regards,
The HookFlo Team

Slack Template Example:

*{{event}} Event on {{table}}*

Record ID: {{record.id}}
Time: {{timestamp}}

*Details:*
{{#each record}}
• {{@key}}: {{this}}
{{/each}}

You can use any data from the webhook payload in your templates.

Webhook Payload Structure

Here’s an example of what the webhook payload looks like for different events:

Database Event Payload

{
  "table": "users",
  "schema": "public",
  "event": "INSERT",
  "record": {
    "id": "d9be2f69-5d13-4ac3-8f77-1193e9b1bfe3",
    "email": "user@example.com",
    "created_at": "2023-04-01T12:00:00Z"
  },
  "old_record": null
}

Authentication Event Payload

{
  "event": "SIGNED_UP",
  "instance": "your-project-ref",
  "timestamp": "2023-04-01T12:00:00Z",
  "user": {
    "id": "d9be2f69-5d13-4ac3-8f77-1193e9b1bfe3",
    "email": "user@example.com"
  }
}

Troubleshooting

Webhook Not Firing

Events Received but No Notifications

Performance Considerations

Example: Monitoring New User Signups

Here’s a complete example of setting up HookFlo to alert your team when new users sign up:

Create the Webhook in HookFlo

Follow the steps above to create a Supabase webhook in HookFlo and configure your notification channels.

Configure the Database Webhook in Supabase

In your Supabase dashboard, go to Database > Webhooks
Create a new webhook named “user-signups”
Select the auth.users table (or your custom users table)
Choose the INSERT event type to trigger on new user creations
Add your HookFlo webhook URL and headers (x-webhook-id and x-webhook-token)
Save the webhook

Security Considerations

When setting up webhook integrations between Supabase and HookFlo, keep these security best practices in mind:

Protect your webhook credentials: Keep your x-webhook-id and x-webhook-token secure
Use row-level security: Limit what data can be included in webhook payloads
Implement data minimization: Only send the fields you actually need
Regular audits: Remove webhooks from tables that no longer need monitoring
Use HTTPS only: Ensure all webhook communications use secure protocols

Congratulations! 🎉

You’ve successfully set up real-time event tracking and alerting between Supabase and HookFlo in just few minutes. Your team can now receive immediate notifications about important database and authentication events, helping you respond quickly to critical situations.

Need more help? Contact our support team or join our Discord forum or DM me directly on X.

On this page

Integration Guide
Prerequisites
Integration Overview
Setting Up Your HookFlo Webhook
Configuring Supabase
Testing Your Integration
Advanced Configuration
Webhook Payload Structure
Database Event Payload
Authentication Event Payload
Troubleshooting
Example: Monitoring New User Signups
Security Considerations
Congratulations! 🎉

Integration Guide

Prerequisites

A HookFlo account with an active project
A Supabase project with admin access
Basic understanding of Supabase database and functions

Integration Overview

The integration process follows these key steps:

Set up a webhook in HookFlo
Configure notification channels (email/Slack)
Connect Supabase to HookFlo
Test the integration

Setting Up Your HookFlo Webhook

After logging into HookFlo, follow these steps to create and configure your Supabase webhook:

Create a Webhook

Setting Up Your Webhook Endpoint

Setup Notification Channel

Configure Email Notifications

Configure Slack Notifications

Connect your Webhook with application

Configure Application

Configuring Supabase

Now that your HookFlo webhook is set up, you need to configure Supabase to send events to it:

Setup Supabase Webhook

Access Supabase Webhooks

Create a Database Webhook

Configure Webhook Details

Enable HTTP Extension (If Needed)

Configure Http Extension

For webhooks to function correctly, Supabase needs the HTTP extension enabled. Most projects created after December 2022 have this extension enabled by default.

To check or enable it:

Go to the SQL Editor in your Supabase dashboard
Run the following SQL command:

create extension if not exists http with schema extensions;

Click Run to execute the command

Select Tables to Monitor

Choose Database Tables

Testing Your Integration

To ensure your integration is working properly:

Generate Test Events

Run Test Events

Verify in HookFlo

Validate Alert Delivery

Advanced Configuration

Using SQL for Custom Webhook Triggers

For more control over your webhooks, you can use SQL to create custom triggers:

-- Create a function that will trigger the webhook
create or replace function public.handle_webhook_event()
returns trigger as $$
declare
  webhook_url text := 'https://api.hookflo.dev/webhook/supabase/[your-webhook-id]';
begin
  perform net.http_post(
    webhook_url,
    json_build_object(
      'table', TG_TABLE_NAME,
      'schema', TG_TABLE_SCHEMA,
      'event', TG_OP,
      'record', case when TG_OP = 'DELETE' then old else new end,
      'old_record', case when TG_OP = 'UPDATE' then old else null end
    )::text,
    'application/json',
    array[
      ('x-webhook-id', '[Your webhook ID from HookFlo]'),
      ('x-webhook-token', '[Your webhook token from HookFlo]')
    ]
  );
  return new;
end;
$$ language plpgsql security definer;

-- Create a trigger on your table
create trigger on_users_changed
  after insert or update or delete on public.users
  for each row execute procedure public.handle_webhook_event();

This approach gives you fine-grained control over what data is sent and when.

Customizing Notification Templates

HookFlo allows you to fully customize your notification templates:

Email Template Example:

Subject: [{{event}}] New activity on {{table}}

Hello,

The following {{event}} event occurred on the {{table}} table:

Record ID: {{record.id}}
Time: {{timestamp}}

Details:
{{#each record}}
- {{@key}}: {{this}}
{{/each}}

Best regards,
The HookFlo Team

Slack Template Example:

*{{event}} Event on {{table}}*

Record ID: {{record.id}}
Time: {{timestamp}}

*Details:*
{{#each record}}
• {{@key}}: {{this}}
{{/each}}

You can use any data from the webhook payload in your templates.

Webhook Payload Structure

Here’s an example of what the webhook payload looks like for different events:

Database Event Payload

{
  "table": "users",
  "schema": "public",
  "event": "INSERT",
  "record": {
    "id": "d9be2f69-5d13-4ac3-8f77-1193e9b1bfe3",
    "email": "user@example.com",
    "created_at": "2023-04-01T12:00:00Z"
  },
  "old_record": null
}

Authentication Event Payload

{
  "event": "SIGNED_UP",
  "instance": "your-project-ref",
  "timestamp": "2023-04-01T12:00:00Z",
  "user": {
    "id": "d9be2f69-5d13-4ac3-8f77-1193e9b1bfe3",
    "email": "user@example.com"
  }
}

Troubleshooting

Webhook Not Firing

Events Received but No Notifications

Performance Considerations

Example: Monitoring New User Signups

Here’s a complete example of setting up HookFlo to alert your team when new users sign up:

Create the Webhook in HookFlo

Follow the steps above to create a Supabase webhook in HookFlo and configure your notification channels.

Configure the Database Webhook in Supabase

In your Supabase dashboard, go to Database > Webhooks
Create a new webhook named “user-signups”
Select the auth.users table (or your custom users table)
Choose the INSERT event type to trigger on new user creations
Add your HookFlo webhook URL and headers (x-webhook-id and x-webhook-token)
Save the webhook

Security Considerations

When setting up webhook integrations between Supabase and HookFlo, keep these security best practices in mind:

Protect your webhook credentials: Keep your x-webhook-id and x-webhook-token secure
Use row-level security: Limit what data can be included in webhook payloads
Implement data minimization: Only send the fields you actually need
Regular audits: Remove webhooks from tables that no longer need monitoring
Use HTTPS only: Ensure all webhook communications use secure protocols

Congratulations! 🎉

Need more help? Contact our support team or join our Discord forum or DM me directly on X.

On this page

Integration Guide
Prerequisites
Integration Overview
Setting Up Your HookFlo Webhook
Configuring Supabase
Testing Your Integration
Advanced Configuration
Webhook Payload Structure
Database Event Payload
Authentication Event Payload
Troubleshooting
Example: Monitoring New User Signups
Security Considerations
Congratulations! 🎉

Supabase

Integration Guide

Prerequisites

Integration Overview

Setting Up Your HookFlo Webhook

Configuring Supabase

Testing Your Integration

Advanced Configuration

Email Template Example:

Slack Template Example:

Webhook Payload Structure

Database Event Payload

Authentication Event Payload

Troubleshooting

Example: Monitoring New User Signups

Security Considerations

Congratulations! 🎉

Get Started

Platforms

Notification Channels

Security

Supabase

Integration Guide

Prerequisites

Integration Overview

Setting Up Your HookFlo Webhook

Configuring Supabase

Testing Your Integration

Advanced Configuration

Email Template Example:

Slack Template Example:

Webhook Payload Structure

Database Event Payload

Authentication Event Payload

Troubleshooting

Example: Monitoring New User Signups

Security Considerations

Congratulations! 🎉

​Integration Guide

​Prerequisites

​Integration Overview

​Setting Up Your HookFlo Webhook

​Configuring Supabase

​Testing Your Integration

​Advanced Configuration

​Webhook Payload Structure

​Database Event Payload

​Authentication Event Payload

​Troubleshooting

​Example: Monitoring New User Signups

​Security Considerations

​Congratulations! 🎉

Get Started

Platforms

Notification Channels

Security

​Integration Guide

​Prerequisites

​Integration Overview

​Setting Up Your HookFlo Webhook

​Configuring Supabase

​Testing Your Integration

​Advanced Configuration

​Webhook Payload Structure

​Database Event Payload

​Authentication Event Payload

​Troubleshooting

​Example: Monitoring New User Signups

​Security Considerations

​Congratulations! 🎉

Integration Guide

Prerequisites

Integration Overview

Setting Up Your HookFlo Webhook

Configuring Supabase

Testing Your Integration

Advanced Configuration

Webhook Payload Structure

Database Event Payload

Authentication Event Payload

Troubleshooting

Example: Monitoring New User Signups

Security Considerations

Congratulations! 🎉

Integration Guide

Prerequisites

Integration Overview

Setting Up Your HookFlo Webhook

Configuring Supabase

Testing Your Integration

Advanced Configuration

Webhook Payload Structure

Database Event Payload

Authentication Event Payload

Troubleshooting

Example: Monitoring New User Signups

Security Considerations

Congratulations! 🎉