How Triggers Work
Event-Driven Actions
Triggers execute automatically based on user interactions - when responses are created, updated, or deleted in your chatflow.
Dynamic Content
All triggers support dynamic content using user responses, variables, and other trigger outputs for personalized automation.
Flexible Timing
Choose instant execution (blocking) or event-based triggers that run in the background without interrupting user experience.
Error Handling
Built-in status reporting and error handling ensure reliable execution of critical business processes.
Trigger Types
Email TriggerSend automated emails with dynamic content, attachments, and professional formatting based on user responses.Perfect For:
- Welcome emails and confirmations
- Application status notifications
- Document delivery and reports
- Customer onboarding sequences
- Approval and rejection notices
- Template support with variable substitution
- Multiple recipients and CC/BCC
- File attachments from other triggers
- Custom reply-to configuration
- Professional HTML formatting
Trigger Execution Options
Instant/Blocking Execution
Immediate ProcessingExecute triggers immediately and wait for completion before allowing users to proceed.
- Best for: Critical calculations, validations, real-time processing
- User Experience: Brief loading while trigger completes
- Use Case: Financial calculations that affect next questions
Event-Based Execution
Background ProcessingTriggers execute in the background without interrupting user experience.
- Best for: Notifications, data sync, non-critical processing
- User Experience: Seamless flow continuation
- Use Case: Email notifications, CRM updates, document generation
Trigger Events
Response Events
Response Events
When to Execute Triggers
- On Create - When user first provides a response
- On Update - When user changes an existing response
- On Delete - When response data is removed
- On All Events - Execute on any response change
Conditional Execution
Conditional Execution
Smart Trigger ActivationTriggers can be enabled or disabled based on:
- User response values
- Calculated variables
- External data conditions
- Business rule requirements
Real-World Implementation Examples
Financial Services Workflow
1
Application Submission
User completes loan application chatflow with personal and financial information
2
Instant Risk Assessment
Calculation Trigger (blocking) performs real-time risk scoring and eligibility check
3
Document Generation
PDF Trigger generates personalized pre-approval letter or application summary
4
CRM Integration
Webhook Trigger creates lead record in Salesforce with risk score and documents
5
Team Notification
Slack Trigger alerts loan officers about high-value applications requiring review
6
Customer Communication
Email Trigger sends confirmation email with next steps and generated documents
Insurance Onboarding Process
Integration Capabilities
Dynamic Content
Resource URIsReference user responses, variables, and other trigger outputs throughout your automation workflows.
Complex Transformations
Business LogicApply sophisticated data transformations and business rules before sending to external systems.
Error Recovery
Reliability FeaturesBuilt-in retry logic, error reporting, and status tracking for mission-critical processes.
Best Practices
Performance Optimization
Choose the Right Execution Type
Choose the Right Execution Type
Blocking vs Background
- Use blocking triggers for calculations that affect subsequent questions
- Use background triggers for notifications and non-critical integrations
- Consider user experience impact when choosing execution timing
Optimize Trigger Chains
Optimize Trigger Chains
Efficient Workflows
- Chain related triggers logically (calculation → document → notification)
- Use conditional execution to avoid unnecessary processing
- Consider API rate limits for external integrations
Error Handling
Plan for Failures
Plan for Failures
Robust Implementation
- Include fallback logic for external API failures
- Implement appropriate timeout settings
- Use status reporting to monitor trigger performance
- Plan alternative flows when triggers fail
Data Validation
Data Validation
Quality Assurance
- Validate data before sending to external systems
- Use proper error messages for user feedback
- Implement data sanitization for security
- Test edge cases and boundary conditions
Security & Compliance
Enterprise SecurityWizflow triggers support enterprise-grade security requirements:
- Encrypted Data Transfer - All external communications use HTTPS/TLS
- Authentication Support - Bearer tokens, API keys, OAuth integration
- Data Privacy - GDPR-compliant data handling and retention
- Audit Trails - Complete logging of trigger execution and data flow
- Access Controls - Role-based permissions for trigger configuration
Integration ConsiderationsWhen implementing triggers with external systems:
- Test thoroughly in staging environments before production
- Monitor performance and set appropriate timeouts
- Handle rate limits for external APIs gracefully
- Secure credentials using proper secret management
- Plan for downtime of external services
Related Features
Variables
Create calculated values to use as trigger inputs and dynamic content
Conditional Logic
Use conditional execution to trigger actions only when conditions are met
Entities Overview
Understand the data sources available for trigger processing
Platform Integrations
Technical details about external system integration capabilities