Build workflows by talking to your AI assistant
Connect Fleet to an AI assistant that supports MCP, then describe the process you want in ordinary language. Your assistant can propose the graph, validate it, save it, and make later changes without rebuilding the workflow by hand.
What you need
- A Fleet workspace and access to the files or integrations the workflow will use.
- An AI assistant that supports remote MCP servers and Fleet's OAuth sign-in.
- A Fleet manager or admin role to create or update saved workflows.
The Fleet plugin configures the connection automatically where it is available. Otherwise, add https://app.fleetctl.ai/mcpas a remote HTTP MCP server in your client and sign in when prompted. Start a new conversation so the client discovers Fleet's tools. You can design and validate a workflow before a worker is connected; a run needs a connected worker to reach private files or connected systems.
Start with the result you want
The same workflow model works for marketing, operations, customer success, policy, and software delivery. Name the inputs, the work, the checks, the person who decides, and the final destination. For complete setup examples, see the customer onboarding, meeting follow-up, and expense approval playbooks.
Marketing example
Review and approve campaign content
Turn a campaign brief into reviewed, approved content while keeping the launch process consistent.
Ask your assistant
Create a workflow named “Launch campaign content” for acme/company-knowledge. Start it manually. Draft campaign copy from the brief and approved brand and product material. Have Brand and Compliance review it, with up to two revisions when either finds a problem. Require marketing lead approval, then publish and notify the launch team. Show me the proposed workflow before saving it.
Proposed graph
Manual start
↓
Draft content ←──────────────┐
↓ │
Brand review ── changes ─────┤
↓ approved │ retry 2
Compliance review ─ changes ─┘
↓ approved
Marketing approval
↓
Publish → NotifyChange it later
Add an Accessibility review between Compliance and Marketing approval. Have Draft create email and landing-page variants, with a citation for every product claim. Keep the manual start, two-revision limit, approval, publish, and notification steps. Show me the change before saving it.
Operations example
Deliver a Monday leadership brief
Give the assistant the sources, writing instructions, schedule, and sign-off point for a recurring brief.
Ask your assistant
Create a workflow named “Monday leadership brief” for acme/company-knowledge. Every Monday at 9:00 AM UTC, gather operations/**/*.md and write a brief that leads with business risks. Name the owner and decision needed for each risk, then cover progress. Require leadership approval. Show me the proposed workflow before saving it.
Proposed graph
Every Monday at 9:00 AM UTC
↓
Gather notes
↓
Write risk brief
↓
Approve briefChange it later
Move the Monday leadership brief to 8:30 AM UTC. Add sections for work blocked more than three days and customer commitments due in the next two weeks. Keep the workspace, source documents, and approval step. Show me the change before saving it.
What happens when you make a change
Your assistant reads the current workflow and revision, applies the requested change, validates the complete replacement, and saves a new revision. A stale update fails if someone else edited the workflow first. Saving a definition does not start a run.
You can change instructions, steps, connections, schedules, review routes, retry limits, approvals, sources, roles, inputs, and outputs in the same way.
Work safely
- Inspect first. Ask the assistant to show and validate the proposed graph before it saves anything.
- Set boundaries. Say which sources, approvals, steps, and limits must remain unchanged.
- Save deliberately. Creation and editing require a manager or admin role, and saving never starts a run.
- Verify the result. Inspect the trigger, ordered steps, routes, approval gates, revision, and warnings in the assistant or in Fleet.