Skip to main content
Komo’s Schedules & Triggers system enables you to automate recurring work and respond to events in real-time. Whether you need daily reports, monthly analysis, or instant responses to specific events across your tools, Komo handles it automatically.

​
What are Schedules & Triggers?

Clean Shot 2026 01 06 At 14 35 36@2x Schedules let you run agents at specific times—daily, weekly, monthly, or custom intervals. Perfect for recurring workflows like reports, monitoring, and periodic analysis. Triggers activate agents based on events in your connected applications—new emails, calendar events, Slack messages, GitHub issues, and more. Perfect for real-time automation and event-driven workflows. Together, they eliminate manual task initiation and enable true 24/7 autonomous operations.

​
Schedule

Clean Shot 2026 01 06 At 14 32 59@2x

​
Quick Schedule

Run agents immediately or after a brief delay. Use Cases:
  • Test a workflow before setting up recurring execution
  • One-time delayed execution
  • Immediate processing with manual trigger
Example: 
"Analyze last week's support tickets and post summary to #customer-success"

​
Recurring Schedule

Run agents at regular intervals. Frequency Options:
  • Every minute - Real-time monitoring and rapid processing
  • Every 5 minutes - Near real-time workflows
  • Every 15 minutes - Frequent check-ins
  • Every 30 minutes - Regular interval processing
  • Every hour - Hourly updates and monitoring
  • Every day - Daily reports and summaries
  • Every week - Weekly analysis and reviews
  • Every month - Monthly reports and audits
Example for agent builder: 
"Every Monday at 8 AM: Research top 5 competitors for product updates, pricing changes, and news. Create summary report and post to #competitive-intel Slack channel"

​
One-Time Schedule

Schedule a single execution for a specific future date and time. Use Cases:
  • Delayed execution for specific date
  • Event preparation (report generation day before meeting)
  • Scheduled reminders and follow-ups
Example for agent builder: 
"On February 1st at 9 AM: Generate Q4 financial summary, analyze trends, and email to CFO with recommendations"

​
Advanced Schedule

Custom scheduling with complex patterns using cron expressions. Use Cases:
  • Multiple specific days (e.g., every Tuesday and Thursday)
  • Specific dates of the month (e.g., 1st and 15th)
  • Complex business logic (e.g., last business day of month)
Example for agent builder: 
"Every Tuesday and Thursday at 2 PM: Check inventory levels, flag items below threshold, create purchase orders in ERP system"

​
Event Triggers

Event triggers activate agents automatically when specific events occur in your connected applications. Clean Shot 2026 01 06 At 14 33 54@2x

​
Supported Trigger Applications

​
Communication & Collaboration

Gmail - Trigger on:
  • New email received
  • Email matching specific criteria (sender, subject, label)
  • Email sent
  • Label applied to email
Slack - Trigger on:
  • New message in channel
  • Direct message received
  • Mention of specific keywords
  • Emoji reaction added
Outlook - Trigger on:
  • New email received
  • Calendar event created/updated
  • Meeting invitation received
Discord - Trigger on:
  • New message in channel
  • Direct message received
  • Role assigned

​
Productivity & Project Management

Notion - Trigger on:
  • New page created
  • Database entry added/updated
  • Page property changed
  • Comment added
Google Calendar - Trigger on:
  • Event created
  • Event updated
  • Event starting soon (15 min before)
  • Event completed
Google Drive - Trigger on:
  • File uploaded
  • File modified
  • File shared with you
  • Folder created
Google Docs/Sheets/Slides - Trigger on:
  • Document created
  • Document edited
  • Comment added
  • Shared with team
Asana - Trigger on:
  • Task created
  • Task assigned to you
  • Task completed
  • Due date approaching
Linear - Trigger on:
  • Issue created
  • Issue assigned
  • Issue status changed
  • Comment added
Jira - Trigger on:
  • Issue created/updated
  • Status changed
  • Comment added
  • Sprint started/completed
Trello - Trigger on:
  • Card created/moved
  • Checklist completed
  • Comment added
  • Due date approaching
Todoist - Trigger on:
  • Task created
  • Task completed
  • Project created
Coda - Trigger on:
  • Row added to table
  • Document updated
  • Button pressed

​
Development & Code

GitHub - Trigger on:
  • New issue opened
  • Pull request created
  • Code pushed to repository
  • Release published
  • Issue comment added
