Schedules & Triggers

Schedules and triggers turn a playbook from a one-click action into an autonomous workflow.

Schedule vs. trigger

	Schedule	Trigger
Activated by	A clock (cron)	An event in a connected app
Typical use	Monday pipeline review, daily Signal Agent run	Inbound reply, “Closed Won,” GitHub issue opened
Set up in	Playbook → Schedules tab	Playbook → Triggers tab

You can put both on the same playbook.

Schedules

Quick — one immediate run for testing. Recurring — built-in cadences:

Cadence	Typical sales use
Every minute	Real-time inbox monitoring for hot leads
Every 5–30 min	Signal Agent → Slack pings
Hourly	Dashboard refresh, urgent reply scan
Daily	Morning pipeline digest, end-of-day recap
Weekly	Monday pipeline review, Friday summary
Monthly	QBR generation, renewal scan

Defaults to your account timezone, DST automatic. One-time — single future run:

On Thursday 8 AM: Generate pre-call briefs for tomorrow's external meetings.

Advanced (cron):

# Every Tue + Thu at 2 PM
0 14 * * 2,4

# 1st and 15th at 9 AM
0 9 1,15 * *

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

# Last business day of every month at 11:59 PM
59 23 L * 1-5

Triggers

Inbox-driven (often easier via Inbox routing rules):

New email from VIP → notify owning rep
Reply classified as “Hot Lead” → auto-draft fast follow-up
“Meeting Request” → propose calendar slots
“Unsubscribe” → propagate to all campaigns + suppression list

CRM-driven:

New CRM contact → enrichment + ICP scoring + auto-add to list
Account stage → “negotiation” → generate stakeholder map, push to Slack
Signal Agent surfaces a new lead → auto-draft personalized first touch

External-app-driven:

App	Trigger	Use
Gmail / Outlook	New email matching pattern	Inbound deal triage
Calendar	Event created / starting soon	Pre-call brief
Salesforce / HubSpot	Deal stage change	”Closed Won” → onboarding
Slack	`@komo` mention or keyword	Conversational invocation
Notion	Page edited / row added	New ICP → kick off list build
GitHub / Linear	Issue/PR opened	Engineering update for an account
Stripe	Payment, subscription change	Customer success follow-up
Fireflies / Granola	Transcript ready	Auto-summarize → account timeline

…plus 100+ more apps.

High-leverage patterns

Morning pipeline digest

Playbook: Weekly pipeline review
Schedule: Every Monday 7 AM
Output:   Digest emailed to rep + posted to #sales-pipeline

Signal-to-touch

Playbook: Signal-to-touch (draft 2-step outreach)
Trigger:  Signal Agent surfaces a new ICP-matched lead
Output:   Drafts queued in the campaign; Slack DM if high-fit

Pre-call brief

Playbook: Pre-call brief
Trigger:  Calendar event with external attendee, 12h before
Output:   Brief in inbox at meeting start - 12h

Closed-won onboarding

Playbook: Customer onboarding kickoff
Trigger:  Deal stage → "Closed Won"
Output:   Linear tasks, kickoff email, welcome Slack channel, Stripe record

Renewal risk watch

Playbook: Renewal risk scan
Schedule: Monday 7 AM, scoped to accounts renewing in 90 days
Output:   Watchlist emailed to CS team

Setting up a schedule

Open the playbook

Edit the playbook to automate.

Schedules tab

Right-side panel.

Pick type

Quick, Recurring, One-time, or Advanced (cron).

Configure

Frequency, timezone, name.

Test first

Run manually before enabling.

Enable

Toggle on.

Setting up a trigger

Triggers tab

Inside the playbook.

Pick the app

Connected apps show a green badge; others prompt for auth.

Pick the event

e.g. Gmail “new email received,” Slack “keyword mentioned.”

Configure filters

Narrow with from:, subject:, channel, etc. Without filters the trigger fires on every event — too noisy.

Set a cooldown

e.g. max once per 30 min, to prevent runaway loops.

Test + enable

Use Test trigger to simulate, then save.

Managing

Every schedule/trigger appears in the playbook’s right panel. Pause/resume, Edit, View runs, Delete.

Tips

Always test manually before scheduling. A broken daily schedule is harder to catch than a broken one-off.

Use filters aggressively. “New Gmail email” without filters fires on every email.

Combine schedules with triggers — one playbook can be daily + on-demand from Slack.

Time triggers in your audience’s timezone. A 7 AM digest in their inbox, not yours.

FAQ

What happens if a scheduled task fails? Komo retries with exponential backoff. Failed runs logged in History. Configure a Slack DM for critical playbooks. Multiple schedules + triggers on one playbook? Yes — common pattern: daily schedule + on-demand Slack trigger. Timezone? Defaults to your account timezone, overridable per-schedule. DST automatic. How many schedules/triggers can I have? Depends on plan. Contact sales for higher limits.

Turn any playbook into an autonomous workflow. Pick the motion you run every Monday and ask: what would make this trigger itself?

Get started

Sales CRM

Agents & Playbooks

Integrations

API & MCP

Schedules & Triggers

Schedule vs. trigger

Schedules

Triggers

High-leverage patterns

Setting up a schedule

Setting up a trigger

Managing

Tips

FAQ

​Schedule vs. trigger

​Schedules

​Triggers

​High-leverage patterns

​Setting up a schedule

​Setting up a trigger

​Managing

​Tips

​FAQ

Schedule vs. trigger

Schedules

Triggers

High-leverage patterns

Setting up a schedule

Setting up a trigger

Managing

Tips

FAQ