Your First Mission
A mission is one run of a workflow. This walkthrough takes you from picking a workflow to reading its results.
Before you start
- Your project needs at least one workflow. If Missions says Nothing to launch yet, click Create a workflow and follow Designing Workflows — a Trigger node followed by one Agent node is enough.
- You need the project Editor role, or permission to run that workflow.
1. Open Missions
In the left navigation, go to Build → Missions. The page heading is the workflow picker, under Start a Mission.
Missions selects the first workflow for you when it opens. If that workflow has no attributes, it launches straight away. Use a workflow's Run button on Build → Workflows to open Missions without this.
2. Choose a workflow
Click the workflow name and pick the workflow you want to run. Its inputs (attributes) appear underneath.
3. Fill in the inputs
Fill in the fields — for a new workflow this is usually one box labelled Enter your request. Drop-downs, checkboxes and option buttons appear below the main box.
Be specific. "Compare the three largest AI customer-service platforms in the ANZ market on price and data residency" gets better results than "AI stuff".
4. Launch
Click the launch button — Launch Mission, or the workflow's own button such as Go. You can also press Enter in the text box (Shift+Enter adds a new line).
The execution canvas opens.
5. Watch it run
- Nodes change from Waiting to Running to Completed. The canvas follows whichever node is running.
- Agent and team nodes show what they're doing and the tools they call.
- The progress bar at the top fills as nodes finish. Live in the header means updates are streaming.
- The side rail's Stages view lists each step; Timeline shows a running log.
Click View live output on a running node to read its output as it's produced, or Open in Chat to read the agent's full conversation and talk to it.
6. Handle approvals
If a node shows Action Required, the run is waiting for you. Read the request (and the previous node's output), then click Approve to continue or Reject. The same request appears in the Alerts panel (the bell in the header), so you can respond from anywhere in the app. See Using Approval Gates.
7. Review the results
When every node is Completed, expand the last nodes with View output and use Copy output to take the result elsewhere.
To come back later: on Missions, open View all history, find the run, and click View mission. Re-run this mission launches it again with the same inputs.
If something shows Failed, its message says why — see Missions for what each status means.
What just happened
You launched a workflow. FYAI created a mission, started at the workflow's Trigger, ran each node in turn — calling agents, teams and functions, passing each step's output to the next — and recorded every step so you can review it.
Next steps
- Designing Workflows — build your own
- Workflow Examples — common patterns
- Scheduling Workflows — run it automatically
- Agents and Teams — the workers behind each step