GitLab - Trigger on:
  • Merge request created
  • Pipeline completed
  • Issue created

​
Customer & Sales

HubSpot - Trigger on:
  • New contact created
  • Deal stage changed
  • Form submission received
  • Email opened/clicked
Salesforce - Trigger on:
  • New lead created
  • Opportunity stage changed
  • Account updated
  • Task assigned
Pipedrive - Trigger on:
  • Deal created/updated
  • Activity completed
  • Contact added
Zendesk - Trigger on:
  • Ticket created
  • Ticket priority changed
  • Comment added
  • Ticket solved
Stripe - Trigger on:
  • Payment received
  • Subscription created/cancelled
  • Invoice paid/failed
  • Refund issued
Mailchimp - Trigger on:
  • Subscriber added
  • Campaign sent
  • Email opened

​
Other Platforms

Canvas - Trigger on:
  • New submission
  • Assignment graded
Fireflies - Trigger on:
  • Meeting recorded
  • Transcript available
Spotify - Trigger on:
  • Playlist updated
  • Song saved
YouTube - Trigger on:
  • Video uploaded
  • Comment received
and more… See the full list in the app.

​
Real-World Examples

​
Example 1: Daily Competitive Intelligence (Schedule)

Schedule: Every weekday at 7 AM EST Workflow: 
"Every weekday at 7 AM:
1. Research these 10 competitors for:
   - New blog posts or press releases
   - Product updates or launches
   - Pricing changes
   - Job postings (especially executive roles)
   - LinkedIn company updates
2. Create structured summary with key findings
3. Post to #competitive-intel Slack channel
4. If major news found: @ mention @strategy-team"
Result:
  • Team starts day with fresh competitive intelligence
  • No manual monitoring required
  • Major updates escalated automatically
  • Complete history maintained in Slack

​
Example 2: Automated Customer Onboarding (Event Trigger)

Trigger: New deal marked “Closed Won” in Salesforce Workflow: 
When deal status changes to "Closed Won":
1. Extract customer details from Salesforce
2. Create customer workspace in Notion using template
3. Generate onboarding task list in Linear
4. Create dedicated Slack channel, invite team
5. Send welcome email via Gmail
6. Schedule kickoff call in Google Calendar
7. Set up billing in Stripe
8. Post summary to #customer-success: "New customer: [Company] - Onboarding initiated"
Result:
  • Zero manual coordination
  • Instant onboarding activation
  • 100% consistent process
  • Customer success team notified immediately

​
Example 3: Security Incident Response (Event Trigger)

Trigger: Critical alert in Datadog or new message in #security-alerts Slack channel Workflow: 
When critical Datadog alert received OR keyword "CRITICAL" in #security-alerts:
1. Analyze alert severity and context
2. Query Splunk for related logs (last 1 hour)
3. Check AWS for affected infrastructure
4. Create incident ticket in Linear with findings
5. Post detailed summary to #security-incidents
6. If customer-impacting: escalate to PagerDuty
7. Document timeline in Notion incident log
8. Send notification to [email protected]
Result:
  • Initial triage completed in under 2 minutes
  • Consistent investigation methodology
  • Complete documentation automatically
  • Appropriate escalation based on severity

​
Example 4: Monthly Financial Close (Schedule)

Schedule: First business day of each month at 6 AM Workflow: 
On the 1st of every month at 6 AM:
1. Export all transactions from Stripe (previous month)
2. Pull closed deals from Salesforce
3. Reconcile revenue against QuickBooks invoices
4. Update financial model in Google Sheets
5. Calculate variances vs. budget
6. If variance > 10%: create analysis tasks in Linear
7. Generate preliminary close summary
8. Email CFO and finance team with findings
9. Post summary to #finance Slack channel
10. Update month-end close tracker in Notion
Result:
  • Month-end close process starts before team arrives
  • Initial reconciliation completed automatically
  • Issues flagged proactively
  • 3-5 days reduced from close cycle time

​
Example 5: Support Ticket Triage (Event Trigger)

