Windmill

Agents built in Windmill act in outside systems with stored credentials. The Hub catalogs integration scripts across hundreds of services (Slack, Jira, Gmail, Google Sheets, Postgres, Airtable, OpenAI, Anthropic and more), resource types store the credentials those scripts act with, and any Windmill script can be attached as a tool to an AI agent step, so the agent takes authenticated action in outside systems. AI sessions can also connect external MCP servers as clients.

Sourcehub.windmill.devread 2026-09-23

Windmill is a workflow engine: flows compose scripts in 20-plus languages into multi-step graphs with branches, loops, early stops, retries, error handlers and suspend steps, and AI agent steps run inside those flows with tools, including nested agents configured as tools of another agent.

Sourcewindmill.dev/docs/flows/flow_editorread 2026-09-23

No retrieval structure Windmill maintains over the customer's corpus is documented. Its persistent storage (data tables, DuckLake, object storage, states and resources) holds data the customer's own scripts read and write, which is storage rather than grounding, and any retrieval a customer builds runs through tools or providers they call from a script.

Sourcewindmill.dev/docs/core_concepts/persistent_storage/states_resources_shared_directoryread 2026-09-23

Any flow step can be set to suspend, a durable approval wait built into Windmill, holding the flow until the required number of approval events arrive through generated resume and cancel URLs or the approval page, with forms for the approver to fill in and a timeout.

Sourcewindmill.dev/docs/flows/flow_approvalread 2026-09-23

The plans page states Windmill is SOC 2 Type II compliant, with the report downloadable from the customer portal, and a trust center at trust.windmill.dev, scoped to the Enterprise Edition. On Enterprise, SAML and SCIM authenticate and provision users through the customer's identity provider; SSO is available on every edition (capped at 10 users on the free edition), and developer and operator roles separate who can edit from who can only run. Audit logs record every operation with side effects.

Sourcewindmill.dev/docs/advanced/saml_and_scimread 2026-09-23

Runs are recorded step by step, with an audit record kept apart from them. The Runs page lists past and future jobs with each job's logs, inputs, results and per-step detail for flows, and AI agent steps report their tool calls and token usage. Audit logs capture every operation with side effects and the user responsible, with a configurable retention period on self-hosted instances, and an OpenTelemetry guide exports traces, metrics and logs to the customer's own observability stack.

Sourcewindmill.dev/docs/core_concepts/audit_logsread 2026-09-23

The AI agent step keeps conversation memory the agent reads as context across runs: in auto mode Windmill keeps up to a set number of the most recent messages, in manual mode the caller supplies the history in OpenAI message format, and the docs cover using memory with webhook-triggered runs. No published lifetime or purge path and no first-party surface to review or edit what the agent remembers are documented. States and resources persist small JSON between job executions, which is storage the code reads.

Sourcewindmill.dev/docs/core_concepts/ai_agentsread 2026-09-23

Windmill is open source and self-hosts in the customer's own infrastructure, with documented Docker, Kubernetes (Helm), AWS EKS and ECS and Azure setups, alongside Windmill Cloud and dedicated cloud instances for Enterprise.

Sourcewindmill.dev/docs/advanced/self_hostread 2026-09-23

The Hub publishes a browsable catalog of assets a buyer adopts into a Windmill workspace. It includes ready-made projects that each do a job: a support engine that drafts replies into Gmail, a recruiting app with AI CV screening, a Sentry engine that investigates recurring errors and opens a pull request with the fix, a helpdesk and an uptime monitor. It also holds integration scripts and flows for hundreds of services, pickable from inside the editors, and a Private Hub serves an organization's own approved set.

Sourcehub.windmill.devread 2026-09-23

Work starts on its own from cron schedules, webhooks and HTTP routes, email triggers, WebSocket and Postgres change capture, and from Kafka, NATS, Amazon SQS, MQTT, AMQP, Google Cloud Pub/Sub and Azure triggers, plus native triggers, each starting a script or flow when the event arrives.

Sourcewindmill.dev/docs/triggersread 2026-09-23

The customer chooses the model behind each Windmill AI agent step. Providers include OpenAI, Azure OpenAI, Azure AI Foundry, Anthropic, Mistral, DeepSeek, Google (Gemini), Groq, OpenRouter, Together AI and custom endpoints, with the credentials stored as reusable resources. The model is picked per step, with a reasoning-effort setting for models that support it, and nested agents configure their own provider and model.

Sourcewindmill.dev/docs/core_concepts/ai_agentsread 2026-09-23

Outside callers reach Windmill through a documented REST API with a published OpenAPI specification, the wmill CLI with sync to Git, TypeScript and Python clients, webhook and HTTP route endpoints generated for any script or flow, and an MCP server that exposes a workspace's scripts and flows as tools plus API operations on jobs and other objects.

Sourcewindmill.dev/docs/core_concepts/mcpread 2026-09-23

Customers get an evaluation harness for their agents. AI agent evals attach a dataset of cases (question and expected answer) to a reusable agent, run the agent against every case, score the answers with AI judges or scripts, and keep every run so the next one is compared against it. The docs frame it as answering whether the agent got better after each change.

Sourcewindmill.dev/docs/core_concepts/ai_agent_evalsread 2026-09-23

Windmill hosts the environment browser automation runs in: a worker group installs Chromium on start and takes jobs tagged chromium, and the docs give Playwright and Puppeteer examples for testing and scraping, which a script can expose as a tool to an AI agent step. The browser control comes from those libraries in the customer's own script, and no Windmill API for screenshots, clicks or typing is documented.

Sourcewindmill.dev/docs/advanced/browser_automationread 2026-09-23