Appearance
Use Cases
Concrete, end-to-end recipes — not feature lists. Each combines several connectors with the agent loop, scheduled tasks, and channels into a working pattern you can stand up in a day. Both the Web UI and the REST API path are documented step-by-step, with screenshots, curl examples, and worked Rego policies.
Recipe catalog
01 · DevOps
CI/CD intelligence
Builds & deploys become a queryable feed in Slack.
Read recipe →
02 · DevOps
Automated code review
Claude Code reviews PRs in a CIAB sandbox.
Read recipe →
03 · SRE
Incident response
Pages get triaged with metrics & cluster context.
Read recipe →
04 · Knowledge
Cited Q&A
Ask the company. Answers cited back to source.
Read recipe →
05 · GTM
Customer success
CRM + call recap surface churn risk early.
Read recipe →
06 · Security
Security audit
Quarterly compliance evidence pulled and archived.
Read recipe →
07 · Data
Data ops
Schedule queries · spot anomalies · alert on breach.
Read recipe →
08 · Platform
Platform engineering
Self-service infra ops — deploy, scale, debug from Slack.
Read recipe →
09 · Security
CVE remediation
Auto-patch CVEs across repos with policy-gated PRs.
Read recipe →
10 · Finance
FinOps cost watch
Spot cost spikes · attribute to teams · suggest fixes.
Read recipe →
11 · Reporting
Executive reporting
Roll up metrics from N tools into a weekly exec brief.
Read recipe →
12 · Platform
Developer self-service
Spin up envs · rotate secrets · restart services from chat.
Read recipe →
13 · SRE
Observability Q&A
Ask the dashboards. Get rendered panels and cited metrics back.
Read recipe →
14 · Finance
Conversational FP&A
Ask budget, forecast, and scenario questions across ERP, HRIS, spend, and banking — every figure cited.
Read recipe →
15 · Marketing
Marketing content generation
Drop assets + a brief, get scripts, voiceover, and rendered videos. Daily proactive content suggestions from the graph.
Read recipe →
Adding a new recipe
All recipes are defined in docs/.vitepress/data/recipes.ts. To add one, append an entry to the recipes array and create a matching docs/use-cases/<slug>.md page. The catalog above and the comparison table below render automatically.
At-a-glance comparison
| # | Recipe | Domain | Connectors | Trigger | Outbound |
|---|---|---|---|---|---|
| 01 | CI/CD intelligence | DevOps | GitHub · Jenkins · Vercel | Webhook + cron | Slack |
| 02 | Automated code review | DevOps | GitHub · CIAB (Claude Code) | GitHub PR webhook | PR comment + Slack |
| 03 | Incident response | SRE | Grafana · Kubernetes · AWS | Grafana alert | Slack #oncall |
| 04 | Cited Q&A | Knowledge | Google Workspace · Slack · Read.ai | Chat / cron | Cited answers in chat |
| 05 | Customer success | GTM | HubSpot · Read.ai · Slack | Cron weekly | Slack #cs-leads |
| 06 | Security audit | Security | AWS · GitHub · Agentcy audit log | Cron quarterly | Markdown report + Slack |
| 07 | Data ops | Data | SQL · MongoDB · S3 | Cron every 2h | Slack (only on anomaly) |
| 08 | Platform engineering | Platform | Kubernetes · GitHub · Grafana | Slack mention | Slack thread |
| 09 | CVE remediation | Security | GitHub · NVD/OSV CVE feed · Kubernetes | CVE feed + cron daily | PR per repo + Slack #security |
| 10 | FinOps cost watch | Finance | AWS Cost Explorer · GCP Billing · Kubernetes | Cron daily + spike webhook | Slack #finops + weekly digest |
| 11 | Executive reporting | Reporting | GitHub · HubSpot · Grafana · Stripe | Cron Monday 06:00 | PDF + email + Slack |
| 12 | Developer self-service | Platform | GitHub · Kubernetes · AWS · Vault | Slack slash command | Slack thread + audit log |
| 13 | Observability Q&A | SRE | Grafana · Kubernetes · Loki/Prometheus | Chat / Slack mention | Slack thread with rendered panels |
| 14 | Conversational FP&A | Finance | NetSuite · HiBob · Ramp · Moss · Procurify · Alta Via · Excel | Chat / Slack mention | Slack / dashboard / PDF scenario export |
| 15 | Marketing content generation | Marketing | Figma · Remotion · ElevenLabs · Runway · CIAB | Chat upload / cron daily | MP4 + scripts + social copy |
What every recipe gives you
A consistent shape so you can scan one and be productive in 30 minutes:
- Hero diagram — the flow at a glance, with vendor icons.
- At-a-glance — a 3-line summary of what the agent is doing.
- Stack — exactly which connectors and features are in play.
- What you'll build — narrative of the end-to-end flow.
- Prerequisites — tokens, optional features (Workers, Channels), realm setup.
- Step-by-step — every step has both Web UI and REST API tabs. Pick your lane.
- Worked example — a real Task definition + Rego policy you can copy-paste.
- What good looks like — sample chat transcript or task-run output.
- Variations — 2–3 ways to bend the recipe to your context.
- Troubleshooting — most common failure modes with fixes.
- Next steps — where to go for more depth.
Patterns these recipes share
Three patterns appear across all recipes — worth understanding once:
- Triggers, not polling. Webhooks (GitHub, Grafana, HubSpot, CVE feeds) and crons (Tasks) drive everything. Agentcy doesn't poll your tools.
- The agent uses the catalog, not a hard-coded tool list. Every recipe relies on the agent calling
search_connector_toolsto discover the right tool for the moment. See Agent Loop. - Memory + suppression for high-frequency alerts. Recipes that fire often (Data Ops, SRE, FinOps) use Memory to track what's already been alerted on so the channel doesn't get noisy.
Coming soon
Recipes we're working on, buildable on the same primitives:
| Domain | Sketch | Description |
|---|---|---|
| Sales ops | Lead enrichment | Inbound lead → enrich (Clearbit / People) → score → route to AE in Slack |
| Marketing | Campaign perf | Watch funnel anomalies → pull copy from brand-voice docs → suggest revisions |
| Recruiting | Hire-loop nominator | New PR author detected → enrich career graph → suggest team to nominate |
| Finance | Month-end close | Pull Stripe + ledger + AR aging → draft narrative → flag exceptions |
| CIAB | Cursor / Codex packaging | Sandbox image with Cursor or Codex CLI baked in (today: only Claude Code) |
| Protocol | Inbound MCP server | Expose Agentcy itself as an MCP server so external agents can call us back |
If you want one of these, open an issue or write the first draft and PR it.
Vendor logos
Vendor names and logos are trademarks of their respective owners; used here under fair editorial use to identify integrations.