Overview
Triggers enable you to automate your Utari workers by scheduling them to run at specific times or in response to events. This powerful automation capability allows your workers to perform tasks daily, hourly, or on custom schedules—completely hands-free. Whether you need daily reports, regular monitoring, or event-driven responses, triggers make it possible.Types of Triggers
Utari supports two types of triggers for different automation needs:Schedule Trigger
Event-Based Trigger
Where to Create Triggers
You can create triggers from two locations in Utari:Option 1: Within the Worker
Select Your Worker
Find Triggers Section
Create New Trigger
Option 2: From Triggers Tab
Navigate to Triggers
Add New Trigger
Select Worker
Creating a Schedule Trigger
Let’s create a schedule trigger step by step:Select Trigger Type
Select Agent/Worker
Name Your Trigger
Configure Schedule
- Every minute
- Every 5 minutes
- Every 15 minutes
- Every 30 minutes
- Every hour
- Daily at 9 AM (default)
- Daily (choose specific time)
- Weekly (choose day and time)
- Monthly (choose date and time)
- Execute once at a specific date and time
- Custom cron expressions for complex schedules
Set Time Zone
Choose Execution Method
Provide Instructions
- What tools to use
- What information to gather
- What output to create
- Where to save results
Create Schedule Task
Schedule Configuration Options
Quick Schedules
Pre-configured intervals for common use cases:Every Minute
Every Minute
- Real-time monitoring
- High-frequency data collection
- Urgent alert systems
Every 5 Minutes
Every 5 Minutes
- Frequent status checks
- Regular data updates
- Near-real-time reporting
Every 15 Minutes
Every 15 Minutes
- Periodic monitoring
- Regular data synchronization
- Moderate-frequency updates
Every Hour
Every Hour
- Hourly reports
- Regular content aggregation
- Scheduled data processing
Daily at 9 AM
Daily at 9 AM
- Daily reports and summaries
- Morning briefings
- Daily content creation
- Overnight processing
Recurring Schedules
Advanced Scheduling
For complex schedules, use cron expressions:Writing Effective Trigger Instructions
The instructions you provide determine what your worker does when triggered. Follow these best practices:Be Specific and Clear
❌ Vague Instructions:Include All Necessary Steps
Specify Tools and Resources
Define Output Requirements
Managing Triggers
Once created, triggers appear in your triggers list with management options:View Trigger Status
Active
Paused
Failed
Trigger Actions
From the triggers list, you can:View Details
Edit Trigger
- Schedule timing
- Time zone
- Instructions
- Worker selection
Pause/Resume
Delete Trigger
View Execution History
- Execution timestamps
- Success/failure status
- Generated outputs
- Error logs (if any)
Common Trigger Use Cases
Daily Reporting
Morning Briefings
Regular Monitoring
Competitor Tracking
Content Automation
Social Media Content
Data Processing
Analytics Compilation
Task Management
Project Updates
Reminders and Follow-ups
Follow-up Automation
Best Practices
Test Before Scheduling
Start Simple
Monitor Initially
Use Descriptive Names
Set Appropriate Frequency
Document Purpose
Verify Time Zones
Plan for Failures
Troubleshooting
Trigger not executing
Trigger not executing
- Trigger status is “Active” not “Paused”
- Schedule settings are correct
- Time zone is set properly
- Worker has all required tools and integrations
- Instructions are valid and clear
- View execution history for error messages
Trigger runs at wrong time
Trigger runs at wrong time
- Time zone setting matches your location
- Schedule configuration is correct (AM vs PM)
- Daylight saving time considerations
- Server time vs local time differences
Worker errors during execution
Worker errors during execution
- Execution history for specific error messages
- Worker has necessary permissions for all tools
- Instructions are properly formatted
- External services (integrations) are accessible
- Test the same instructions manually
Incomplete or incorrect output
Incomplete or incorrect output
- Making instructions more specific and detailed
- Breaking complex tasks into steps
- Specifying exact output format and location
- Testing instructions manually first
- Adding error handling instructions
Can't edit or delete trigger
Can't edit or delete trigger
- Pausing the trigger first
- Refreshing the page
- Checking your permissions
- Waiting for current execution to complete
- Contact support if issue persists
Too many executions/costs
Too many executions/costs
- Reducing trigger frequency
- Making worker tasks more efficient
- Consolidating multiple triggers
- Pausing unnecessary triggers
- Using one-time triggers for testing