Trigger: New ticket created in Zendesk Workflow: 
When new Zendesk ticket received:
1. Analyze ticket content and urgency
2. Check if customer exists in Salesforce
3. Pull customer context: ARR, health score, support history
4. Search knowledge base (Notion) for relevant articles
5. If known issue: draft response with solution
6. If urgent + high-value customer: escalate priority to "High"
7. Assign to appropriate team based on category
8. Post to #customer-support Slack: "New ticket #[ID] - [Summary] - Priority: [Level]"
9. If VIP customer: @ mention account manager
Result:
  • Every ticket triaged within seconds
  • Complete customer context provided
  • Appropriate prioritization and routing
  • Support team focuses on solving, not researching

​
Example 6: GitHub Issue Management (Event Trigger)

Trigger: New issue created in GitHub repository Workflow: 
When new issue opened in [ProductName] repository:
1. Analyze issue content for type: bug, feature request, question
2. Check for similar existing issues
3. If duplicate: comment with link, suggest closing
4. If bug: label as "bug", add reproduction steps template if missing
5. If feature request: label as "enhancement", check against product roadmap in Notion
6. Extract technical details and create summary
7. Create corresponding Linear issue for product team
8. Post to #engineering Slack with summary and priority suggestion
9. If security-related: escalate to #security-incidents immediately
Result:
  • Every issue triaged and categorized automatically
  • Duplicates identified immediately
  • Product team notified with context
  • Security issues escalated without delay

​
Example 7: Weekly Team Sync Preparation (Schedule)

Trigger: Every Friday at 4 PM Workflow: 
Every Friday at 4 PM:
1. Pull completed tasks from Linear (past week)
2. Extract key metrics from analytics dashboard
3. Review Slack #wins channel for highlights
4. Check calendar for upcoming milestones
5. Analyze blockers and open issues
6. Generate weekly summary document in Notion:
   - Key accomplishments
   - Metrics and trends
   - Upcoming priorities
   - Blockers requiring discussion
7. Post preview to #team-general Slack
8. @ mention team leads for Monday meeting
Result:
  • Team meeting prep automated
  • Complete context before Monday sync
  • Data-driven discussions
  • No manual status gathering

​
How to Set Up

​
Creating a Schedule

  1. Navigate to agent configuration → Schedules/Triggers section
  2. Click “Configure Schedule”
  3. Choose schedule type:
    • Quick: Immediate or near-immediate execution
    • Recurring: Regular intervals (minute/hour/day/week/month)
    • One-time: Specific future date/time
    • Advanced: Custom cron expression
  4. Select timezone (defaults to your account timezone)
  5. Configure frequency:
    • For recurring: select interval (e.g., “Every day at 9 AM”)
    • For one-time: select specific date and time
    • For advanced: enter cron expression
  6. Name your trigger (e.g., “Daily Competitor Report”)
  7. Add description (optional but recommended)
  8. Enable trigger immediately (toggle on to activate)
  9. Click “Create Trigger”

​
Creating an Event Trigger

  1. Navigate to agent configuration → Schedules/Triggers section
  2. Click “Create Event Trigger”
  3. Step 1 - Select App: Choose the application to monitor
    • Shows connected apps (green “Connected” badge)
    • Shows apps requiring setup (gray “Setup Required”)
    • Search bar for quick filtering
  4. Step 2 - Choose Trigger: Select the specific event type
    • Example: For Gmail → “New email received” or “Email with specific label”
    • Example: For Slack → “New message in channel” or “Keyword mentioned”
    • Example: For GitHub → “New issue opened” or “Pull request created”
  5. Step 3 - Configure: Set trigger parameters
    • Filter criteria (e.g., email from specific sender, Slack message in specific channel)
    • Conditional logic (e.g., only if subject contains “urgent”)
    • Frequency limits (e.g., max once per hour to prevent spam)
  6. Test the trigger to verify it works correctly
  7. Name and save the trigger

​
Managing Schedules & Triggers

​
View Active Schedules/Triggers

Navigate to Agent Configuration → Schedules/Triggers to see:
  • All active schedules and triggers
  • Next scheduled execution time
  • Trigger event source and conditions
  • Execution history

​
Pause/Resume

Toggle any schedule or trigger on/off without deleting. Perfect for temporary suspension.

​
Edit Configuration

Modify timing, frequency, trigger conditions, or workflow without recreating from scratch.

​
Delete

Remove schedules or triggers you no longer need. Cannot be undone.

​
Schedule Configuration Options

​
Timezone Support

