What an output is
An output is the data a step produces after executing. It can be:- A structured dataset — a table, JSON object, or list of records
- A file — a PDF, CSV, or document
- A confirmation — a record that an action was taken (email sent, row written, message posted)
- A variable — a value passed to the next step
How outputs flow between steps
Felix automatically passes each step’s output to the next step that needs it. You don’t need to wire anything manually — describe what data a step should use and Felix handles the connection.Final outputs
The last step in a workflow produces the final output of a run. This is typically:- A file written to a connected service (
@GoogleSheets,@GoogleDrive,@Notion) - A notification sent via a connector (
@Slack,@Gmail) - A document generated and returned in the run view
Run logs
Every run produces a full log. For each step you can see:- What input the step received
- What the step did
- What output it produced
- How long it took
- Any errors or warnings
Downloading outputs
File outputs — CSVs, PDFs, documents — can be downloaded directly from the run view. Outputs written to connected services are available in those services immediately after the run completes.Tips
- Check intermediate outputs when debugging. If your final output is wrong, expand each step’s log to find where the data diverged from what you expected.
- Be specific about what data you’re referencing. “The flagged contracts from step 2” is clearer than “the previous output”.
- Write final outputs to a connected service. Storing results in
@GoogleSheetsor@Notionmakes them accessible to your team without needing access to Felix.
Run
Execute a workflow and read its outputs
Running
Scheduled runs, batch runs, and run history
Human Checkpoints
Review outputs mid-run

