Trigger

BaaS Tables Trigger

The BaaS Tables Trigger transforms your nLink workspace into a highly reactive Backend-as-a-Service. Instead of polling for changes, this trigger automatically activates a workflow precisely when a specific Data Table event occurs (like a new record being inserted, or an existing one modified), instantly pushing the changed data payload directly into your workflow.

BaaS Tables Trigger

Core / Trigger

⚠️

What can you do with BaaS Tables Trigger?

Real-time Reactivity

Fire workflows instantly upon database modifications without any scheduled delays. Perfect for sending a welcome email the exact second a new user record is inserted.

Rich Payload Context

Receives the complete data object representing the modified row. You don't have to query the database again to find out what changed; the exact data is injected straight into the pipeline.

Granular Event Listening

Listen specifically to targeted events. Set the trigger to fire ONLY when a row is 'created', 'updated', or 'deleted', ensuring tight control over your execution quota.

Detailed Usage & Configuration

The BaaS Tables Trigger acts as the central nervous system for your built-in database tables. It allows nLink to function exactly like Supabase or Firebase by triggering serverless functions instantly on data mutations.

1. Selecting the Event

You must specify which Table to listen to, and what Event should wake up the workflow:

On Row Created: Perfect for initial onboarding logic (e.g. sending data to a CRM when a lead is logged).
On Row Updated: Ideal for alerting. Send a Slack notification if an invoice record's status changes to 'Paid'.
On Row Deleted: Useful for cascading cleanups. If a user is deleted from the table, trigger an API to also delete them from your email marketing list.

2. Consuming the Trigger Payload

When the event fires, the node outputs a heavily structured JSON payload containing exactly what happened:

{
  "event": "created",
  "tableId": "tbl_xyz123",
  "payload": {
    "name": "Jane Doe",
    "email": "jane@example.com",
    "_row_id": "row_abc789",
    "_created_at": 1715421200000
  }
}

You can instantly map this data downstream using variables like {{ $json.payload.email }} without executing any further database lookups.