One-time setup: (1) Sign up and connect your Supabase project through OAuth authentication. (2) Add your FCM Server Key (for Android) or APN certificate (for iOS) in the dashboard. (3) Install our SDK in your app and call the register method with user_id when users log in (and unregister when they log out). Recurring step: (4) Create notification triggers by selecting a table, event type (insert/update/delete), and customizing your message template. That's it - notifications start working immediately.

Click 'Connect Supabase' in the dashboard and you'll be redirected to Supabase's official OAuth login. We never see your password. Once authorized, we receive secure access through the Supabase Management API to enable necessary extensions (pg_net, supabase_vault) and read your table schemas to help you configure notifications. You can revoke access anytime from your Supabase dashboard.

For Android: Get your FCM Server Key from Firebase Console (Project Settings > Cloud Messaging) and paste it in Entrig dashboard. For iOS: Upload your .p8 APN authentication key from Apple Developer portal along with your Team ID and Key ID. We encrypt all credentials before storing them. These credentials allow us to send push notifications on your behalf.

Install our SDK for your platform (Android/iOS/Flutter), initialize it with your Project API Key from the dashboard, and call the register method with the user's ID when they log in. The SDK handles device token registration with FCM/APNs and syncs it with Entrig. When your database triggers fire, we use these tokens to deliver notifications. Call unregister when users log out.

In the dashboard, select a table from your Supabase database, choose the event type (INSERT, UPDATE, or DELETE), and customize your notification message using column placeholders like {{user_name}} or {{order_total}}. We automatically generate a PostgreSQL function and trigger in your database that sends notifications whenever that event occurs. You can test it immediately and see the generated SQL code.

No. While OAuth technically allows database access, we only read table schemas (column names, types, relationships) to help you configure notifications. We don't query your user data. When notifications trigger, your database function sends only the specific fields you configure in the payload, which we immediately forward to FCM/APNs without storing.

We create database functions and triggers that follow the 'entrig_*' naming pattern. These functions only READ data to build notification messages - they never write, update, or delete your data. You have full visibility and can inspect them anytime. If you delete them, notifications will stop working.

We handle it automatically. If there's a temporary issue with FCM or APNs, we retry the delivery. If a token has expired (like when users uninstall your app), we mark it as invalid so it's not used again.