Skip to main content
You don’t need to write code or map out logic before you start. Felix takes a plain-language description of your process — however rough — identifies what’s missing, and asks targeted questions until it has enough to build. Once built, the workflow runs end to end. It can fetch data, process documents, call external services, pause for human review, and produce structured outputs. You don’t prompt it each time. It runs on its own.

​
How it works

1

Describe your process

Type what you want to automate in plain language. No templates, no flowcharts required.
2

Felix fills the gaps

Felix identifies missing details and asks follow-up questions — so the workflow it builds accurately reflects how your process actually works.
3

Felix builds the workflow

Felix writes the underlying code and wires up each step automatically.
4

Run it

Trigger the run manually, on a schedule, or across a large dataset. Felix handles execution and logs every step.

​
Where Felix fits

Most automation tools fall into one of two categories: Node-based automations (Zapier, n8n, Make) are reusable and consistent, but rigid. They connect pre-built actions in a fixed sequence. When a process has complexity, edge cases, or requires any judgement, they break. Probabilistic agents (LLM-driven, autonomous) are flexible and capable, but unpredictable. They make AI decisions at runtime on every execution. The same input can produce a different output each time — which is unacceptable in legal, insurance, and finance. Felix sits between the two.
Node-based automationsFelixProbabilistic agents
ExamplesZapier, n8n, Make—LLM agents
Reusable✓✓—
Consistent✓✓—
Flexible—✓✓
Handles complexity—✓✓
Deterministic✓✓—
Auditable—✓—
Felix combines the reusability and consistency of node-based automations with the reasoning capability and flexibility of agents — without the rigidity of one or the unpredictability of the other.

​
What Felix is built for

Felix is purpose-built for legal, insurance, and finance — environments where processes are complex, documentation-heavy, and often dependent on institutional knowledge spread across people and systems. Felix captures that knowledge and embeds it into workflows that no longer depend on who is available to run them.
Felix is not a general-purpose AI tool. It is operational infrastructure for professional services teams.

​
Core concepts

  • Workflow — The end-to-end automated process Felix builds and runs
  • Step — A single unit of work within a workflow, defined in plain language
  • Run — A single execution of a workflow
  • Connector — A connected third-party service, referenced using @mentions
  • Human Checkpoint — A pause in a workflow where you approve or input before execution continues
  • Batch run — Processing multiple items through a workflow in one run
  • Scheduled run — A workflow triggered automatically on a time-based schedule

Quickstart

Build your first workflow in a few minutes

Building

How Felix builds workflows

Connectors

Connect your tools