Specify timezone for all scheduled executions:
  • Auto-detect based on account settings
  • Manual override: “Every day at 9 AM EST”
  • Handles daylight saving time automatically

​
Recurring Patterns

PatternConfigurationExample Use Case
Every minute1-minute intervalsReal-time monitoring
Every 5 minutes5-minute intervalsFrequent updates
Every 15 minutes15-minute intervalsRegular check-ins
Every 30 minutes30-minute intervalsModerate frequency
Every hourHourlyHourly reports
DailySpecific time each dayDaily summaries
WeekdaysMonday-Friday at timeBusiness reports
WeeklySpecific day/timeWeekly analysis
Monthly1st of month at timeMonthly reports
CustomCron expressionComplex patterns

​
Advanced Cron Expressions

For complex scheduling needs, use cron syntax: 
# Every Tuesday and Thursday at 2 PM
0 14 * * 2,4

# First and fifteenth of each month at 9 AM
0 9 1,15 * *

# Every weekday at 8 AM and 5 PM
0 8,17 * * 1-5

# Last day of every month at 11:59 PM
59 23 L * *

​
Event Trigger Configuration

​
Filter Criteria

Apply filters to narrow trigger activation: Gmail Example:
  • From specific sender: sender:[email protected]
  • Subject contains: subject:URGENT
  • Has attachment: has:attachment
  • Specific label: label:vip-customers
Slack Example:
  • Specific channel: #customer-support
  • Contains keyword: keyword:@komo OR keyword:urgent
  • From specific user: from:@manager
GitHub Example:
  • Repository: repo:company/product
  • Issue label: label:bug
  • Assigned to: assignee:@username

​
Conditional Logic

Add conditions in the playbook to prevent false triggers: 
Trigger: New Zendesk ticket created
Condition: Customer ARR > $50,000 AND priority = "High"
Action: Escalate to VP Customer Success immediately

​
Frequency Limits

Prevent trigger spam:
  • Cooldown period: “Max once per 30 minutes”
  • Batch processing: “Accumulate triggers and process every 15 minutes”
  • Deduplicate: “Ignore duplicate events within 5 minutes”

​
Tips for Better Schedules & Triggers Configs

​
For Schedules

Be specific about timing:
  • ✅ “Every weekday at 8 AM EST”
  • ❌ “In the morning”
Include time ranges for data:
  • ✅ “Analyze data from last 24 hours”
  • ✅ “Review tickets created since last run”
  • ❌ “Recent data” (ambiguous)
Define clear outputs:
  • ✅ “Email summary to [email protected]”
  • ✅ “Post to #analytics Slack channel with charts”
  • ❌ “Share the results”
Test before scheduling:
  • Run workflow manually first to verify
  • Check output format and quality
  • Then set up recurring schedule

​
For Triggers

Use specific filters:
  • ✅ “Gmail: from VIP customers list AND subject contains ‘urgent’”
  • ❌ “Any email”
Add safeguards:
  • ✅ “Max once per 30 minutes to prevent duplicate processing”
  • ❌ No frequency limits (risk of trigger spam)
Consider dependencies:
  • ✅ “When Salesforce deal closes AND Stripe payment received”
  • ❌ “When deal closes” (may trigger before payment confirmed)
Include context in notifications:
  • ✅ “Post to Slack: ‘[Trigger Type] - [Details] - [Action Taken]’”
  • ❌ “Notify team” (lacks context)

​
Common Questions

Q: What happens if a scheduled task fails? A: Komo logs the error, and you could view failure details in execution history. Q: Can I run a workflow both on schedule AND on trigger? A: Yes. Set up multiple triggers for the same agent—one schedule-based, others event-based. Q: What timezone are schedules in? A: Your account timezone (set in Schedule configs). Override by specifying timezone: “9 AM EST” or “14:00 UTC”. Q: How many schedules/triggers can I have? A: Depends on your plan. Standard: 5 per agent. Enterprise: unlimited. Q: Can I test a trigger without waiting for the event? A: Yes. Use “Run Agent” in the playbook editor to simulate the event and verify agent behavior. Q: Do triggers work across time zones? A: Yes. Event triggers fire immediately regardless of timezone. Scheduled triggers respect specified timezone. Q: What happens if I’m not connected to an app when a trigger fires? A: Trigger fails and notifies you to reconnect. Once reconnected, you can manually replay missed events if needed.