Supabase Trigger

overview the supabase trigger node monitors a supabase database table and starts a workflow when data changes (insert, update, delete) it enables real time database event handling without polling classification node type trigger node → external events purpose react to supabase database changes activation realtime or webhook events insert, update, delete key features real time monitoring live database event detection multiple event types choose specific operations webhook alternative http callback mode available payload customization select which fields to emit column filtering trigger on specific columns only configuration fields credential supabase project url and api key service account recommended for webhooks must have replication/webhook permissions schema database schema (default public) custom schemas supported with permissions table table name to monitor must exist and be accessible events insert new row added update row modified delete row removed all trigger on any change mode realtime live updates via replication (low latency) webhook http post callbacks (reliable) setup process use supabase trigger as workflow start connect supabase credentials select schema and table choose event types select mode (realtime or webhook) save and test connect to downstream nodes trigger workflow by making database change output data payload includes operation type (insert, update, delete) new row data old row data (for updates/deletes) changed columns timestamp access {{triggerdata new}} new values {{triggerdata old}} previous values {{triggerdata operation}} change type mode comparison realtime live updates, low latency requires publication setup best for immediate reactions webhook reliable, simpler setup slight delay possible best for production workflows requirements supabase project active account with credentials database access user/service account with permissions table setup table must exist and be accessible realtime mode publication and replication enabled use cases new user registration trigger on insert order status change trigger on update data archival trigger on delete real time sync keep systems synchronized event notifications alert on changes dashboard updates live data refresh configuration example monitor all changes in users table schema public table users events all mode realtime monitor new orders only schema public table orders events insert only mode webhook common errors authentication failed verify api key and permissions table not found check table name spelling permission denied check rls policies webhook timeout ensure endpoint responds publication error enable replication on table best practices use service account credentials enable appropriate rls policies filter to necessary columns choose correct mode for use case test configuration thoroughly monitor execution logs add error handling downstream quick reference type trigger node category external events start database changes output old/new data + operation type modes realtime, webhook events insert, update, delete