Skip to main content
Triggers let you execute webhooks automatically when changes occur in your collections. They are ideal for synchronizing data with external systems, sending notifications, or running workflows.
Triggers page with empty state and New trigger button

Triggers section in Databases settings

Creating a trigger

New trigger form with Name, Collection, Event (Create, Update, Delete), Webhook Request, Headers, and Status fields

Form for creating a new trigger with events and webhook configuration

1

Go to Triggers

Navigate to Settings > Triggers from the left sidebar.
2

Click + New trigger

The button is located in the upper-right corner.
3

Configure the trigger

Fill in the following fields:
  • Name — A descriptive name (e.g. “Sync CRM”, “Notify new order”)
  • Collection — The collection you want to monitor
  • Event — The type of event that fires the webhook
  • Update scope — Only for the Update event: fires on any column or only specific columns
  • Webhook Request — The HTTP method and destination URL
  • Headers — Custom headers for the request
  • Status — Enable or disable the trigger
4

Click Create trigger

The trigger activates immediately if the status is set to Active.

Available events

You can create multiple triggers for the same collection with different events. For example, one trigger to synchronize data on each Create and another to send an alert on each Delete.

Update scope

When the event is Update, an additional Update scope control appears with two options: When you choose Specific columns you must select at least one column. The Create and Delete events always use “any column” and don’t show this control.

Webhook configuration

HTTP method

Select the appropriate HTTP method for your endpoint:

Webhook URL

Enter the full URL of the endpoint that will receive the notification (e.g. https://your-api.com/webhooks/databases).
The URL must be public and use HTTPS.

Headers

Add custom headers for authentication or other purposes. By default, an example Authorization header with Bearer token format is included. Click + Add header to add additional headers. Each header has a name (key) and value field.

Automatic retries

If a webhook delivery fails, Databases retries it automatically.

Trigger status

The Status toggle lets you enable or disable a trigger without deleting it. A disabled trigger does not send webhooks even if events occur in the collection.