​

Workflow Triggers

​

How to Choose the Right Trigger

​

Contact Triggers

​

Example: Welcome New Users

Trigger: Contact.Identified
├── Contact Filter: First time visitor
│   ├── Success: Send welcome email
│   └── Add to "New Users" list
└── Award: 50 welcome points

​

Gameplay Triggers

​

Example: Lead Qualification Flow

Trigger: Gameplay.DataCapturedQualified
├── Contact Filter: Company size > 100 employees
│   ├── Success: 
│   │   ├── Webhook to Salesforce CRM
│   │   └── Tag: "Enterprise Lead"
│   └── Fallback:
│       ├── Add to "SMB Nurture" email sequence
│       └── Tag: "SMB Lead"

​

Prize Triggers

​

Example: Winner Notification System

Trigger: Prize.Awarded
├── Contact Filter: Prize value > $50
│   ├── Success: Send premium winner email + SMS
│   └── Fallback: Send standard winner email
├── Add to List: "Prize Winners"
└── Webhook: Notify fulfillment system

​

Card Triggers

​

Example: Interest Tracking

Trigger: Card.CoverClicked
├── Contact Update: Increment "card_clicks" counter
├── Tag: "Engaged User"
└── Decision: If clicks > 5 this week
    └── Success: Add to "Highly Engaged" list

​

Loyalty Triggers

​

Example: Tier Upgrade Celebration

Trigger: Loyalty.TierAdded
├── Contact Filter: New tier = "Gold"
│   ├── Success: 
│   │   ├── Send gold tier welcome email
│   │   ├── Issue 500 bonus points
│   │   └── Send exclusive discount code
└── Add to List: "Gold Members"

​

Webhook Triggers

​

How webhook triggers work

​

Using webhook data in workflow steps

• {{ webhook.user_id }}
• {{ webhook.amount }}

​

Example: External purchase sync

Trigger: Webhook.Received
  Schema: { user_id: string, amount: number, product: string }
├── Contact Filter: webhook.amount > 100
│   ├── Success:
│   │   ├── Award loyalty points (webhook.amount × 2)
│   │   └── Send "VIP Purchase" email
│   └── Fallback:
│       └── Award loyalty points (webhook.amount)
└── Contact Update: Set "last_purchase" = webhook.product

​

Setting up a webhook trigger

1. Create a new workflow and select Webhook.Received as the trigger event
2. A unique webhook slug is generated for your workflow — this forms your webhook URL
3. Optionally define a request schema using JSON Schema format to describe the expected payload structure
4. Use the schema fields as Liquid variables in your workflow actions (e.g., email templates, contact updates, filters)

​

Advanced Trigger Strategies

​

1. Trigger Stacking

# Welcome sequence with multiple entry points
Trigger 1: Contact.Identified (new users)
Trigger 2: Contact.Verified.Sso (returning users)
Both → Same welcome workflow with different paths

​

2. Qualification Layering

Trigger: Gameplay.DataCaptured (all submissions)
├── Contact Filter: Email contains company domains
│   └── Success: Route to B2B workflow
└── Fallback: Route to B2C workflow

​

3. Time-Based Follow-ups

Initial: Prize.Awarded
├── Immediate: Send winner notification
├── After 24h: Send claim reminder (if not claimed)
└── After 7 days: Send final reminder

​

Troubleshooting Triggers

​

Common Issues

​

Testing Tips

1. Start with broad triggers - Use Gameplay.Action to see all events
2. Add logging - Use webhook actions to log trigger data
3. Test with real data - Use actual user interactions, not simulated events
4. Monitor execution volume - Check Workflow Runs for unexpected patterns

​

Best Practices

​

✅ Do This

• Be specific - Use qualified triggers when possible (DataCapturedQualified vs DataCaptured)
• Add context filters - Narrow scope with contact properties or gameplay data
• Plan for scale - Consider execution volume for broad triggers
• Document trigger purpose - Name workflows clearly to indicate trigger intent

​

❌ Avoid This

• Don’t use overly broad triggers without filters (Contact.PropertyUpdated without field specification)
• Don’t stack identical triggers - Combine similar workflows instead
• Don’t ignore data availability - Ensure required data exists when trigger fires
• Don’t skip testing - Always verify triggers fire as expected

​

What’s Next?

• Browse workflow actions → - Explore actions to pair with these triggers
• Back to workflows guide → - Return to main workflows documentation