Features
Custom Events
Funnels
Triggers
Email Forwarding
Need help? Email us

Triggers

Triggers react to what happens on your site in real time — send a Discord message or an HTTP request when something specific occurs.

How triggers work

A trigger watches a source and runs an action whenever it matches. The source can be:

  • A tracked event — for example a page view or a custom event such as Register.
  • A received email — incoming mail to an alias on your domain (requires Email Forwarding).

Creating a trigger

Go to the Triggers section of your dashboard and create a new trigger. You configure three things:

  1. Source — what to watch for.
  2. Conditions — optionally narrow down which occurrences count, for example matching a specific event name or email subject.
  3. Action — what happens when the trigger fires.

Actions

Discord

Send a message to a Discord channel. Create a webhook URL in your Discord server settings and paste it into the trigger. The message template supports {property} placeholders, so you can include event data in the message.

HTTP request

Send an HTTP request to any URL — suitable for connecting your own backend, or services such as Zapier and IFTTT. You can configure the method, headers, and body, and use the same {property} placeholders in the body. A typical payload looks like this:

http
POST /your-endpoint HTTP/1.1 Content-Type: application/json { "event": "Register", "timestamp": 1634567890, "data": { ... } }

Email triggers

With Email Forwarding configured, a trigger can fire when an email is received at one of your aliases. Conditions let you match on the recipient address, the sender, or the subject — for example, get a Discord notification whenever an invoice arrives.