Workflow playbooks
Start with a process your team already repeats. Each guide shows the short request, the graph Fleet should propose, one later change, and the cases to test. You can use the request in any MCP-connected AI assistant.
Before you start
- Choose the Fleet workspace and the source files or connected systems.
- Name the person or role that can approve the final action.
- Ask to see the proposed graph before saving it.
You need a manager or admin role to save a workflow. A connected worker is required when a run reads private files or connected systems.
Choose a starting point
Customer onboarding →
Turn a completed intake form into a reviewed onboarding plan and welcome email.
Intake form → Draft plan → Review → Approval → Send
Meeting follow-up →
Turn meeting notes into clear decisions and action items, then send them to the attendees.
Notes → Decisions and actions → Review → Email
Expense approval →
Check an expense request for missing details, route it to a manager, and notify the employee.
Request → Check details → Approval → Notify
Use the guides with your own assistant
- 1. Replace the placeholders. Use your workspace, sources, roles, email addresses, and thresholds.
- 2. Inspect the interpretation. Confirm the proposed steps, routes, retry limits, and approval points.
- 3. Save, then test. Run one ordinary case and every decision path before relying on the workflow.
Need the connection and editing basics?
Read Build workflows by talking to your AI assistant for the MCP endpoint, permissions, revision behavior, and examples of later changes.