Skip to main content
Use this page to add the first trigger to an automation scenario.

​
Overview

A trigger starts an automation scenario. The current automation builder exposes 9 trigger families. Pick the family that matches the event you want to react to, then choose the specific trigger option within that family.

​
Before you start

  • Open Automation.
  • Click Create new scenario.
  • Make sure the source you want to use is already connected under Integrations.

​
Steps

  1. Click Trigger.
  2. Choose the trigger family for the event you want to react to (see the 9 families below).
  3. Choose the specific trigger option within that family.
  4. Save the trigger.
  5. Continue building the scenario with the next step you need.

​
Trigger families

​
1. Shopify

Fires when a Shopify emits an order, cart, or checkout event. See Set up Shopify triggers in automation.

​
2. Commerce

Fires when bitbybit Commerce emits an order event. See Set up Commerce triggers in automation.

​
3. Web activity

Fires when a visitor performs a tracked action on a connected web property (page view, product view, collections view, add item to cart). See Set up Web activity triggers in automation.

​
4. bitLoyalty

Fires when a member earns, redeems, or otherwise mutates points in bitLoyalty. See Set up bitLoyalty triggers in automation.

​
5. Jubelio

Fires on events from the Jubelio inventory/POS integration. See Set up Jubelio triggers in automation.

​
6. Stamped loyalty

Fires on Stamped.io loyalty events (earn rewards, reward used). See Set up Stamped loyalty triggers in automation.

​
7. Custom webhook

Fires when a configured external endpoint POSTs to a bitbybit webhook URL with the expected payload. See Set up Custom webhook triggers in automation.

​
8. Schedule

Fires on a configured schedule for a selected customer segment. Repeat options include daily, weekly, monthly, annually, date of birth, and more. See Set up Schedule triggers in automation.

​
9. Chat trigger

Fires when an inbound message arrives on a connected channel (Incoming Chat) or when a support ticket is resolved (Ticket Resolved) in bitChat. See Set up Chat triggers in automation.

​
What happens next

After the trigger is saved, add the next step for the scenario, such as Communication channel, Time delay, or Conditions.