> ## Documentation Index
> Fetch the complete documentation index at: https://flywheel.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Event Trigger
> Respond to specific user actions or events that occur in your application
## How Event Triggers Work
When a user performs an action that matches your trigger configuration, the workflow immediately starts processing that user through your workflow. Event triggers respond to specific user actions or events that occur in your application and are perfect for real-time responses to user behavior.
## Configuration
Select the specific event name that should start your workflow. Examples: `user_signed_up`, `subscription_created`, `purchase_completed`, `page_viewed`.
The complete event data that triggered the workflow.
Unique database identifier for this event.
Unique external identifier for this event.
The name of the event that triggered the workflow.
ISO datetime when the event occurred.
ISO datetime when the event was created in the system.
Internal Flywheel user identifier associated with the event.
Your company's external user identifier, if available.
Organization identifier.
Anonymous identifier for the user, if available.
The source of the event (e.g., web, mobile, API).
The location where the event occurred, if available.
The type of event: `track` or `identify`.
Schema identifier for the event structure, if applicable.
Factory schema identifier, if applicable.
Contains all event-specific data and custom properties specific to your application and event type.
Comprehensive user information for the user who triggered the event.
Unique user identifier.
Organization identifier.
Your company's external user identifier.
User's primary email address.
User's primary phone number.
User's first name.
User's last name.
ISO datetime when the user was created.
ISO datetime when the user was last updated.
Current subscription status: `incomplete`, `incomplete_expired`, `trialing`, `active`, `past_due`, `canceled`, `unpaid`, `paused`, `inactive`.
Payment processor used: `stripe` or `paddle`.
Monthly recurring revenue from this user.
Lifetime value of the user.
ISO datetime of user's first payment.
ISO datetime of user's next scheduled payment.
ISO datetime when subscription will be cancelled (if applicable).
User's preferred contact method.
Additional contact information and preferences.
Customer Success Manager information assigned to this user.
Custom user properties you've defined.
## Use Cases
**New User Onboarding**
```
Event: user_signed_up
Condition: None (trigger for all new users)
Result: Starts onboarding workflow immediately after signup
```
**High-Value Purchase Follow-up**
```
Event: purchase_completed
Condition: purchase_amount > 1000
Result: Triggers premium customer welcome sequence
```
**Feature Adoption Campaigns**
```
Event: feature_used
Condition: feature_name = "advanced_analytics"
Result: Sends advanced tips and usage guides
```
**Subscription Status Changes**
```
Event: subscription_canceled
Condition: cancellation_reason = "pricing"
Result: Offers discount or alternative pricing options
```
## Best Practices
**Consider Event Frequency**
* Some events may fire multiple times for the same user
* Plan for duplicate events and implement appropriate safeguards
* Use workflow conditions to prevent redundant communications
**Monitor Performance**
* Track trigger activation rates and workflow completion
* Optimize based on user engagement and conversion data
* A/B test different trigger conditions and timing