A paper system and 28 hours a week
When John Cabanela became the interim bookkeeper at Theatre Passe Muraille in April 2024, he inherited a paper-heavy bookkeeping system built around QuickBooks Desktop. "I was not about that at all," he says.
He began moving the theatre's financial processes to the cloud, starting with a transition from Excel spreadsheets to Google Sheets. Then, in June 2025, a few months after being made the finance manager, someone at Intuit's Get Connected conference mentioned Zapier in a session. John got curious about what he could automate.
He started small, on the free plan. Invoices that landed in his inbox were forwarded automatically to QuickBooks Online's document intake system for review, so he could process them there. "Just removing little bits of manual labor," he says. Once he was comfortable with classic Zaps, he got approval from the theatre's artistic producer to upgrade to a paid plan and started building multi-step workflows.
The error list that kept growing
John works 28 hours a week at the theatre over three days. The more Zaps he built, the more of those hours went to keeping them running. A format would change, a Zap would error, and he'd have to find the time to go back and fix it.
"My list of errors that I just had to fix in my automations just kept growing and growing, because I didn't have any time to be able to go back to them," he says.
Next-Gen Zaps changed that. John works in ChatGPT, connected to Zapier, and his conversion process is simple. "I paste the link to the classic Zap," he says. "I just tell it, convert it to a Next-Gen Zap, and then also fix A, B, C and D that's also wrong. And then just let it run." The agent handles much of the development work, but the resulting workflows still require testing and verification before they can be relied upon in production. This allows John to build and maintain automations more efficiently while retaining responsibility for financial oversight.
He started in early October. Six weeks later he had built 59 Next-Gen Zaps, 30 of them rebuilt from classic Zaps, and 42 of them are live today.
The Zap he'd wanted for years
Some automations had always seemed like pipe dreams. Daily sales was one of them. The theatre's previous ticketing setup didn't provide the automated daily reports John needed, so there was nothing for a Zap to start from.
When the theatre switched ticketing systems, the new one emailed a report every day. That gave John a clean trigger. He told the agent what the report looked like, what to pull out of it, and to "look at previous daily sales entries to understand the structure."
The biggest challenge wasn't building the Zap: it was ensuring the resulting accounting entries were accurate. Each line of a sales entry needs the right project and class in QuickBooks Online, and those change with every show. So John built a productions sheet in Google Sheets by hand: the show's name, opening and closing dates, and its project, customer and class IDs. The Zap uses the productions sheet to determine the appropriate accounting allocations for each journal entry, including the relevant project, class, and revenue account. The process includes validation checks, exception handling, and reconciliation procedures, allowing John to review unexpected results and trace accounting entries back to their supporting records.
He built that sheet himself on purpose. "I want to make sure I'm using my thinking to understand the layout of how things are going to work first," he says.
Structure before automation
That's the lesson John would pass on to anyone starting out. "You need to understand the structure to your existing processes before you can even think about automating them," he says.
The trap, he says, is asking for an outcome without knowing the steps. "What's the A, B, C and D to get to the end goal? When you don't have that in place, it's hard to even think about what the first automation step could be."
AI only where it has to think
John believes that AI has a place in financial workflows, but that its outputs should always be independently verifiable. He wants to be able to look back at any figure and understand exactly where it came from and how it was calculated.
That's a big part of why he's continued using Zapier. "Everything's basically a deterministic workflow, except for when you need it," he says.
John is also developing a credit card reconciliation process that uses AI to extract statement transactions into a structured Google Sheet. Other Zaps collect receipts and supporting documentation, with the goal of matching those records against statements, identifying missing receipts, and preparing follow-up emails. The process is designed to keep the accounting decisions and final review in human hands.
"Not a question of should I or can I"
For John, automation isn't about removing people from financial decisions. It's about freeing up time for the work that requires his attention, from investigating discrepancies to planning the theatre's finances.
Today, John's Zaps support financial processes across the theatre, including payables and vendor intake, receivables and cash flow, daily sales and deposits, payroll entries and timesheets, artist and rental contracts, tax and compliance, and month-end reporting. Between his classic and Next-Gen Zaps, 63 did work in the last 90 days. We compared him with 371 other finance and bookkeeping builders, and the median runs 10.
John also recognizes that successful automation depends on more than the technology itself. The workflows need to be accessible to the colleagues who interact with them, allowing staff to benefit from automation without needing to understand how the underlying automations are built or maintained.
Making workflows accessible doesn't mean removing the need for oversight. For John, the challenge is designing workflows that automate repetitive steps while preserving the checks and human decisions that financial processes require. Even so, his perspective on what's possible has changed. "I've gotten past the point of can I automate this, to how I automate this," he says. "It's not a question of should I or can I, but how."
John Cabanela is the finance manager at Theatre Passe Muraille in Toronto. He also runs his own bookkeeping and tax preparation practice.
Learn more about Next-Gen Zaps.









