Workflow Examples
Module:
operations:agents| Role: Any member | Licence: Pro+
Real-world examples of deploying agent teams via Eve. Each example follows the same loop:
1. Identify the workflow problem
2. Design agent team (which LANES patterns, what tools, what schedule)
3. Create the team and agents via Eve chat
4. Agents run on schedule, deliver output to users
5. Iterate on prompts based on results
No code is written. Everything is created dynamically via create_agent_team and create_agent.
Example 1: Content Pipeline
Problem: The CEO needs a weekly blog but doesn't have time to scan industry news, pick a topic, and draft an outline from scratch every week.
Solution: Three agents working as a pipeline — one scans, one drafts, one archives.
Team Design
| Agent | Pattern | Tools | Schedule | Delivery |
|---|---|---|---|---|
| Scout | Explorer | websearch | Monday 7am | Slack DM + email |
| Analyst | Analyst | websearch | Tuesday 9am | Slack DM + email |
| Librarian | Librarian | auto-provisioned vault | Friday 10am |
Deployment Steps
Step 1: Create the team
Create an agent team called [team_id] with name "[Team Name]"
and description "[what this team does]"
Step 2: Create each agent
Create an agent with these settings:
agent_id: [id]
name: [Name]
pattern: [lanes_pattern]
tool_groups: ["websearch"]
triggers: [{"type": "cron", "schedule": "every monday at 07:00 UTC", "delivery": ["slack_dm", "email"]}]
prompt: [your prompt here]
Step 3: Add agents to the team
Add [agent_1], [agent_2], and [agent_3] to the [team_id] agent team.
How It Works
- Monday: Scout scans the web and delivers a ranked topic list via Slack DM and email
- Tuesday: Analyst picks the best topic, drafts an outline, delivers via Slack DM and email
- Wednesday-Thursday: Human drafts the blog using the outline (with Claude as copilot)
- Friday: Librarian sends a weekly digest of everything stored in the vault
The Librarian auto-provisions vault tools (query, store, delete) when created with pattern: librarian. Other agents or the user can store content in the vault via Eve.
Example 2: Executive Meeting Support
Problem: ExCo meetings lack structured agendas, decisions aren't tracked, and action items slip.
Solution: Three agents — one preps agendas, one stores decisions, one chases overdue actions.
Team Design
| Agent | Pattern | Schedule | Delivery | Visibility |
|---|---|---|---|---|
| Prep | Analyst | Thursday 8am | Slack DM + email | restricted (ExCo members) |
| Librarian | Librarian | (no trigger) | — | restricted (ExCo members) |
| Tracker | Steward | Wednesday 9am | Slack DM | restricted (ExCo members) |
Key Design Decisions
Restricted visibility: All agents use visibility: restricted with visible_to listing ExCo member user IDs. Only those users can see or interact with these agents.
No trigger on the Librarian: It's written to after meetings by any ExCo member telling Eve "store these decisions in [librarian_id]". No automated schedule needed.
Tracker reads from Librarian: The Tracker agent queries the Librarian's vault for open actions and flags anything overdue. The Steward pattern is designed for this — monitoring and accountability.
How It Works
- Wednesday: Tracker queries the Librarian for overdue actions, sends a status report via Slack DM
- Thursday: Prep builds the agenda (decisions needed, blockers, updates), delivers via Slack DM + email
- Friday: Meeting happens. Afterward, any ExCo member tells Eve to store decisions and actions in the Librarian
- Repeat
Example 3: Personal Knowledge Vault
Problem: Important ideas, meeting notes, and strategic thinking get lost in email and chat.
Solution: A single private Librarian agent that stores and retrieves anything on demand.
Design
| Agent | Pattern | Visibility | Trigger |
|---|---|---|---|
| Personal Librarian | Librarian | restricted (single user) | none |
Deployment
Create an agent with these settings:
agent_id: [your_id]_librarian
name: [Your] Librarian
pattern: librarian
visibility: restricted
prompt: [your storage/retrieval instructions]
No team needed — this is a standalone personal agent. When visibility: restricted is set without visible_to, it defaults to the creating user only.
Usage
- "Store this: [meeting notes, idea, decision]" — Eve dispatches to your Librarian
- "What did I note about [topic]?" — Librarian searches the vault and returns matches
- "What's in my vault tagged [type]?" — Librarian lists entries by tag
Patterns to Note
| Pattern | When to use |
|---|---|
| Pipeline (Example 1) | Sequential workflow — each agent's output feeds the next |
| Hub-and-spoke (Example 2) | Central Librarian, other agents read/write to it |
| Standalone (Example 3) | Single agent, no team, personal use |
Delivery Channel Reference
| Channel | Requires | Behavior |
|---|---|---|
slack_dm | Workspace Slack integration + user's linked Slack account | DM via bot |
email | User's registered email address | Email via Mailgun |
Both can be used together: "delivery": ["slack_dm", "email"]. If one fails, the other still delivers.
Trigger Schedule Cheat Sheet
All schedules are human-readable strings in UTC. Cron notation is no longer accepted — it was the source of a day-of-week ambiguity that shifted some agents' fire days by one. See parse_schedule in ai/agents/base.py for the format spec.
| Schedule | Meaning |
|---|---|
every monday at 07:00 UTC | Monday at 07:00 UTC |
every tuesday at 09:00 UTC | Tuesday at 09:00 UTC |
every thursday at 08:00 UTC | Thursday at 08:00 UTC |
daily at 06:00 UTC | Every day at 06:00 UTC |
every friday at 10:00 UTC | Friday at 10:00 UTC |
daily at 04:00 UTC | Every day at 04:00 UTC (background processing) |
every weekday at 06:00 UTC | Monday through Friday at 06:00 UTC |