Start the day with the signal, not the overnight noise.
Review overnight incidents, group recurring signals, check the approved runbook, and deliver a source-linked morning handover.
How this composition works
This workflow wakes before the team, gathers overnight operational evidence, separates repeated patterns from isolated alerts, and prepares a concise brief. Routine reporting can run automatically, while paging an owner or proposing a production change remains a human decision.
Collect overnight evidence
Read new incidents, errors, and service signals since the previous handover.
Check service context
Compare the signal with edge and availability context before drawing a conclusion.
Ground the response
Link recommendations to the approved operational runbook.
Deliver or escalate
Post the routine brief and pause for approval when an owner must be paged.
Connected systems
These are the real product connectors composed for this example, each scoped to the credential permissions your workspace approves.
Sentry
Investigate errors, traces, releases, and project health in Sentry.
Explore connectorCloudflare Developer Platform
Manage Cloudflare accounts and KV storage namespaces, and list Workers.
Explore connectorSlack
Read channels and messages, post messages, and upload files as your Slack bot.
Explore connectorNotion
Read, search, and update Notion pages and databases.
Explore connectorOptional skills
Where relevant, skills add reusable method and verification. The connectors and agent instructions remain the primary building blocks.
Try asking
More examples for Operations
Build a governed workflow like morning operations brief.
Tell us what your team repeats today. We will map the systems, approval boundaries, and first governed run with you.