> ## Documentation Index > Fetch the complete documentation index at: https://felix.so/docs/llms.txt > Use this file to discover all available pages before exploring further. # Building > Felix turns a plain-language description of your process into a workflow — through a conversation. Building in Felix follows a simple flow: you describe your process in the **Chat**, Felix builds it, you **Preview** the steps, **Run** it to test, then **Share** it with your team. You don't need to prepare anything before you start. A rough description is enough to begin. ## The building flow **Chat → Preview → Run → Share** | Stage | What happens | | ----------- | ------------------------------------------------------------------------------------------------------------------ | | **Chat** | You describe your process. Felix asks follow-up questions, generates the steps, and writes the code automatically. | | **Preview** | You review the generated steps before running anything. | | **Run** | You execute the workflow and review the output and logs. | | **Share** | You share the workflow with others on your team. | ## What you need to get started * **A process to automate** — anything repetitive, document-heavy, or rules-based works well * **A Felix account** — sign in at [app.felix.so](https://app.felix.so) * **Your connectors** — if your workflow needs an external service, connect it in advance or when Felix prompts you mid-build That's it. No flowcharts, no technical specs, no code. ## What makes a good workflow Felix works best on processes that: * Happen repeatedly on the same kind of input * Follow consistent rules or logic * Involve documents, data, or structured information * Currently depend on someone being available to do them manually **Good candidates:** * Extracting key clauses from batches of contracts * Screening new insurance applications against underwriting criteria * Pulling data from a regulatory database and flagging changes * Generating a compliance report from multiple data sources **Less suited to Felix:** * One-off tasks with no repeating structure * Processes that require real-time conversation or open-ended judgement at every step ## Human Checkpoints You stay in control at every stage. At any point in a workflow, you can add a **Human Checkpoint** — a pause that waits for your approval or input before execution continues. Use Human Checkpoints before any step that sends, publishes, deletes, or makes a decision you want to review first. See [Human Checkpoints](/docs/workflows/human-checkpoints) for a full guide. ## Tips * **Start with one step.** Get it working, then add more. * **Be specific about outputs.** Tell Felix what format you need — a table, a CSV, a document, a Slack message. * **Use `@mentions`** to reference connectors explicitly: `@Slack`, `@GoogleDrive`, `@OpenAI`. * **Add a Human Checkpoint** before any irreversible action. Describe your process Review before running Control where execution pauses