Code

You don’t write or edit code directly. This page is for anyone who wants to understand what Felix generates and why — useful for IT and ops teams reviewing workflows before deployment.

​

How Felix generates code

When you describe a step, Felix generates a TypeScript code block that executes your instruction. The code:

• Calls the relevant connector APIs using your authenticated credentials
• Handles errors and retries automatically
• Passes outputs to the next step using the variable names Felix assigns
• Runs the same way every time — deterministically

Felix applies AI reasoning to generate the code once. After that, the code runs as structured logic — not as an AI making decisions at runtime.

​

Viewing the code

To inspect the code for any step:

1. Open the workflow in Preview or from your dashboard
2. Click on the step you want to inspect
3. Select View code

The code view shows the full TypeScript block Felix generated for that step. You can read it, copy it, or share it with a technical reviewer.

​

Editing the code

Felix does not support direct code editing. To change what a step does, update its description and Felix regenerates the code automatically.

​

Audit trail

Every run produces a full log of what each step’s code received, what it did, and what it produced. This log is available in the run history for every workflow. See Outputs for more on run logs and output formats.

​

Tips

• Review the code before deploying high-stakes workflows. For workflows that write, send, or delete data, a code review adds a useful layer of verification.
• Use Human Checkpoints as a lighter alternative. If you want oversight without reviewing code, a Human Checkpoint pauses execution for your review at the relevant step.
• Share the code view with your IT team. If your organisation requires technical sign-off before deploying automated processes, the code view gives them exactly what they need.