For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create a trigger

React to user events with an action.

Where: Membership β†’ Triggers β†’ New Β· /projects/<project>/membership/triggers/new

Screenshot TODO β€” capture comes from testing-plan area 02-triggers.

The form is a two-step flow: If this (the event) … then (the action).

If this β€” pick the event

Event
Fires

When registered (OnRegistered)

A new user registers.

When invited (OnInvited)

A new user is invited.

When verified (OnVerified)

A user is verified.

When updated (OnUpdated)

A user is updated.

When deleted (OnDeleted)

A user is deleted.

When blocked (OnBlocked)

A user is blocked.

When reactivated (OnReactivated)

A user is reactivated.

The user's data is passed to the action, so templates and payloads can use tokens from it.

… then β€” pick the action

Run Code (invoke a serverless function), Send Email, Send Push Notification, Send SMS (all three from a template, with delivery settings for who receives it), Call Webhook (POST a signed event payload to your destinations β€” the webhook event name, e.g. membership.user.registered, is implied by the chosen event), or Send In-App (Realtime / SSE) (deliver live to connected apps or AI agents). Each action opens its own settings block.

Finish

Set the Order (lower numbers run earlier when several triggers share an event) and optionally Break execution queue on failure. Then Name the trigger (e.g. When user registers, send welcome email), add a Description, and switch Is this trigger enabled? on when it is ready. Saving returns you to the list.

How triggers work in general β€” events, action types, and delivery settings β€” is explained in Triggers.

Use it from code

Membership β†’ Triggers

API reference

Endpoints: Save Membership Trigger.

Last updated