Get Started

What PIILOT does

A product-level overview of PIILOT’s natural-language automation builder.

PIILOT turns natural-language workflow requests into structured automations and agents. It is built for teams that know what manual process they want to improve, but do not want to start by wiring every trigger, branch, action, approval gate, and validation rule by hand.

The app currently centers on Discovery, Workflows, Canvas, Integrations, Approvals, Agents, Logs, Analytics, and Settings. The workflow builder takes a request, produces a graph-shaped workflow draft, validates the structure, simulates the path, enriches the workflow with setup requirements, and saves the result to the workspace.

The PIILOT automation loop

flowchart TD
  A[Describe the manual workflow]
  A --> B[PIILOT extracts intent]
  B --> C[Generate workflow graph]
  C --> D[Validate structure]
  D --> E[Simulate the path]
  E --> F[Compile setup requirements]
  F --> G[Review in Workflows and Canvas]
  G --> H[Connect tools and refine]
  H --> I[Working automation]

The core outcome

A PIILOT workflow is more than a text answer. It includes named workflow metadata, the real underlying need, the stated request, success metrics, nodes, edges, connector contracts, safety gates, validation results, simulation output, setup state, and enrichment data such as variable manifests and human-time estimates.

Primary surfaces

Discovery: where users describe workflows and receive generated automation drafts.
Workflows: where saved automations are listed, reviewed, and opened.
Canvas: where workflow graphs are inspected visually.
Integrations: where connected tools are discovered and authorized through Composio.
Approvals: where risky or gated actions can be routed for review.
Agents: where external MCP clients and exposed PIILOT capabilities are managed.
Logs: where workflow and system activity can be inspected.

Alpha status

PIILOT is an alpha product. The docs describe the intended completed product behavior for the current product direction, while still matching the architecture and concepts present in the codebase.