Windmill automation platform for workflows and internal tools
Windmill automation platform for scripted workflows and internal tools, with setup from a Sydney AI agency.
Updated 2026-07-01
What Windmill is
The Windmill automation platform turns scripts into workflows and internal apps. A team writes the logic in code, and Windmill runs it on a schedule or when an event occurs. Staff can then start the job from a web interface, check the results and review the run history. The platform can be self-hosted, so a business decides where the software and its data run. For a small business, the value usually lies in gathering recurring jobs into one place, many of which now live in spreadsheets, shared inboxes and scripts that only one person understands. Typical examples include moving records between systems, sending reminders, preparing reports and routing approvals. Windmill suits teams comfortable reading and changing code, or teams with someone who is. It sits alongside existing software rather than replacing it. MILabs, a Sydney agency, helps owners and team leads decide where Windmill belongs, and delivers the work remotely for clients outside Sydney.
Windmill in plain language
Windmill is a developer-oriented platform that lets a team run code as dependable background jobs and simple internal tools. Its basic unit is a script, which can be written in several languages and kept under version control like any other source file. A script can run by hand, on a timetable, or in response to a web request, and each run leaves a record of its inputs, outputs and any errors. Scripts can be chained into flows, so one step's result becomes the next step's input. The same logic can also be wrapped in a form, letting a non-technical colleague start it without touching the code.
The idea behind the platform is that much of ordinary office work already runs on scripts, even if nobody calls them that. A spreadsheet macro, a cron job on an old server, or a forwarding rule in an inbox each performs a small task on a trigger. Windmill brings those tasks into one place where they can be monitored, secured and handed over. Because it can be self-hosted, the organisation decides which server holds the platform and where its credentials are kept.
What businesses use it for
- Moving records between a CRM, accounting software and other systems on a schedule
- Sending appointment reminders and payment follow-ups without manual copying
- Running nightly reports that pull figures from several sources into one view
- Routing approvals and enquiries to the right person with a visible run history
- Replacing single-person scripts with shared internal tools that staff can run safely
Who it suits
- Owners with a technical team member who is comfortable writing and reviewing code
- Businesses that already run recurring jobs from scripts or spreadsheets and want them shared
- Teams that want to self-host their automation and keep data on infrastructure they choose
How MILabs sets it up
MILabs starts with a conversation with the owner or team lead about which jobs matter most and who will use the tools. Together we agree the hosting arrangement, including whether Windmill runs in a self-hosted environment the business controls, and confirm the plan that fits. We then connect the systems the business uses, such as its CRM, accounting software, inboxes and spreadsheets, using the access each system provides. Each script and app is limited to the people and roles that need it, and sensitive credentials are kept in the platform's secrets rather than written into individual scripts. Before handover we agree who looks after the platform after launch, who receives alerts when a run fails, and how changes are requested. The business keeps its data and accounts throughout.
Builds it fits
Industries it fits
Windmill in practice
In a business that runs Windmill well, the work tends to look less like one large project and more like a set of small, named jobs with clear owners. Picture a trades business where the office manager relies on a booking calendar, a job sheet and a shared mailbox. A scheduled script can read the calendar each evening, check which jobs for the next day lack a confirmed time, and prepare customer messages. A second script runs when a new enquiry arrives, pulls out the address and service type, and creates a CRM record. Each job has its own input fields, so a staff member can rerun it with a different date without editing any code.
Inside the business, the platform usually sits behind the scenes. Most staff never open the script editor. They see a short form, press run, and check the result. The developer or technical team member keeps the scripts in version control, reviews changes before they go live, and watches the run history for failures. When a run fails, the alert goes to the person named at handover, who decides whether to fix the script, correct the source data, or pause the schedule until the problem is understood.
Frequently asked questions
- Can Windmill connect to the software I already use?
- Yes. Windmill runs scripts that call APIs and databases, so it can reach most software that offers a documented interface. Common examples include accounting packages, CRMs, booking tools and shared spreadsheets. MILabs works through each connection with you, and where a system offers no usable interface we say so and suggest another route. Credentials are stored as platform secrets, and access stays limited to what each job needs.
- How does Windmill compare with other tools for the same job?
- Zapier, Make and n8n also automate work between apps. Those tools often favour visual builders that non-developers can edit. Windmill suits teams that want their logic in reviewable code, and it can be self-hosted. Retool is closer when the main need is an internal interface on top of existing data. The right choice depends on who will maintain the work, so MILabs compares options with the owner before recommending one.
- How do I get my team to use Windmill?
- Start with one job people find tedious, such as chasing unpaid invoices or copying enquiries into a CRM. Build it with the people who will use it, then run a walkthrough showing where to start and how to read the run history. Keep the tools few at first, and name one person to review failed runs. MILabs can run that walkthrough and agree the support arrangement before handover, so everyone knows who to ask.
- Can I self-host Windmill?
- Yes. Windmill can be self-hosted, so a business decides where the platform and its data run, which suits organisations with strict data handling needs. Self-hosting also puts updates, backups and access control in the hands of whoever runs the server. MILabs confirms that arrangement with the owner before setup and agrees who maintains it afterward. Clients elsewhere are supported the same way, with work delivered remotely outside Sydney.
- Which builds work well with Windmill?
- Windmill suits builds that run on a schedule or respond to events, where the logic is clear and repeatable. Good examples include invoice chasing, lead routing, CRM data entry and appointment reminders. Accounting-to-CRM syncs and daily briefings also fit well. Builds that depend on judgement across many unstructured documents usually need a different approach or a separate AI component. MILabs reviews the process first and recommends the build that matches it.
