Supabase

Your receptionist can save details from a call to a Supabase table and look up a caller by phone number, through Supabase’s REST API. The setup below uses your project’s public key with row-level security, so the receptionist can only do what you allow.

Before you start

In the Supabase dashboard, open Project Settings → API Keys and copy the publishable key, or the legacy anon key. Your project URL is https://PROJECT_REF.supabase.co.

Prepare the database

Run this in the SQL Editor. It creates a table your receptionist can only insert into, and a function that returns one customer by exact phone number. The function assumes an existing customers table with name, plan, notes, and phone columns, so adjust the names to your schema.

Callers can’t use the function to list customers: it returns nothing unless the exact phone number is known.

create table callback_requests (
  id bigint generated always as identity primary key,
  created_at timestamptz not null default now(),
  caller_name text not null,
  phone text not null,
  reason text not null
);
alter table callback_requests enable row level security;
create policy "Receptionist can add callback requests"
  on callback_requests for insert to anon
  with check (true);
create function find_customer_by_phone(phone text)
returns table (name text, plan text, notes text)
language sql stable security definer set search_path = public
as $$
  select c.name, c.plan, c.notes from customers c where c.phone = find_customer_by_phone.phone limit 1;
$$;
revoke execute on function find_customer_by_phone from public;
grant execute on function find_customer_by_phone to anon;

Create the tools

For both tools, go to Integrations, select Add integration, choose Webhook Tool, and add these request headers:

Save a callback request

Look up a customer

Select Enable on each tool, then test your receptionist with a callback request. The row appears in Table Editor.

Troubleshooting