Skip to content
Call wiki

Can a no-code Claude setup react to external events, or are scheduled tasks the ceiling?

Last updated 2026-08-17 · Confidence: documented — Anthropic’s help center, Claude Code docs, and the routines announcement, read that day; one inferred claim underlined.

Time-based schedules only, hourly at most frequent — event-style triggers exist at the edges (Claude Code routines’ API/GitHub triggers, Slack @-mentions, terminal-bound “channels”), and none fires on “the meeting just ended” out of the box.

What no-code scheduling supports

Section titled “What no-code scheduling supports”

Cowork’s scheduled tasks run “on a recurring basis, or on demand”: cadence options are hourly, daily, weekly, weekdays, or manual — hourly is the minimum interval. They run remotely in the cloud (“even when your computer is asleep”), are in beta on web and mobile for all paid plans, and “each scheduled task runs as its own Cowork session.” Cowork projects carry an Instructions section guiding “how Claude works on all tasks in the project” and support “recurring tasks that are specific to the project” — so the hourly-fresh-session-that-reads-the-instructions pattern is exactly what ships. The docs list no event, webhook, or connector-based trigger; task assignment is always human-initiated or scheduled.

Where event triggers do exist

Section titled “Where event triggers do exist”

Claude Code routines (research preview, April 2026; Pro/Max/Team/Enterprise, 5–25 runs/day by plan) run cloud sessions “on a schedule, from an API call, or in response to an event”: each routine gets its own HTTPS endpoint and auth token, and can subscribe to GitHub repository events. The scheduling docs put routines’ minimum interval at 1 hour; Desktop scheduled tasks and session-scoped /loop go down to 1 minute but need your machine on. Separately, channels (research preview) push external events — chat messages, CI webhooks — into an already-running Claude Code terminal session; that requires an installed plugin and an open session, not a claude.ai project. A Slack message can start a session only via an explicit @Claude mention.

What “the meeting just ended” would take

Section titled “What “the meeting just ended” would take”

No supported trigger fires on it. The realistic bridges: (a) an hourly Cowork scheduled task that checks the calendar/Granola via connectors and acts if a meeting ended — polling, up to an hour late (each run reads connected docs live; see connector-doc-freshness.md); (b) a routine’s API endpoint hit by anything that can send an HTTP POST (a Zapier/Pipedream-style webhook step, or your own script) — event-driven, but the POST-sender is where the setup stops being no-code.

Sources

Section titled “Sources”