Inngest workflow automation for small and mid-sized businesses
How Inngest runs background jobs and multi-step workflows, and how MILabs sets them up for businesses in Sydney and beyond.
Updated 2026-08-20
What Inngest is
Inngest is a platform for running background jobs and multi-step workflows in software. A workflow is a set of steps that run in order, often started by an event such as a new form submission, a payment or a change in a record. Inngest handles the parts that are easy to get wrong when code runs outside a single web request. It keeps track of each step, retries steps that fail, and can wait for a set time or a later event before continuing. Developers write these workflows as functions in their own codebase and send events to them from the applications a business already runs. Inngest is developer-facing software, so it sits in a business's engineering layer rather than in a no-code tool. Inngest runs as a hosted service or in a self-hosted setup, which some organisations choose for control over where their data runs. Teams often pick it when a process must keep working reliably across several systems over longer periods.
Inngest in plain language
Most business software is built around a request: someone clicks a button, a page loads, and the answer returns at once. Many important processes do not fit that pattern. An invoice may need a reminder if it stays unpaid, a booking may need a confirmation only after payment clears, and a supplier feed may arrive at an unpredictable hour. Software handling these cases must remember where it stopped.
External services fail in small ways. A webhook can arrive twice, a payment provider can time out, and an email service can accept a message and then fail to deliver it. A step that sends a message or charges a card should record its outcome before the next step begins, so a retry does not produce a duplicate.
Platforms in this area differ in who writes the logic and where the state lives. Visual builders suit operators who want to change a process themselves. Inngest sits at the other end, expecting the logic to live in code the business owns, with the platform supplying scheduling, retries and a record of each run. The choice resembles the one between a spreadsheet and a database: more responsibility in exchange for behaviour that can be tested and reviewed.
What businesses use it for
- Sending reminder sequences after a quote or invoice goes unanswered, with each step checking the record first.
- Syncing new bookings, customers and payments between a website, a calendar and an accounting system.
- Running nightly jobs that tidy records, produce reports and flag items that need attention.
- Coordinating onboarding tasks across email, documents and internal tools once a new client agrees to start.
- Handling webhooks from payment and form providers so that events are not lost during busy periods.
Who it suits
- Businesses with engineers who already maintain their own software
- Operators whose processes span several systems and must not lose steps
- Teams that want long-running processes to be easy to monitor
How MILabs sets it up
MILabs starts with the owner or team lead to choose the Inngest plan and whether the business wants the hosted service or a self-hosted setup. Next, the team maps the systems the business already uses, such as the website, the accounting software, the booking tool and the email platform, and connects each one to the workflows that need it. Access is set by role, so engineers who build functions can change them while managers read run history and status. Before handover, MILabs agrees with the business who monitors failed runs, who approves changes and how issues are escalated. This shared agreement keeps workflows dependable after the build.
Builds it fits
- Invoice chasing automation
- Quote follow-up automation
- Appointment reminder automation
- Booking confirmation automation
- Payment reminder SMS automation
- Accounting and CRM sync
- Ecommerce and ERP sync
- Calendar and CRM sync
- Booking platform sync
- Client onboarding automation
- Delivery notification automation
- Subscription billing automation
Industries it fits
Inngest in practice
A typical workflow begins with an event nobody had to watch for, such as a customer's reply arriving by email or a cleared payment. The first step looks up the related customer or job, because the event alone rarely holds everything later steps need. Each following step does one thing, like drafting a message or updating a field, and records its outcome so a stopped run can resume.
Waiting is where much of the value sits. An unanswered quote can sit in a waiting state until the customer replies or a calendar date comes due. When the wait ends, the workflow checks the record again, since the customer may have paid in the meantime.
People stay in the loop at defined points. A refund or a message touching a complaint goes to an approver rather than sending automatically. A run that fails after its retries lands on a shared list, which the person the owner nominates reviews on a set routine.
Changes are tested against sample events and reviewed by a second person before reaching live records, so a small edit cannot quietly alter every future enquiry.
Frequently asked questions
- How does MILabs set up Inngest?
- MILabs begins with the owner or team lead to agree on the plan and on whether the business uses the hosted service or a self-hosted setup. Then the team connects the systems the business already runs, such as its website, accounting software and booking tool, so that events from those systems reach the right workflows. Permissions are set by role, and the owner and MILabs agree who monitors failed runs and who approves changes.
- Where does Inngest store data?
- Where data sits depends on the deployment. On the hosted service, the data is held by Inngest on its own infrastructure. When the business self-hosts, the data is kept on servers the business or its provider controls. MILabs records the chosen location in the handover notes so the owner knows which records, event payloads and run history are held where. The owner can then see exactly where each record type is held.
- When is Inngest the wrong choice?
- Inngest is a poor fit when a business wants a no-code tool that staff can change themselves, since its workflows are written as code. If the business has no engineer or contractor to maintain functions, the workflows will fall behind as systems change. In those cases, a simpler platform such as Zapier or Make is often the better starting point, and MILabs will say so during the first conversation.
- Can my team use Inngest without training?
- No. Building and changing workflows takes engineering knowledge, because Inngest is a developer platform. The people who write functions need to be comfortable with code and with the systems the business uses. MILabs writes a short operating guide for each workflow, covering what it does, how to check a run and who to contact when a run fails. That guide lets staff follow the process without reading code.
- Can MILabs build on top of Inngest?
- Yes. Building on Inngest is part of custom development at MILabs, one of its five services. The team can design the functions, connect the events from the business's applications and add steps that call AI models. Each build starts from a written scope agreed with the owner, and the business receives the code, the operating guide and a list of the systems involved. Work outside Sydney is delivered remotely.
