Post-deploy setup
Required configuration after deploying wakit on Supabase.
After the initial deploy, you must configure vault secrets that the database triggers need to call Edge Functions.
Vault secrets (required)
Run these SQL commands in the Supabase SQL Editor:
select vault.create_secret(
'https://{SUPABASE_PROJECT_ID}.supabase.co/functions/v1',
'edge_functions_url'
);
select vault.create_secret(
'{SERVICE_ROLE_KEY}',
'edge_functions_token'
);Replace {SUPABASE_PROJECT_ID} and {SERVICE_ROLE_KEY} with your actual values. You can find them in Project Settings > API Keys in the Supabase Dashboard.
Without these secrets, incoming WhatsApp messages will be received by the webhook but will not be processed. The database triggers that forward messages to the agent and dispatcher functions will silently fail.
Edge Functions with external webhooks
Functions that receive requests from external services (Meta, Stripe) must be deployed without JWT verification:
npx supabase functions deploy whatsapp-webhook --no-verify-jwt
npx supabase functions deploy stripe-webhook --no-verify-jwtThe config.toml sets verify_jwt = false for these functions, but the Supabase GitHub Integration may not respect this setting. Deploying via CLI ensures the flag is applied.
Supabase Auth
Enable the authentication providers you want in Authentication > Providers:
- Email — for email/password login and signup
- Google — requires a Google OAuth Client ID and Secret
- GitHub — requires a GitHub OAuth App
Add your domain to Authentication > URL Configuration > Redirect URLs:
https://app.yourdomain.com/**