app.windmill.dev or self-hosted) through its REST API (<your base URL>/api, described by the OpenAPI spec in the Windmill repository), using an API token. Configview sends only GET requests. It never creates, changes, runs or deletes anything in Windmill.
You will end up with 2 required secrets (WINDMILL_BASE_URL, WINDMILL_TOKEN) and 1 optional secret (WINDMILL_WORKSPACES) in Configview when setup is complete.
Scope of this integration today. Configview answers “who can build and run automations here, and what can they reach”: workspace members and their roles, groups, folders and owners, scripts, flows and schedules (owner, language, cron, enabled), the resources that connect to other systems (name and type only), variables (name and secret flag only), the API tokens of the collector’s own user, HTTP triggers and how callers authenticate, executions per user, instance users, and a 30-day audit log. It does not read script or flow code, resource or variable values, job inputs, outputs or logs, or the arguments of audit events.
What you need
- A Windmill instance and a user who is an admin of the workspaces you want covered
- For instance users and every workspace: a token for an instance superadmin
- The base URL of the instance, with
https
Step 1: Open the Windmill page in Configview
Open Configview in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/windmill
Step 2: Create the token
- In Windmill open Account settings > Tokens and create a token. Give it an expiry. Windmill has no read-only role, so the token can do whatever its user can do; Configview only ever reads. Use a dedicated service-account user that is an admin (workspace admin for the workspace-level data, superadmin only if you want instance users).
- In the Configview tab paste it into
WINDMILL_TOKENunder Credentials and save. - Save the address of your instance as
WINDMILL_BASE_URL, for examplehttps://app.windmill.devorhttps://windmill.example.com. Do not add/api. Configview refuses plainhttp. - Optional: save
WINDMILL_WORKSPACESas a comma-separated list of workspace ids (for exampleprod,staging) to cover only those. Leave it empty to cover every workspace the token can see.
Step 3: Connect and verify
- Click Connect. Configview creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads both secrets, then
/users/whoamiand the workspace list.
- 401. The token is wrong, expired, revoked, or belongs to a different instance.
- 403 or 404. The token’s user cannot read that area. Configview skips that workspace or collector and carries on.
Data Tables
Each table has arun_at column and keeps only the newest run.
Things worth knowing
Owners come from the path. Windmill paths start withu/<user>/ for a personal item or f/<folder>/ for a folder item. Configview derives the owner from that, because the script list has no creator field.
Resources show where automations can reach. A resource is a stored connection (a Postgres database, a Slack workspace, an AWS account). Configview keeps the path and type so you can see which systems are wired in, and whether an OAuth connection has expired. The values, which often hold passwords, are never read even though Windmill’s list returns them.
Tokens are the collector user’s own. Windmill lists only the caller’s tokens, so windmill_tokens shows the tokens of the account Configview uses, not every token in the workspace.
HTTP triggers with no authentication. A trigger whose authentication_method is none can be started by anyone who knows its URL. Configview lists them.
Audit log. The last 30 days, up to 5,000 events per workspace; a warning is printed if the cap is hit. Windmill may limit audit retention on the open-source edition.
Rate limit. Windmill documents no numeric API rate limit. Configview paces itself at 120 requests a minute and waits as long as an HTTP 429 asks.
What isn’t collected
- Script and flow code, steps and arguments, schedule arguments
- Resource and variable values, token values
- HTTP trigger route paths and static asset settings
- Job inputs, results and logs (only per-user execution counts)
- The arguments of audit events