When something happens, do something.
A user signs up — send a welcome email. A record changes — call your webhook. An order is paid — send a push notification. Set it once. We run it every time.
When X happens, do Y
Image placeholder — hero illustration
Stop writing the same glue code.
Every app needs small jobs. Send a note when a user joins. Tell another system when data changes. You do not write that code again. You pick the event. You pick the action. You save.
Pick an event. Pick an action.
Try it. Each pair you see here works.
1. When
2. Then
When — five places events come from
- Database. When a record is added, changed or deleted.
- Membership. When a user signs up, is invited, verifies, changes, is blocked, comes back or is deleted.
- Files. When a file is uploaded or deleted.
- Payments. When an order is created or paid, or your payment provider calls back.
- AI. When your AI credits or quota run low, or run out.
Then — seven things that can happen
- Email. We send an email from your template.
- SMS. We send a text message from your template.
- Push. We send a push notification from your template.
- Webhook. We call your webhook with the event.
- Run a cloud function. We run your own code on AWS Lambda, Azure Functions or Google Cloud Functions.
- Live update. We send a live update to apps that are open.
- Marketplace. We run a function you installed from the marketplace.
Email, SMS and push actions start a campaign. It is the same campaign engine you use in Messaging.
Watch it work.
Pick the event. Pick the action. Save. It runs on its own.
How it works
Pick the event
Choose where it comes from and what happens. A new user. A changed record. A paid order.
Pick the action
Email, SMS, push, a webhook, your own cloud function, a live update or a marketplace function.
Save and switch it on
It runs each time the event happens. Switch it off when you do not need it.
When things go wrong
You see it
A message that cannot go out marks the trigger "Needs attention". The mark goes away after the next good run.
The others keep going
One trigger fails. The next trigger for the same event still runs.
Every run is written down
Each run keeps its status. You can see what ran and what failed.