Skip to content

field notes · build

Workflow automation

Workflow automationAn isometric drawing of a workflow as a conveyor belt. At the front left a form on a stand; behind it a trigger hopper drops one data card onto the belt. The card passes three step stations: a CRM cabinet that looks up the customer, an accounting ledger with a stamp that writes to the books, and a bell that tells the team. A retry loop arches over the accounting step, and at the end of the belt a printer logs every run. At the front right an alert lamp, the job's owner and a runbook on a hook. Run sends the card all the way through. With break a step on, accounting fails, the card loops back over the retry loop, fails again, the lamp lights and the owner is alerted. Fix and replay has the owner use the runbook and finishes the same run without typing anything again.typed in onceteamledgercrmlogretrytriggerrunbookform1234567

A form comes in on the left, three steps run along the belt and every run is logged. Press run.

A workflow for each job your team keeps doing by hand.

Book a free first callEstimate the cost

In short

Workflow automation is when software does repeated admin that people used to do, like moving data between systems, routing leads or building reports. Zenoware is a small studio in Auckland. We build these workflows in Zapier, Make, n8n or custom Laravel, with retries, logging and alerts, and leave your team a runbook. It suits any business losing hours a week to copy and paste. The first call is free.

What you get

  • Data typed in once and passed along from there

  • Failures logged and sent to whoever owns the job

  • Zapier, Make, n8n or Laravel, depending on the job

How it runs

  1. 01

    Map the process

    First we sit with the person who does it now.

  2. 02

    Pick the platform

    We pick the platform once we know the data and the rules.

  3. 03

    Build and test

    Each workflow is built with retries and tested on real examples.

  4. 04

    Hand over

    Your team gets alerts, a runbook and a walkthrough.

Who you'll work with

Brush sketch of JP Caparas

JP Caparas

Founder and lead engineer

Thirteen years of principal engineering, including development lead at Public Trust. OpenAI Codex and Devin ambassador in New Zealand. You talk to the person who writes the code.

About the team

Questions

What is workflow automation?

Software doing a repeatable process for you. Something happens (a form is sent, an order lands, it's 9am on Monday) and the workflow runs the steps a person used to do, like updating the CRM or emailing the customer. Good ones also log what they did and complain when they fail.

What is the difference between n8n, Zapier and Make?

Zapier connects to more apps than anything else and is the fastest way to wire SaaS tools together. Make (it used to be Integromat) is visual and copes well with branching, loops and bulk data. n8n can run on your own server, which matters when the data's sensitive or you need custom code.

When should I build a custom workflow instead of using Zapier?

Once the rules are specific to how your business works (multi-step approvals, audit trails, odd edge cases), no-code tools start to strain. Per-task pricing also adds up at volume. A Laravel workflow lives in your own app, so you own the code and nobody bills you per run.

Can n8n be self-hosted?

It can. n8n will run on a server or cloud account you control, which is why we lean on it when the data is the sort you'd rather not hand to a third party, like customer or finance records.

Which business processes are worth automating first?

Anything frequent, rule-based and dull. Leads landing in a CRM, a database and a spreadsheet that should match, data pulled out of PDFs, order updates, a weekly report someone builds by hand, support tickets that need routing.

You might also need

Tell us what isn't working.

The first call is free, and we'll tell you straight whether we're the right people for it.

Start a project