The Bot Team
Office bots for Grok Bot and Claude, rebuilt from public bots and set up to work together on work that runs over days.
Most Grok Bots do one task and stop. Your office work doesn’t. The enquiry turns into a quote on Monday, the job on Thursday, the invoice the week after, and the chase a month later. When each step sits in a different bot, someone retypes the details between them, and that’s where jobs go missing.
The Bot Team passes the work along like a relay baton. Each bot picks the job up where the last one left it, with the same customer, the same job and the same figures, and hands it on when its part is done. Nothing is retyped, and no bot pays a bill or approves spending: money decisions stay with a person.
Every bot started as one someone built for their own business, credited to them by name, or as one we built ourselves. Each is rebuilt to the same written rules and tested before it’s listed. We test on sample records, not yours. The real test is the first week on your own jobs.
New to running more than one bot? How to set up a Bot Team shows how to put them in one channel with a manager bot and a board.
1. The cash path, hop by hop
Four hops from the call to the money, bound by the Cash Seam so one id survives all four. Every bot on this path also brings a green Cash Seam run.
1. Booked After Hours
Woken by
call.received, hands onjob.created- After-Hours DeskListed, routable
Answers the phone when we're closed, books one job per caller in our job system, and wakes the on-call only for a real emergency.
- Woken by:
- call.received (webhook)
- Hands on:
- job.created
- Systems:
- ServiceM8, Simpro
- Evidence:
- self-run, booked-after-hours 8 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on After-Hours Front Desk by John Shetler. Rebuilt and maintained by AI Pathway.Show the original
This is John Shetler’s own bot, not the version above, and it won’t pass the job along: After-Hours Front Desk. - Roof DeskListed, routable
Answers roofing calls we miss after hours, checks the address is in our area, books one inspection or repair job, and wakes the on-call roofer only when water is coming in.
- Woken by:
- call.received (webhook)
- Hands on:
- job.created, exception.raised
- Systems:
- ServiceM8, Simpro
- Evidence:
- self-run, booked-after-hours 8 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Route missed roofing calls to a Retell AI agent with Twilio and Google Workspace by Khadija Naeem. Rebuilt and maintained by AI Pathway.Show the original
This is Khadija Naeem’s own bot, not the version above, and it won’t pass the job along: Route missed roofing calls to a Retell AI agent with Twilio and Google Workspace.
2. Quote Out
Woken by
job.created, hands onquote.sent- Defect QuoteListed, routable
When a tech logs fire or life-safety defects on a site's inspection or fault job, draft one rectification quote on it from our own price list, or park it, and leave it for us to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- Simpro, ServiceM8, Xero (Items as the rectification price list, Quotes)
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Design QuoteListed, routable
When a customer accepts their solar or heat-pump design and it is on the job, draft the job's quote lines from our own price book, or park it with a reason, and leave it for us to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- Simpro, ServiceM8, Xero (Items as the price book, Quotes)
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Estimate DeskListed, routable
When a price request from our website form is logged as a job, draft the estimate from our own price list, or park it with a reason, and tell me it is ready for me to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- Xero (Items as the price list, Quotes), ServiceM8, Simpro (parts only)
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Send instant price quotes from forms with Data Tables, Telegram and Gmail by Tomasz Kaczyński. Rebuilt and maintained by AI Pathway.Show the original
This is Tomasz Kaczyński’s own bot, not the version above, and it won’t pass the job along: Send instant price quotes from forms with Data Tables, Telegram and Gmail. - Measure QuoteListed, routable
When the site measure is on the job (rooms, square metres, lineal metres, counts), draft the quote at our own price-list rates, or park it with a reason, and leave it for us to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- ServiceM8, Simpro, Xero (Items as the price list, Quotes)
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Parts QuoteListed, routable
When a customer's spare-parts enquiry is logged as a job, draft its quote from our own parts price list, or park it with a reason, and leave it for us to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- Xero (Items as the parts price list, Quotes), ServiceM8, Simpro (parts only)
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Generate & Send Spare Parts Price Quotes with Gmail, Sheets and Gemini AI by berke. Rebuilt and maintained by AI Pathway.Show the original
This is berke’s own bot, not the version above, and it won’t pass the job along: Generate & Send Spare Parts Price Quotes with Gmail, Sheets and Gemini AI. - Proposal DeskListed, routable
When we open a proposal job for a prospective client, draft their engagement fee quote from our own service price list, or park it with a reason, and hold it for a partner to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- Xero Practice Manager (the prospect's proposal job), Xero (Items as the service price list, Quotes)
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Quote DeskListed, routable
When a job is booked, draft its quote in our job system from our own price list, or park it with a reason, and leave it for us to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.sent, exception.raised
- Systems:
- ServiceM8, Simpro, Xero
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Tiffany by Micah Watson. Rebuilt and maintained by AI Pathway.Show the original
This is Micah Watson’s own bot, not the version above, and it won’t pass the job along: Tiffany. - Takeoff QuoteListed, routable
Count the fittings and cable runs on a tender job's current drawings, draft the quote from our own pre-builds and price list, park anything the book misses, and leave it for us to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- Simpro, ServiceM8, Xero (Items as the price list and pre-builds, Quotes)
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Tier QuoteListed, routable
When a job is booked, draft one quote with good, better and best options from our own tier list, each line at our own price-list rate, or park it, and leave it for us to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- ServiceM8, Simpro, Xero (Items as the price list, Quotes)
- Evidence:
- self-run, quote-out 10 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Trim QuoteListed, routable
When a finish-carpentry job has its labour hours on it, draft the quote as hours times our own sell-rates, or park it with a reason, and leave it for us to send.
- Woken by:
- job.created (webhook), job.updated (webhook)
- Hands on:
- quote.drafted, exception.raised
- Systems:
- ServiceM8, Simpro, Xero (Items as the price list, Quotes)
- Evidence:
- self-run, quote-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Estimator by Mike A. Rebuilt and maintained by AI Pathway.Show the original
This is Mike A’s own bot, not the version above, and it won’t pass the job along: Estimator.
3. Invoice Out
Woken by
quote.accepted or job.completed, hands oninvoice.raised- Contract BillingListed, routable
When a maintenance contract's billing period closes, draft the client's service invoice in Xero at our schedule of rates, park what it cannot price, and hold it for a named person.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the job system that holds each maintenance contract and closes one billing-period record per contract per cycle on its billing date (Simpro, ServiceM8 or the fire maintenance system the business runs), issuing the period's id (carried as job_id), Xero, which issues the invoice_id
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Delivery BillingListed, routable
When a delivery job is marked done, put its draft invoice in Xero at our own item prices, park what it cannot price, and send only once our rule or accounts person releases it.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the job or dispatch system that issues the job_id (ServiceM8, Simpro, or a job sheet), Xero, which issues the invoice_id
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Create a QuickBooks invoice on a new Onfleet Task creation by James Li. Rebuilt and maintained by AI Pathway.Show the original
This is James Li’s own bot, not the version above, and it won’t pass the job along: Create a QuickBooks invoice on a new Onfleet Task creation. - Docket BillingListed, routable
When a job is marked complete, turn its signed site dockets of hours, plant and materials into one draft Xero invoice at our rates, park what it can't bill, and hold it for a named person.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the job system that issues the job_id and holds the site dockets filed against it as job lines (ServiceM8, Simpro, or a job sheet), Xero, which issues the invoice_id and holds the schedule of rates as Items
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Invoice DeskListed, routable
When a job is marked complete, put its draft invoice in Xero at our own prices, park what it cannot price, and send only once a named person or their rule releases it.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the job system that issues the job_id (ServiceM8, Simpro, or a job sheet), Xero, which issues the invoice_id
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Create and approve Xero invoices from Pipedrive Closed Won deals with Slack by Intuz. Rebuilt and maintained by AI Pathway.Show the original
This is Intuz’s own bot, not the version above, and it won’t pass the job along: Create and approve Xero invoices from Pipedrive Closed Won deals with Slack. - Invoice HoldListed, routable
When a renovation job is marked complete, draft its one invoice in Xero at our own prices and hold it until a named person, or their rule, releases it.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the job system that issues the job_id (ServiceM8, Simpro, or a job sheet), Xero, which issues the invoice_id
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Chief of Staff by Amine. Rebuilt and maintained by AI Pathway.Show the original
This is Amine’s own bot, not the version above, and it won’t pass the job along: Chief of Staff. - Matter BillingListed, routable
When our practice system marks an appearance or signed draft done, draft its invoice in Xero at our rate card, or park it with a reason, and hold it for the solicitor's release.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the firm's practice management system, which issues the id of each billable task on a matter (carried as job_id), Xero
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Fee Note and Invoice Clerk by Suyash Verma. Rebuilt and maintained by AI Pathway.Show the original
This is Suyash Verma’s own bot, not the version above, and it won’t pass the job along: Fee Note and Invoice Clerk. - Outgoings DeskListed, routable
Each year, when a commercial tenant's outgoings are reconciled, work out their share from the lease, draft the recovery invoice in Xero, park any unclear share, and hold it for the manager.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the property management system that holds each commercial lease, its recoverable outgoings and the tenant's share, and issues one outgoings reconciliation record per tenancy per outgoings year (carried as job_id, with the tenancy_id on it), which the property manager marks final, the building's outgoings schedule for the year, actual and budget per category, kept as the agency's Xero items for that building, Xero, which issues the invoice_id
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Recharge DeskListed, routable
Each month, turn the software we pay for on clients' behalf into one draft recharge invoice per client in Xero at our recharge prices, and hold it for a named person to release.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the practice's subscription register (a sheet or the practice management system) that holds one recharge period per client per month, with each subscription on it reconciled to the supplier's bill, and issues the period's id (carried as job_id), Xero, which issues the invoice_id
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Stage BillingListed, routable
When a building job reaches a stage on its payment schedule, deposit included, draft that stage's invoice in Xero at the contract amount, park what it can't bill, and hold it for a named person.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the job system that holds each building job's payment schedule as one stage record per instalment and marks a record complete when the supervisor signs that stage off (Simpro, ServiceM8, Buildxact or the job sheet the builder runs), issuing the stage record's id (carried as job_id), Xero, which holds the agreed payment schedules as items and issues the invoice_id
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-04); cash-seam 4 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Timesheet BillingListed, routable
When a client's timesheet period closes, draft its invoice in Xero from the hours at our rate card, park what it cannot price, and hold it for a named person to release.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- invoice.raised, invoice.sent, exception.raised
- Systems:
- the job system that holds each client engagement's billing periods, with the time entries filed from the staff's emailed timesheets, and issues the period's id (carried as job_id), Xero, which issues the invoice_id
- Evidence:
- self-run, invoice-out 7 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Convert emailed timesheets into QuickBooks invoices with OCR, AI, Gmail and Sheets by DIGITAL BIZ TECH. Rebuilt and maintained by AI Pathway.Show the original
This is DIGITAL BIZ TECH’s own bot, not the version above, and it won’t pass the job along: Convert emailed timesheets into QuickBooks invoices with OCR, AI, Gmail and Sheets.
4. Debtor Chasing
Woken by
invoice.overdue, hands onpromise.recorded- Chase BookListed, routable
Every morning, read who owes us from Xero, send one reminder per customer pitched to how late they are, log it on the invoice, and hand disputes and big accounts to a named person.
- Woken by:
- schedule.tick (schedule), invoice.overdue (poll), payment.received (webhook), email.received (webhook), exception.closed (webhook)
- Hands on:
- promise.recorded, exception.raised
- Systems:
- Xero (invoices, contacts and invoice history), Gmail or Outlook (the reminder thread and the debtor's reply)
- Evidence:
- self-run, debtor-chasing 9 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Send tiered overdue invoice reminders with Xero, Gmail, Slack, and Google Sheets by Intuz. Rebuilt and maintained by AI Pathway.Show the original
This is Intuz’s own bot, not the version above, and it won’t pass the job along: Send tiered overdue invoice reminders with Xero, Gmail, Slack, and Google Sheets. - Chase DeskListed, routable
Every morning, rank who owes us by what is at risk, chase only those the rules allow, record each promise as a date, and hand disputes to a named person.
- Woken by:
- schedule.tick (schedule), invoice.overdue (webhook), payment.received (webhook), exception.closed (webhook)
- Hands on:
- promise.recorded, exception.raised
- Systems:
- Xero (the ledger that issues the invoice_id, its contacts and its invoice history), the job system named on the invoice (ServiceM8, Simpro), read by job_id only
- Evidence:
- self-run, debtor-chasing 9 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Accounts Receivable by Thomas Matteson. Rebuilt and maintained by AI Pathway.Show the original
This is Thomas Matteson’s own bot, not the version above, and it won’t pass the job along: Accounts Receivable. - Chase ListListed, routable
Each morning, rank who owes us money by what it is worth chasing, draft a friendly, firm or final reminder for each, and leave them for us to send.
- Woken by:
- schedule.tick (schedule), invoice.overdue (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- promise.recorded, exception.raised
- Systems:
- Xero, MYOB, the exception desk the business runs
- Evidence:
- self-run, debtor-chasing 9 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Invoice Chaser by Thuong P. Nguyen. Rebuilt and maintained by AI Pathway.Show the original
This is Thuong P. Nguyen’s own bot, not the version above, and it won’t pass the job along: Invoice Chaser. - Nudge DeskListed, routable
Every weekday, find our overdue invoices, chase each customer once in the right order, never past the do-not-chase list or the gate, and turn a reply with a date into a promise.
- Woken by:
- schedule.tick (schedule), invoice.overdue (poll), email.received (webhook), exception.closed (webhook)
- Hands on:
- promise.recorded, exception.raised
- Systems:
- QuickBooks Online (the ledger that issues the invoice_id), Gmail (the reminder and the reply, by message_id), the exception desk the business runs (a sheet or a task list that issues the exception_id)
- Evidence:
- self-run, debtor-chasing 9 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Chase overdue QuickBooks invoices with Claude, Gmail, Slack and Google Sheets by Amplence. Rebuilt and maintained by AI Pathway.Show the original
This is Amplence’s own bot, not the version above, and it won’t pass the job along: Chase overdue QuickBooks invoices with Claude, Gmail, Slack and Google Sheets. - Owing TodayListed, routable
Every morning, show me who owes us money, biggest first, with a polite or firmer reminder already written for each one, and I send them.
- Woken by:
- schedule.tick (schedule), payment.received (webhook), email.received (webhook), exception.closed (webhook)
- Hands on:
- promise.recorded, exception.raised
- Systems:
- Xero, MYOB, ServiceM8, the exception desk the business runs
- Evidence:
- self-run, debtor-chasing 9 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Invoice Chaser by Mark G. Rebuilt and maintained by AI Pathway.Show the original
This is Mark G’s own bot, not the version above, and it won’t pass the job along: Invoice Chaser. - Payment WatchListed, routable
Keep track of what each client owes, check the ledger and the inbox for a payment before every reminder, and draft one calm reminder per client for me to say yes to.
- Woken by:
- schedule.tick (schedule), invoice.overdue (schedule), payment.received (webhook), email.received (webhook), exception.closed (webhook)
- Hands on:
- promise.recorded, exception.raised
- Systems:
- Xero, MYOB, Gmail (the reminder threads, each carrying its invoice id), the exception desk the business runs
- Evidence:
- self-run, debtor-chasing 9 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on Freelance Invoice Chaser by Cristopher Guido. Rebuilt and maintained by AI Pathway.Show the original
This is Cristopher Guido’s own bot, not the version above, and it won’t pass the job along: Freelance Invoice Chaser. - Promise WatchListed, routable
Turn every client's "I'll pay by" reply into a dated promise on the invoice, and when that date passes unpaid, draft the next chase for the owner to approve.
- Woken by:
- schedule.tick (schedule), invoice.overdue (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- promise.recorded, exception.raised
- Systems:
- Xero (the ledger that issues the invoice_id; the promise is written onto the invoice), Gmail (the watched inbox that issues the message_id of each client reply and holds the chase drafts)
- Evidence:
- self-run, debtor-chasing 9 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
Based on PayDate Chase by Skip Rogers. Rebuilt and maintained by AI Pathway.Show the original
This is Skip Rogers’s own bot, not the version above, and it won’t pass the job along: PayDate Chase. - Terms WatchListed, routable
Each business day, chase the customers whose invoices are past their due date, biggest risk first, inside the calling rules, and turn each reply with a date into a promise.
- Woken by:
- schedule.tick (schedule), invoice.overdue (webhook), email.received (webhook), payment.received (webhook), exception.closed (webhook)
- Hands on:
- promise.recorded, exception.raised
- Systems:
- the ledger that issues the invoice_id (Xero, MYOB or QuickBooks): its invoices, contacts and invoice history, the mail system that issues the message_id of a debtor's reply (Gmail, Outlook)
- Evidence:
- self-run, debtor-chasing 9 green, 1 with_us (2026-11-03); cash-seam 4 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
2. Other office jobs
- Ageing MondayListed, routable
Every Monday, publish the accounts receivable ageing report from the ledger, every figure with its definition, source and as-of time, and say so when one cannot be read.
- Woken by:
- schedule.tick (schedule)
- Hands on:
- report.published, exception.raised
- Systems:
- the ledger (Xero or MYOB): aged receivables by due date, the job system (ServiceM8 or Simpro): completed jobs not yet invoiced, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-03)
Based on Send weekly AR ageing reports with Invoice Ninja, PDFMint and Gmail by Florian Standhartinger. Rebuilt and maintained by AI Pathway.Show the original
This is Florian Standhartinger’s own bot, not the version above, and it won’t pass the job along: Send weekly AR ageing reports with Invoice Ninja, PDFMint and Gmail. - Agent Rules DeskListed, routable
Answer our agents on the state agent rules we are licensed under, only from the rules we hold, citing the clause and edition, or hand the question to the licensee in charge.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- answer.sent, exception.raised
- Systems:
- the mail system that issues the message_id an agent's question arrived on and the reply went out on (Gmail, Outlook), the agency's own rule library: the state agent legislation and regulations for each state it is licensed in (NSW, QLD, VIC and the rest) and its compliance manual, held as clauses with editions, state or territory and effective dates, with its answer register, the exception desk the agency runs, which issues the exception_id
- Evidence:
- self-run, cited-answer 7 green, 1 with_us (2026-11-03)
Based on CA Brokerage Compliance by Joe Foxx. Rebuilt and maintained by AI Pathway.Show the original
This is Joe Foxx’s own bot, not the version above, and it won’t pass the job along: CA Brokerage Compliance. - Agreement ChaseListed, routable
Before a new commercial customer's first job, chase their signed service agreement and rate sheet, file each the day it comes back, and hand a no, a dispute or a silent customer to a named person.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the onboarding register, one open item per document owed on the new customer's first job (the job system such as ServiceM8 or Simpro, or a SharePoint list or Google Sheet kept beside it), which issues the job_id and the item id, the accounts mailbox (Outlook or Gmail) the signed agreement and rate sheet come back to, which issues the message_id
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Arrears DeskListed, routable
Each day after the platform's own reminders, chase only tenants who are truly behind, quoting the paid-to date and exact balance, and hand the rest to a named person.
- Woken by:
- schedule.tick (schedule), rent.overdue (webhook), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the property management system that issues the tenancy_id (PropertyMe, Console Cloud or similar): its tenancy ledger, rule store and message log
- Evidence:
- self-run, rent-arrears 5 green, 1 with_us (2026-11-03)
Based on Rent Collections Desk by Nymble Pay. Rebuilt and maintained by AI Pathway.Show the original
This is Nymble Pay’s own bot, not the version above, and it won’t pass the job along: Rent Collections Desk. - Arrival BriefListed, routable
Each morning, send every tech a brief of their jobs that leads with the dog, key safe, hazards and access, quoting the job record each line came from, and saying what is missing.
- Woken by:
- schedule.tick (schedule), job.updated (webhook), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- ServiceM8, Simpro, AroFlo or Fergus (the day's slots, the job, and the site's hazard, access, visit, note, parts, quote and asset records, read by the job's customer id), the exception desk the business runs (a task list or a sheet)
- Evidence:
- self-run, job-brief 6 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Backflow WatchListed, routable
Every morning, check our backflow device register against each state's rule, draft bookings for tests due soon, and put anything overdue or unclear in front of a named person.
- Woken by:
- schedule.tick (schedule), document.received (webhook), exception.closed (webhook)
- Hands on:
- asset.service_due, exception.raised
- Systems:
- the contractor's asset register of testable backflow prevention devices (its dated rule store per state, and the document store the signed test reports are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-03)
Based on Triage backflow compliance notices with Google Sheets, Gmail, Slack, OpenAI, and a state API by Swapnil Mandloi. Rebuilt and maintained by AI Pathway.Show the original
This is Swapnil Mandloi’s own bot, not the version above, and it won’t pass the job along: Triage backflow compliance notices with Google Sheets, Gmail, Slack, OpenAI, and a state API. - Balance ProofListed, routable
Each month, tie every balance sheet account in Xero to the statement that supports it, by account id, and list every balance nobody can explain for a named person to clear.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- Xero (the ledger that issues the account id and holds each balance sheet account's month-end balance), the practice's support file for the month (bank, loan and hire purchase statements, the ATO integrated client account, payroll liabilities and super reports, the fixed asset register), each document tagged with the Xero account id it supports
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Bank QuestionsListed, routable
Each weekday, ask each client in plain words what their uncategorised bank transactions were, stop when they answer, and turn the answers into coding suggestions for the bookkeeper.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the practice's register of what each client owes it, one open item per client per period on the client's bookkeeping job (a practice management system such as Xero Practice Manager or FYI, or a register kept beside it), Xero, whose bank feed issues the id of each uncategorised bank line the questions are about (read only; nothing is coded or reconciled by this bot), the practice's mail system, which issues the message_id of the client's reply carrying the answers
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Bill CheckListed, routable
Check every supplier bill that lands in the ledger against its purchase order before anyone books or pays it, and put each one in exactly one queue for a person.
- Woken by:
- bill.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- exception.raised
- Systems:
- Xero or MYOB (the ledger that issues the bill_id and holds the purchase orders), the document store where the written variation approvals live
- Evidence:
- self-run, invoice-check 7 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Billing MatchListed, routable
Every morning, check each customer's CRM billing details against Xero by account id, show each difference with both values and the owning system, and fix one only once a named person accepts it.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the CRM (issues the customer account id; owns billing email, billing address and ABN), Xero (the invoicing ledger; carries the CRM account id on the contact and owns the invoiced total, last invoice date and payment terms)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-03)
Based on Reconcile CRM and invoicing owner fields with HTTPS APIs and Data Tables by Kuliberda Labs. Rebuilt and maintained by AI Pathway.Show the original
This is Kuliberda Labs’s own bot, not the version above, and it won’t pass the job along: Reconcile CRM and invoicing owner fields with HTTPS APIs and Data Tables. - Branch DriftListed, routable
Every week, check each branch or franchise against our written operating standard, score its drift the same way for all, send each its own report, and put a slipping one in front of a named person.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the versioned key contract the business keeps (a SharePoint list or Google Sheet) that issues the contract version, Microsoft 365 or Google Workspace access groups, which decide which branch a record belongs to, each branch's own report location (a folder, channel or list) that issues the report_id, the exception desk the business runs, which issues the exception_id
- Evidence:
- self-run, multi-site-conformance 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Buy DeskListed, routable
Buy the materials for one job from stock first and the supplier's own prices, release only under the money rules, and check every delivery docket back.
- Woken by:
- schedule.tick (schedule), job.updated (webhook), document.received (webhook), exception.closed (webhook)
- Hands on:
- order.sent, delivery.recorded, exception.raised
- Systems:
- the job system that issues the job_id and holds its material list and stock, the supplier portal or job-system purchasing that issues each order's external id
- Evidence:
- self-run, material-order 9 green, 1 with_us (2026-11-03)
Based on Home Remodel Job Desk by Howie. Rebuilt and maintained by AI Pathway.Show the original
This is Howie’s own bot, not the version above, and it won’t pass the job along: Home Remodel Job Desk. - Cash AheadListed, routable
Every Monday, publish our 13-week cash forecast from the open invoices, bills and payroll, with the assumption behind every line written down, and say so when a line cannot be read.
- Woken by:
- schedule.tick (schedule)
- Hands on:
- report.published, exception.raised
- Systems:
- the ledger (Xero or MYOB): open sales invoices, open bills and the operating bank balance, the payroll system (Xero Payroll, KeyPay or Employment Hero): the pay calendar and the last finalised pay run, the system the forecast is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Claim CheckListed, routable
Check every subbie's claim, line by line, against the agreed contract rate before anyone pays it, keep the record, and put any mismatch in front of a named person.
- Woken by:
- bill.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- bill.checked, exception.raised
- Systems:
- Xero or MYOB (the ledger that issues the bill_id and holds the subcontract or purchase order with its agreed rates), the job system (Simpro, ServiceM8 or similar) for the quantity marked complete, the document store where the signed variation approvals live
- Evidence:
- self-run, invoice-check 7 green, 1 with_us (2026-11-03)
Based on Check invoice contract price compliance with Google Sheets and Telegram alerts by Abdullah Latif. Rebuilt and maintained by AI Pathway.Show the original
This is Abdullah Latif’s own bot, not the version above, and it won’t pass the job along: Check invoice contract price compliance with Google Sheets and Telegram alerts. - Claim ClockListed, routable
When a subbie's payment claim comes in, work out when our payment schedule is due under that state's security of payment rule, remind the named person, and draft the schedule for them to serve.
- Woken by:
- document.received (webhook), email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the business's claims register (each subcontractor payment claim on its job, with the date it was served, the state the job is in, and the named person who owns it), the dated security of payment rule set per state, and the document store served payment schedules are filed in
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Claim MatchListed, routable
Each morning, check every insurance repair job against the insurer's claim by claim number, show any missing or different scope, photo or report with both values, and fix only what a person accepts.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (Simpro, ServiceM8 or similar: carries the insurer's claim number on the job; owns photos filed and reports lodged), the insurer's claim record (the claim portal or its export: issues the claim number; owns the authorised scope, scope version, excess and claim status)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Client Review WatchListed, routable
Work out when each client's AML/CTF review is next due from our program's dated rules, and list everyone due or overdue, with their last review, for our compliance officer.
- Woken by:
- schedule.tick (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the practice's client review register (its AML/CTF program's dated review rules by risk rating, each client's review obligation, and the document store signed review records are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Client Site ReportListed, routable
Each month, publish each commercial client a report on their sites: jobs done, assets overdue, open defects and services due next, every line traced to its record, for their account manager to send.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (such as Simpro) that holds each site's completed jobs and logged defects, issuing the job_id, the asset register that holds each site's fire and electrical assets with their AS 1851 or AS/NZS 3760 service dates, issuing the asset_id, the business's report store or client portal the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Close CheckListed, routable
Each month, check whether a client's Xero file is ready to close and publish Ready or Not ready with the items to fix.
- Woken by:
- schedule.tick (schedule)
- Hands on:
- report.published, exception.raised
- Systems:
- the ledger (Xero): bank statement lines, draft invoices and bills, the suspense account and tax rates for the month, the practice management system (such as Xero Practice Manager or Karbon): the client's month-end close job and its open steps, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-03)
Based on Bookkeeping Ninja Month-End by Tim Armstrong. Rebuilt and maintained by AI Pathway.Show the original
This is Tim Armstrong’s own bot, not the version above, and it won’t pass the job along: Bookkeeping Ninja Month-End. - Comeback ListListed, routable
Every weekday morning, pick the past customers from our job history who are due a check-up or have not used us in a year, say why each one, and draft a short text for me to send.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (ServiceM8, Simpro, Fergus, Tradify or AroFlo) that holds each customer, their completed jobs with the job_id, the last outcome and the do-not-contact flag, the place the owner opens each morning (job system tasks, a shared sheet or a morning email), which issues the report_id for each day's list
- Evidence:
- self-run, database-reactivation 8 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Comp CheckListed, routable
For each appraisal, check the price against comparable sales chosen by written rules, each sourced and dated, and hold the one-page evidence for the agent to approve.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the agency's listing system, which issues the listing_id for the appraisal and holds the subject property and the agent's appraisal, the recorded sales source the agency already licenses (for example a state valuer-general sales record), the document store the approved one-pager and its record of what was shown are published into, which issues the report_id
- Evidence:
- self-run, price-one-pager 9 green, 1 with_us (2026-11-03)
Based on Listing Agent Desk LITE by Balaci Claudiu. Rebuilt and maintained by AI Pathway.Show the original
This is Balaci Claudiu’s own bot, not the version above, and it won’t pass the job along: Listing Agent Desk LITE. - Comp ReportListed, routable
Every Monday, publish the multifamily comp report: availability, effective rents and the comp set, every figure linked to its source and read time.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the property management system (rent roll and unit availability), the comp survey the leasing team keeps, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-03)
Based on Multifamily Comp Desk by Matthew Dickson. Rebuilt and maintained by AI Pathway.Show the original
This is Matthew Dickson’s own bot, not the version above, and it won’t pass the job along: Multifamily Comp Desk. - Company Review WatchListed, routable
Keep each client company's ASIC annual review and officeholder change dates worked out from dated rules, draft the client reminder before late fees start, and file the proof.
- Woken by:
- schedule.tick (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the practice's obligation register (its client company calendar, dated rule set and the document store ASIC confirmations and fee receipts are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Consultant HoursListed, routable
Total each consultant's onsite, remote and unplaced hours from their PDF timesheets, put the odd ones in front of a named person, and send nothing to payroll until someone releases it.
- Woken by:
- document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the document store that issues the document_id for each PDF timesheet (SharePoint or Google Drive); entries are keyed <document_id>#<row>, the job system that issues the job_id and holds the allocations and the roster, the payroll system that takes one export per period and returns its id (Xero Payroll, Employment Hero or MYOB), the workbook or report store the payroll officer opens, which returns a report_id, the exception desk the business runs, for the anomaly queue
- Evidence:
- self-run, timesheet-check 10 green, 1 with_us (2026-11-03)
Based on Extract consultant hours from PDF timesheets with Azure OpenAI and Excel by Christoph Dibbern. Rebuilt and maintained by AI Pathway.Show the original
This is Christoph Dibbern’s own bot, not the version above, and it won’t pass the job along: Extract consultant hours from PDF timesheets with Azure OpenAI and Excel. - Cost DeskListed, routable
Put each supplier bill on its job by the order number printed on it, so the job's cost is current, and list every bill with no clear job for a named person.
- Woken by:
- document.received (webhook), email.received (webhook), exception.closed (webhook), schedule.tick (schedule)
- Hands on:
- evidence.filed, report.published, exception.raised
- Systems:
- the job system that issues the job_id and the purchase order (order_id) each bill is filed on, e.g. Simpro, ServiceM8, AroFlo or Fergus, Xero, for supplier contacts and statements
- Evidence:
- self-run, document-filing 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Cover CheckListed, routable
File each contractor insurance certificate against their record, check it is current and right for the work, track its expiry, and clear no one with an item missing until a person releases it.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the mail system that issues the message_id (the agency's Gmail or Outlook mailbox the certificates arrive in), the property management system's contractor record (PropertyMe, Console Cloud or PropertyTree) that each certificate is bound to, the document store that holds the filed original (SharePoint, OneDrive or Google Drive), the exception desk the agency runs, holding each stopped pack with its named owner
- Evidence:
- self-run, rejected-pack 9 green, 1 with_us (2026-11-03)
Based on Track vendor insurance COIs and renewals with Gmail, DeepSeek, Sheets, Discord, and Telegram by Khaisa Studio. Rebuilt and maintained by AI Pathway.Show the original
This is Khaisa Studio’s own bot, not the version above, and it won’t pass the job along: Track vendor insurance COIs and renewals with Gmail, DeepSeek, Sheets, Discord, and Telegram. - Crew BoardListed, routable
Put each lawn or field-service job on the right licensed crew member at a time that fits, tell the customer and the tech once, and hand anything it cannot place to the dispatcher.
- Woken by:
- schedule.tick (schedule), job.created (webhook), job.updated (webhook), exception.closed (webhook)
- Hands on:
- job.updated, exception.raised
- Systems:
- the job system that issues the job_id and holds its schedule (ServiceM8, Simpro or Jobber), the tech licence register the business keeps
- Evidence:
- self-run, dispatch-board 8 green, 1 with_us (2026-11-03)
Based on Dispatcher by Brett Brownlee. Rebuilt and maintained by AI Pathway.Show the original
This is Brett Brownlee’s own bot, not the version above, and it won’t pass the job along: Dispatcher. - Danger Tag DeskListed, routable
When a tech tags an appliance Danger Do Not Use, note it on the job, draft the written notice to the owner or managing agent that day, and hand it to a named person to send and follow up.
- Woken by:
- job.updated (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- exception.raised, report.published
- Systems:
- the job system that issues the job_id (ServiceM8, Simpro, AroFlo or Fergus), where the tag and the notice are recorded, the ledger that issues the invoice_id (Xero), for items raised against an invoice, the exception desk the business runs (a sheet with Raise and Routing tabs, a SharePoint list, or Office Voice's queue), which issues the exception_id, Gmail or Outlook drafts, where the written notice waits for the named person
- Evidence:
- self-run, exception-desk 6 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Day DeskListed, routable
Answers our phone during the day, looks the caller up, tells an existing customer when we're coming off their job, and writes new work as one job.
- Woken by:
- call.received (webhook), job.updated (webhook), job.completed (webhook)
- Hands on:
- job.created, job.updated, exception.raised
- Systems:
- ServiceM8, Simpro
- Evidence:
- self-run, client-desk 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Deadline DeskListed, routable
Keep every deadline from our clients' letters and lodgements on a calendar derived from dated rules, chase replies, and put anything late or unclear in front of a named person.
- Woken by:
- schedule.tick (schedule), document.received (webhook), exception.closed (webhook)
- Hands on:
- exception.raised
- Systems:
- the practice's obligation register (its compliance calendar and the document store the forwarded letters and replies are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-03)
Based on Paperwork Desk by Daniel Masarsky. Rebuilt and maintained by AI Pathway.Show the original
This is Daniel Masarsky’s own bot, not the version above, and it won’t pass the job along: Paperwork Desk. - Deal MatchListed, routable
Every morning, check each CRM deal against its Simpro quote by quote id, show each difference in value, stage, customer or contact with both values, and change one only once a person accepts it.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the CRM (holds each sales deal, carries the Simpro quote id, and owns the contact name and contact email), Simpro (issues the quote id and owns the quote value ex GST, the quote stage and the Simpro customer id the quote is raised against)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Defect DeskListed, routable
When a sprinkler inspection report lands in the inbox, file each deficiency against its tagged asset, send critical ones to a named person now, and queue the rest.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the asset register that issues the asset_id (where the tags are already recorded), Gmail or Outlook (the watched inbox that issues the message_id), the exception desk the business runs (a sheet, a task list or a ticket queue)
- Evidence:
- self-run, fire-service-pack-standard 11 green, 1 with_us (2026-11-03)
Based on Route fire sprinkler deficiencies with Gmail, OpenAI, Telegram and Sheets by Swapnil Mandloi. Rebuilt and maintained by AI Pathway.Show the original
This is Swapnil Mandloi’s own bot, not the version above, and it won’t pass the job along: Route fire sprinkler deficiencies with Gmail, OpenAI, Telegram and Sheets. - Deposit MatchListed, routable
Every morning, match each customer deposit in the bank feed to the Xero invoice it paid, by the invoice id, and put every one that does not clearly match in front of the bookkeeper.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- payment.received, report.published, exception.raised
- Systems:
- Xero (the ledger that issues the invoice_id and records the payment applied to each sales invoice), the business's bank feed into Xero (customer deposits carrying the invoice_id in their reference)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-03)
Based on InvoiceMatch Recon Bot by Robert Schiff. Rebuilt and maintained by AI Pathway.Show the original
This is Robert Schiff’s own bot, not the version above, and it won’t pass the job along: InvoiceMatch Recon Bot. - Docs DueListed, routable
Each weekday, chase clients for the documents the practice still needs from them, stop when each one arrives, and hand a no or a silent client to a named person.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the practice's client document checklist, one open item per document owed on the client job (a practice management system such as Xero Practice Manager or FYI, or a register kept beside it), the practice's document store, where a returned document is filed against the client job
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Draw MatchListed, routable
Each morning, match every payment the managing agent sent against what landed in the landlord's books, by payment id, and put each short-pay, wrong fee or missing payment to the bookkeeper.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the managing agency's trust accounting system (PropertyMe, Console Cloud or similar), which issues the payment_id for each owner disbursement and its owner statement, the landlord's own ledger and bank feed (Xero or similar), where each agency deposit lands carrying that payment_id in the EFT reference
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-03)
Based on Doorfolio by Cameron Powell. Rebuilt and maintained by AI Pathway.Show the original
This is Cameron Powell’s own bot, not the version above, and it won’t pass the job along: Doorfolio. - Drawing RegisterListed, routable
Keep every machine drawing on our drive on one register with an owner and its current revision, find the page an electrician needs, and tell the owner when a drawing changes.
- Woken by:
- document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- exception.raised
- Systems:
- the shared drive that holds the drawings and issues the document_id (Google Drive or SharePoint), left where it is, the drawing register on that tenant (one Sheet or SharePoint list: a row per source, owner a person, kind, revision and checksum), the task list the business runs (Google Tasks, Planner or a sheet), which issues the exception_id for each gap
- Evidence:
- self-run, knowledge-base 11 green, 1 with_us (2026-11-03)
Based on Sparky by Zack Edwards. Rebuilt and maintained by AI Pathway.Show the original
This is Zack Edwards’s own bot, not the version above, and it won’t pass the job along: Sparky. - Follow-Up SweepListed, routable
Every evening, find what customers and suppliers still owe us that nobody chased, send the next capped follow-up on a consented channel, and hand any no or dead end to a named person.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- exception.raised
- Systems:
- the register of open items on the business's own records (the job system's quotes and variations, or a sheet kept beside it), with its contact consents and written cadence
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Expense CheckListed, routable
Check each staff expense claim has its receipt, a proper tax invoice where the ATO needs one, and fits our expense policy, then queue it for the approver to approve or reject.
- Woken by:
- bill.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- bill.checked, exception.raised
- Systems:
- Xero or MYOB (the ledger that issues the bill_id for the claim, entered as a draft bill payable to the staff member, and holds the expense policy lines), the document store where receipts and written pre-approvals are filed
- Evidence:
- self-run, invoice-check 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Fact LibraryListed, routable
Keep one read-only company knowledge graph that every bot in the fleet asks, where nothing goes live until a named person accepts it and a replaced document takes its answers with it.
- Woken by:
- document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the document store that issues the document_id for each source in the watched library folder (Drive, SharePoint), the business's own graph store and library register, which hold sources with edition and checksum, nodes, edges, change deltas and the answers given (lists, Postgres or a graph database on the business's account), the system of record that issues entity ids (the Xero contact, the CRM id, the ABN), the exception desk the business runs, which issues the exception_id
- Evidence:
- self-run, knowledge-graph 10 green, 1 with_us (2026-11-03)
Based on Ops Knowledge Observer by Stephen Ruhe. Rebuilt and maintained by AI Pathway.Show the original
This is Stephen Ruhe’s own bot, not the version above, and it won’t pass the job along: Ops Knowledge Observer. - Fault DeskListed, routable
Before we send a tech, check each fault call, text or alarm against our written fault list, give only our own reset steps, and book one job with what was tried.
- Woken by:
- email.received (webhook), call.received (webhook), exception.closed (webhook)
- Hands on:
- job.created, job.updated, exception.raised
- Systems:
- the job system that issues the job_id (ServiceM8 or Simpro, written over its API; on Tradify a person writes the job from the triage log), the fault list the business writes, one sheet or SharePoint list with an edition per upload, read before every triage and never written by the bot, the asset register that issues the asset_id and names each customer's model, the office's message system (Gmail or Outlook), whose drafts folder holds every written reply for a named person to send, the task list the office runs (Google Tasks, Planner or a sheet), which issues the exception_id for each parked alarm or failed job write
- Evidence:
- self-run, fault-triage 5 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Feed MatchListed, routable
Every morning, match each bank-feed payment to the bill in Xero it paid, by the bill id, and put every one that does not clearly match in front of the bookkeeper.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- Xero (the ledger that issues the bill_id and records each bill's payment), the business's bank feed into Xero (statement lines carrying the bill_id in the payment reference)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-03)
Based on Bookkeeping Ninja Bank Rec by Tim Armstrong. Rebuilt and maintained by AI Pathway.Show the original
This is Tim Armstrong’s own bot, not the version above, and it won’t pass the job along: Bookkeeping Ninja Bank Rec. - Fire Code DeskListed, routable
Answer our engineers' fire and electrical code questions from the Standards we hold, citing the clause and the edition the state adopted, or hand them to a named person.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- answer.sent, exception.raised
- Systems:
- the mail system that issues the message_id the question arrived on (Gmail, Outlook), the office's own clause library of the NCC, the Australian Standards it calls up (AS 1851, AS 1670.1, AS 2118.1, AS 2419.1, AS/NZS 3000) and each state's adoption records, with its answer register, the exception desk the business runs, which issues the exception_id
- Evidence:
- self-run, cited-answer 7 green, 1 with_us (2026-11-03)
Based on NFPA Research Assistant by Michal Sullivan. Rebuilt and maintained by AI Pathway.Show the original
This is Michal Sullivan’s own bot, not the version above, and it won’t pass the job along: NFPA Research Assistant. - Fire Round WatchListed, routable
Each morning, work out each site's next monthly, six-monthly and yearly fire service from its written schedule and last visit, draft bookings for a person to release, and flag anything overdue.
- Woken by:
- schedule.tick (schedule), document.received (webhook), exception.closed (webhook)
- Hands on:
- asset.service_due, evidence.filed, exception.raised
- Systems:
- the fire protection contractor's asset register of fire systems on each site, with each site's written routine service schedule, its dated rule store per state, and the document store the signed service reports are filed in (Simpro, a job sheet or a register the business keeps)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Fix BookListed, routable
Keep the fixes our techs find on site, and when a tech asks how we fixed a fault before, show them what was written on that job, or tell them we have no record.
- Woken by:
- job.completed (webhook), email.received (webhook), document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the job system that issues the job_id and names the tech on each job (ServiceM8, Simpro, Tradify, Fergus), whose id names each job's fix folder on the drive, the shared drive that holds the fix notes, voice memos, service manuals and procedures and issues the document_id (Google Drive or SharePoint), left where it is, the register on that tenant (one Sheet or SharePoint list: a row per source, owner a person, kind, edition and checksum), the task list the office runs (Google Tasks, Planner or a sheet), which issues the exception_id for each open question
- Evidence:
- self-run, knowledge-base 11 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Folder BriefListed, routable
Put every file in our messy shared folder on one register with an owner, catch the week one changes, and give me a one-screen brief of what's current, stale, open and changed.
- Woken by:
- document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the shared drive that holds the folder and issues the document_id (Google Drive or SharePoint), left where it is, the register on that tenant (one Sheet or SharePoint list: a row per source, owner a person, kind, edition and checksum), the task list the office runs (Google Tasks, Planner or a sheet), which issues the exception_id for each open question
- Evidence:
- self-run, knowledge-base 11 green, 1 with_us (2026-11-03)
Based on Drive Docs Memory by Markus. Rebuilt and maintained by AI Pathway.Show the original
This is Markus’s own bot, not the version above, and it won’t pass the job along: Drive Docs Memory. - Gas TallyListed, routable
Match the refrigerant log for every cylinder and van to the gas charged and recovered on each job, and list what does not reconcile for the licence holder before the reporting date.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- Simpro (the job system that issues the job id and holds the refrigerant charged and recovered on each job, against the cylinder used), the cylinder log (one line per cylinder per job, by van, as the technician weighed it on the van scale, keyed by the job id and the cylinder id)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Goods MatchListed, routable
Hold every supplier invoice against its purchase order and what was actually received, catch duplicates, and tell finance which queue each one is in.
- Woken by:
- bill.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- bill.checked, exception.raised
- Systems:
- Xero or MYOB (the ledger that issues the bill_id for each supplier invoice), the purchase order and goods-received register, keyed by order_id (Xero purchase orders, or a Google Sheets register), the document store holding the invoice copies and written variation approvals (Google Drive, or the Gmail attachment)
- Evidence:
- self-run, invoice-check 7 green, 1 with_us (2026-11-03)
Based on Match vendor invoices with POs and GRNs in Google Sheets and notify Finance via Gmail by Fahim Jilani. Rebuilt and maintained by AI Pathway.Show the original
This is Fahim Jilani’s own bot, not the version above, and it won’t pass the job along: Match vendor invoices with POs and GRNs in Google Sheets and notify Finance via Gmail. - Handbook DeskListed, routable
Answer staff and manager questions about our employee handbook, HR policies and work rules by quoting the clause and its edition, or hand the question to the HR owner.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- answer.sent, exception.raised
- Systems:
- the mail system that issues the message_id the HR question arrived on and the reply went out on (Gmail, Outlook), the business's own rules library: the employee handbook, HR policies and work rules, and any award or National Employment Standards extract it has loaded, held as clauses with an edition, an Australian state or territory (or AU) and an effective date, with its answer register, the exception desk the business runs, which issues the exception_id
- Evidence:
- self-run, cited-answer 7 green, 1 with_us (2026-11-03)
Based on HR Bot by Goose. Rebuilt and maintained by AI Pathway.Show the original
This is Goose’s own bot, not the version above, and it won’t pass the job along: HR Bot. - Handover ManualListed, routable
At practical completion, put the O&M manual together from the job's asset list, certificates and records, list anything missing, and hold it for the project manager to release.
- Woken by:
- job.completed (webhook), document.received (webhook), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system that issues the job_id the manual belongs to, with its installed asset list (Simpro, ServiceM8 or Tradify's job export), the document store that issues the document_id of each certificate, warranty and record in the job folder, and holds the drafted manual (SharePoint, OneDrive or Google Drive), the exception desk the business runs, holding each held manual with its named owner
- Evidence:
- self-run, rejected-pack 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Hours AuditListed, routable
Every week before the pay run, check the Square timecards against the roster and the award edition, put anything odd in front of its owner, and export only what a person released.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- Square Team (team members, scheduled shifts with the job each is for, and timecards), the business's rule store holding each award edition as a dated row, the business's Australian payroll system, which issues the export batch id, the exception desk the business runs (the anomaly queue)
- Evidence:
- self-run, timesheet-check 10 green, 1 with_us (2026-11-03)
Based on Square Crew, Payroll & HR Helper by Anatoliy Belyshev. Rebuilt and maintained by AI Pathway.Show the original
This is Anatoliy Belyshev’s own bot, not the version above, and it won’t pass the job along: Square Crew, Payroll & HR Helper. - Hours CheckListed, routable
When the pay week closes, check the crew's hours against the roster, their jobs and the dated award, put the odd ones in front of a named person, and send nothing to payroll until someone releases it.
- Woken by:
- schedule.tick (schedule), job.updated (webhook), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system that issues the job_id and holds the allocations and roster (ServiceM8, Simpro, Tradify, Fergus or similar), the payroll system that takes one export per period and returns its id (Xero Payroll, Employment Hero or MYOB), the exception desk the business runs, for the anomaly queue
- Evidence:
- self-run, timesheet-check 10 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Inbox DeskListed, routable
Each weekday, read the shared business inbox, file every message against its job or supplier, and hold every real reply for a named person.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- exception.raised
- Systems:
- the mail system that issues the message_id (the shared Gmail or Outlook mailbox), the job system or ledger that holds the job and supplier records messages are filed against, the exception desk the business runs, holding the queue table and its items
- Evidence:
- self-run, inbox-triage 9 green, 1 with_us (2026-11-03)
Based on Inbox Triage by Cristopher Guido. Rebuilt and maintained by AI Pathway.Show the original
This is Cristopher Guido’s own bot, not the version above, and it won’t pass the job along: Inbox Triage. - Install BookListed, routable
When an install is signed off, put the unit and its warranty on our books from the commissioning record, work out its first service date from our schedule, and remind the customer once.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- job.created, exception.raised
- Systems:
- the job system that issues the job_id (ServiceM8, Simpro, Fergus, Jobber or AroFlo: the completed install or service job and the equipment the technician recorded on it), the asset register that issues the asset_id (each installed unit, with its service records and the reminder history kept against it)
- Evidence:
- self-run, next-service 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Intercompany MatchListed, routable
Each month end, match what our group companies say they owe each other across their Xero files, list every difference with both figures, and fix one only once a named person accepts it.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- Xero, the issuing company's file (the intercompany invoice and its InvoiceID), Xero, the receiving company's file (the bill entered for the same charge, carrying the issuer's InvoiceID as its reference)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Invoice PairListed, routable
Every morning, check our Harvest invoices against the ledger by invoice id, show each difference with both values, and fix one only once a named person accepts it.
- Woken by:
- schedule.tick (schedule), payment.received (webhook), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- Harvest (issues the invoice and its id), Balances (the ledger that records payment against the Harvest invoice id)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-03)
Based on Invoice Mirror by Jerrod Tuck. Rebuilt and maintained by AI Pathway.Show the original
This is Jerrod Tuck’s own bot, not the version above, and it won’t pass the job along: Invoice Mirror. - Job FilesListed, routable
Find the permit, approval and job paperwork on our drive and give back the exact page of the exact file, knowing it is the current copy and who owns it.
- Woken by:
- document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system that issues the job_id (ServiceM8, Simpro, Tradify, Fergus), whose id names each job's folder on the drive, the shared drive that holds the job folders and company files and issues the document_id (Google Drive or SharePoint), left where it is, the register on that tenant (one Sheet or SharePoint list: a row per source, owner a person, kind, edition and checksum), the task list the office runs (Google Tasks, Planner or a sheet), which issues the exception_id for each open question
- Evidence:
- self-run, knowledge-base 11 green, 1 with_us (2026-11-03)
Based on File Crawler by Duncan Waring. Rebuilt and maintained by AI Pathway.Show the original
This is Duncan Waring’s own bot, not the version above, and it won’t pass the job along: File Crawler. - Job HoursListed, routable
When a tech closes a job or the pay week ends, check every hour against the job it was booked to, put the odd ones in front of their owner, and export to payroll only what a person released.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system that issues the job_id and holds the allocations, the roster and the techs' time entries (ServiceM8, Simpro, Tradify, Fergus or similar), the business's rule store holding each award edition as a dated row, the Australian payroll system that takes one export per pay period and returns its id (Xero Payroll, Employment Hero, KeyPay or MYOB), the exception desk the business runs, for the anomaly queue
- Evidence:
- self-run, timesheet-check 10 green, 1 with_us (2026-11-03)
Based on Kairos · Timesheet Manager by ᑕᕼIᑕᗩᘜO MAGA. Rebuilt and maintained by AI Pathway.Show the original
This is ᑕᕼIᑕᗩᘜO MAGA’s own bot, not the version above, and it won’t pass the job along: Kairos · Timesheet Manager. - Job SheetListed, routable
When the tech finishes on site, fill in the job card from what they sent, priced only from our price book, and save it to the job once they reply yes.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- job.completed, exception.raised
- Systems:
- ServiceM8 or Simpro (the job, its assigned tech, its quote, its materials, notes and attachments), the business's own price book (ServiceM8 materials, the Simpro catalogue or the Xero item list), the exception desk the business runs
- Evidence:
- self-run, job-close 5 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Job WIPListed, routable
Every Monday, publish the job profit and work-in-progress report: each open job's quoted value, cost to date and invoiced to date, every figure with its source and the time it was read.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (Simpro, ServiceM8, Fergus and the like): each open job's accepted quote plus approved variations, and its cost to date (labour at cost rate, materials and subcontract bills against the job), the ledger (Xero or MYOB): invoices raised against each job's tracking category to date, less credit notes, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Jobs WeeklyListed, routable
Every Monday, publish our jobs report: jobs finished last week, jobs still open by how old they are, and staff hours by task, every figure with its source and the time it was read.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (ServiceM8, Simpro, Fergus and the like): jobs completed in the week and open jobs by age from their created date, the timesheets (the job system's own time clock, or the payroll timesheets): approved staff hours booked to each task, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Late Rent DeskListed, routable
For a landlord with 1 to 50 doors: each day, find who is really behind on rent, text only them, and hand notices, fees and hardship to a person.
- Woken by:
- schedule.tick (schedule), rent.overdue (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the property management system or rent ledger that issues the tenancy_id (its tenancy ledger, rule store and message log)
- Evidence:
- self-run, rent-arrears 5 green, 1 with_us (2026-11-03)
Based on LeaseLord by Jonah. Rebuilt and maintained by AI Pathway.Show the original
This is Jonah’s own bot, not the version above, and it won’t pass the job along: LeaseLord. - Lead PaybackListed, routable
Each month, publish which ad campaign or lead source our jobs came from and what we invoiced on them, every figure traced to the job and invoice records.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (Simpro, ServiceM8, Tradify, Fergus and the like): the lead source field and accepted quote on each job_id, the ledger (Xero or MYOB): invoices and credit notes raised in the month, each carrying its job_id in the reference, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Lead SortListed, routable
Sort the trade office inbox, voicemails and web-form leads included, onto the job or supplier by id, and hold every real reply for a named person.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the shared office mailbox (Microsoft 365 or Google Workspace) that issues the message_id, where voicemail and website enquiry-form notifications land, the job system that issues the job_id messages are filed against (ServiceM8 or Simpro), the ledger that holds supplier records (Xero), the exception desk the business runs, holding the queue table and its items
- Evidence:
- self-run, inbox-triage 9 green, 1 with_us (2026-11-03)
Based on Contractor Front Desk by Thuong P. Nguyen. Rebuilt and maintained by AI Pathway.Show the original
This is Thuong P. Nguyen’s own bot, not the version above, and it won’t pass the job along: Contractor Front Desk. - Lease DatesListed, routable
Keep every commercial lease's rent review and option dates worked out from the lease and the state's rules, draft the notice in time for the manager to serve, and file the served copy.
- Woken by:
- schedule.tick (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the property management system that issues the tenancy_id (its commercial lease register, dated rule set and the document store served notices are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Licence WatchListed, routable
Each morning, work out when our licences and insurance policies run out from each state's rule, remind the named person with a Done link, and count it renewed only when the new certificate is filed.
- Woken by:
- schedule.tick (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the business's licence register (each contractor licence, worker trade licence and insurance policy with its issue or renewal date, the dated rule set per state, and the document store renewed licences and certificates of currency are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-03)
Based on Send license and insurance renewal reminders by SMS with Twilio by Michael Matthews. Rebuilt and maintained by AI Pathway.Show the original
This is Michael Matthews’s own bot, not the version above, and it won’t pass the job along: Send license and insurance renewal reminders by SMS with Twilio. - Loan IntakeListed, routable
Turn every lead and client call into the one client file in our CRM, chase each missing figure or document as an owned task, and hold the file for a broker to approve.
- Woken by:
- call.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the broker's CRM that issues the client file id (the client file, its deal record and its tasks), the network's dated lender-panel library, where a named person accepts each clause
- Evidence:
- self-run, advice-file 10 green, 1 with_us (2026-11-03)
Based on Qualify mortgage leads and collect documents with Gemini, Gmail, Drive, Telegram, and Supabase by Shashwat Singh. Rebuilt and maintained by AI Pathway.Show the original
This is Shashwat Singh’s own bot, not the version above, and it won’t pass the job along: Qualify mortgage leads and collect documents with Gemini, Gmail, Drive, Telegram, and Supabase. - Lodgement WatchListed, routable
Keep every client's BAS, IAS and payroll tax due dates worked out from the ATO and state rules, file the lodgement receipts, and put anything late in front of a named person.
- Woken by:
- schedule.tick (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the practice's obligation register (its client lodgement calendar, dated rule set and the document store lodgement receipts are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Manual DeskListed, routable
When a tech on site asks about the unit on their job, show them the page of its install or service manual that covers it, with page and revision, or say we hold no manual for it.
- Woken by:
- email.received (webhook), job.created (webhook), document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system that issues the job_id and records the unit make and model on each job (ServiceM8, Simpro, Tradify, Fergus), the shared drive that holds the manufacturers' install and service manuals, commissioning videos and the office's procedures and issues the document_id (Google Drive or SharePoint), left where it is, the register on that tenant (one Sheet or SharePoint list: a row per source, owner a person, kind, revision and checksum), the task list the office runs (Google Tasks, Planner or a sheet), which issues the exception_id for each open question
- Evidence:
- self-run, knowledge-base 11 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Margin WatchListed, routable
Every Friday, list the jobs where what we have actually spent on labour and materials is eating the margin we quoted, name the lines that caused it, and leave what to do about each job to the owner.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (ServiceM8, Simpro, Tradify, Fergus and the like): the accepted quote's labour and material lines, time booked to the job and the job's margin to date, against each job_id, the ledger (Xero or MYOB): supplier bills coded to the job, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Meeting NotesListed, routable
After each client meeting, file what the client told us (facts, preferences, standing instructions) on their record as suggestions, for a partner to accept or reject.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, report.published, exception.raised
- Systems:
- the practice management system that issues the job_id and the client id on it (for example Xero Practice Manager or FYI), the practice's client memory list on its own Microsoft 365 or Google Workspace, with an approvals list only approvers can write to
- Evidence:
- self-run, client-memory 5 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Month PackListed, routable
Each month, put every client's management pack (profit and loss, balance sheet, cash, key ratios) in their folder, every figure sourced and as-of, for the partner to send.
- Woken by:
- schedule.tick (schedule)
- Hands on:
- report.published, exception.raised
- Systems:
- each client's ledger (Xero or MYOB): profit and loss, balance sheet and the executive summary ratios for the month, each client's bank statement: the operating account's closing balance at month end, the practice's client folder the pack is published into (SharePoint or Google Drive), which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Notice CheckListed, routable
Before a breach notice for unpaid rent goes to a tenant, check it against the ledger and the state's dated rule, hold it for a named person with its dates, and check it again when they release it.
- Woken by:
- schedule.tick (schedule), rent.overdue (webhook), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the property management system that issues the tenancy_id (PropertyMe, Console Cloud or similar): its tenancy ledger, dated rule store, notice drafts and message log
- Evidence:
- self-run, rent-arrears 5 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Open Home DeskListed, routable
After each open home, follow up everyone who said yes at sign-in with a message I approved, sort their replies, and draft the vendor's report from what buyers actually said.
- Woken by:
- document.received (webhook), email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the sign-in register the agency CRM exports, or the typed-up paper sheet, which issues the document_id, the agent's mail system, which holds the approved drafts, the sends and the replies (message_id), the report store the agent and the vendor open, which issues the report_id per version
- Evidence:
- self-run, open-home-feedback 9 green, 1 with_us (2026-11-03)
Based on Mary (Realtor Assistant) by Rick. Rebuilt and maintained by AI Pathway.Show the original
This is Rick’s own bot, not the version above, and it won’t pass the job along: Mary (Realtor Assistant). - Ops MapListed, routable
Keep one accepted map of how the business runs, step by step, from its own procedures, and name a person when two procedures disagree or one is replaced.
- Woken by:
- document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the document store that issues the document_id for each procedure and edition (SharePoint or Drive), Xero, for the contact id of each supplier the procedures name, the exception desk the business runs, which issues the exception_id
- Evidence:
- self-run, knowledge-graph 10 green, 1 with_us (2026-11-03)
Based on OS: Ontology Stack by Damiano Redemagni. Rebuilt and maintained by AI Pathway.Show the original
This is Damiano Redemagni’s own bot, not the version above, and it won’t pass the job along: OS: Ontology Stack. - Order ReleaseListed, routable
Turn each job's material list into one purchase order per supplier, and hold any order over the spending limit, or to an unapproved supplier, until a named person releases it.
- Woken by:
- schedule.tick (schedule), job.updated (webhook), document.received (webhook), exception.closed (webhook)
- Hands on:
- order.sent, delivery.recorded, exception.raised
- Systems:
- the job system that issues the job_id and holds its material list (ServiceM8, Simpro, Tradify, Fergus or a job sheet), the supplier portal or job-system purchasing that issues each order's external id
- Evidence:
- self-run, material-order 9 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Outgoings BookListed, routable
File each managed property's council rates, water, strata levy and power bills against that property by the account number printed on them, and list what falls due when for a person to pay.
- Woken by:
- document.received (webhook), email.received (webhook), exception.closed (webhook), schedule.tick (schedule)
- Hands on:
- evidence.filed, report.published, exception.raised
- Systems:
- the property management system that issues each property record and holds its account numbers (rates assessment, water account, strata plan and lot, electricity or gas NMI), e.g. PropertyMe or Console Cloud, the agency's document store, where each original is kept unaltered
- Evidence:
- self-run, document-filing 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Parts CheckListed, routable
The afternoon before, check every part tomorrow's jobs need against the van and shelf counts, flag stale counts, and raise shortfalls for ordering, never substituting.
- Woken by:
- schedule.tick (schedule), job.updated (webhook), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system that issues the job_id and holds tomorrow's dispatched board, each job's accepted quote lines and materials (ServiceM8, Simpro, AroFlo, Fergus, or a Tradify export into the sheet), the stock sheet or job-system stock locations holding each van's count with the time it was counted, and the shelf, Material Order's path (the purchasing step that prices, holds and issues the purchase order id), the exception desk the business runs (a task list or a sheet)
- Evidence:
- self-run, parts-ready 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Permit AnswersListed, routable
Answer the office's permit, inspection, zoning and building code questions from the council and state rules we hold, citing the clause, or hand them to a named person.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- exception.raised
- Systems:
- the mail system that issues the message_id the question arrived on (Gmail, Outlook), the business's own clause library of council planning schemes, building regulations and inspection schedules, with its answer register, the exception desk the business runs, which issues the exception_id
- Evidence:
- self-run, cited-answer 7 green, 1 with_us (2026-11-03)
Based on CITY HALL by John Christian. Rebuilt and maintained by AI Pathway.Show the original
This is John Christian’s own bot, not the version above, and it won’t pass the job along: CITY HALL. - Plant WatchListed, routable
Remind us when each piece of our plant and equipment is due its inspection, draft the booking for a person to release, and count it done only when the completed check is filed on the item.
- Woken by:
- schedule.tick (schedule), document.received (webhook), exception.closed (webhook)
- Hands on:
- asset.service_due, evidence.filed, exception.raised
- Systems:
- the business's plant register (each item of plant and equipment with its state, the date its last completed check was filed, the dated inspection rule set per state, and the document store inspection reports and test and tag records are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- PO MatchListed, routable
Match each emailed supplier invoice against its purchase order and what was received, leave clean ones as draft bills for a person, and raise every mismatch in dollars.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- bill.checked, exception.raised
- Systems:
- Xero (the ledger that issues the bill_id and holds the purchase orders), Gmail (the inbox the invoice arrives in, which issues the message_id), the receipt record against each purchase order (delivery dockets or quantities marked complete), the document store where written variation approvals live
- Evidence:
- self-run, invoice-check 7 green, 1 with_us (2026-11-03)
Based on Automate 3-way invoice matching from Gmail to Xero with Slack and Teams alerts by Jitesh Dugar. Rebuilt and maintained by AI Pathway.Show the original
This is Jitesh Dugar’s own bot, not the version above, and it won’t pass the job along: Automate 3-way invoice matching from Gmail to Xero with Slack and Teams alerts. - Policy DeskListed, routable
Answer staff and customer support, HR and compliance questions only from the policy pack we have approved, citing the clause and its edition, or hand the question to a named person.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- answer.sent, exception.raised
- Systems:
- the mail system that issues the message_id the question arrived on and the reply went out on (Gmail, Outlook), the business's own approved policy pack (staff handbook, leave, refunds and returns, privacy, complaints) held as a clause library with editions, state or territory and effective dates, and its answer register, the exception desk the business runs, which issues the exception_id
- Evidence:
- self-run, cited-answer 7 green, 1 with_us (2026-11-03)
Based on Claim Cage by Andy Mccutcheon. Rebuilt and maintained by AI Pathway.Show the original
This is Andy Mccutcheon’s own bot, not the version above, and it won’t pass the job along: Claim Cage. - Portal MatchListed, routable
Each weekday, check every job's status in Simpro against the client's work-order portal by work-order number, show each difference with both values, and fix one only once a person accepts it.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, job.updated, exception.raised
- Systems:
- Simpro (the job carries the client's work-order number; owns the job status and the invoiced total), the client's work-order portal: a real estate agency's maintenance system, a facilities manager or a CMMS (issues the work-order number; owns the attend-by date and the not-to-exceed limit)
- Evidence:
- self-run, two-records 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Practice DeskListed, routable
Sort everything that lands in the practice inbox onto the right client job or supplier, give each one an owner and a deadline, and hold every reply for the owner to release.
- Woken by:
- email.received (webhook), schedule.tick (schedule)
- Hands on:
- job.updated, exception.raised
- Systems:
- the practice's shared mailbox (Microsoft 365 or Google Workspace), which issues the message_id, the practice manager that issues the client engagement job_id (for example Xero Practice Manager), the practice's own ledger, for supplier records (for example Xero)
- Evidence:
- self-run, inbox-triage 9 green, 1 with_us (2026-11-03)
Based on Tax Firm OS by Amervim Bonano. Rebuilt and maintained by AI Pathway.Show the original
This is Amervim Bonano’s own bot, not the version above, and it won’t pass the job along: Tax Firm OS. - Prestart DeskListed, routable
File each daily vehicle pre-start or site safety check on its vehicle or job, and put every failed item in front of the person our table names, with a clock, for them to sort and tick off.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised, report.published
- Systems:
- the job system (Simpro, or ServiceM8, AroFlo or Fergus) that issues the job_id for a site check and the asset_id for a vehicle kept as plant and equipment, where each completed check is filed as an attachment, the ledger that issues the invoice_id (Xero), for items other surfaces raise against an invoice, the checks mailbox (Gmail or Outlook) the pre-start form app emails each completed check into, which issues the message_id, the exception desk the business runs (a sheet with Raise and Routing tabs, a SharePoint list, or Office Voice's queue), which issues the exception_id
- Evidence:
- self-run, exception-desk 6 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Price CreepListed, routable
Check every line price on each supplier bill against the price we agreed with that supplier, flag every rise in dollars before anyone approves it, and put it in front of a named person.
- Woken by:
- bill.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- bill.checked, exception.raised
- Systems:
- Xero or MYOB (the ledger that issues the bill_id and holds the supplier bills), the agreed supplier price list or trade account schedule of rates, by its reference, in the ledger or the job system (Simpro, ServiceM8 or similar), the document store holding the bill PDFs and any written approval for an item not on the price list
- Evidence:
- self-run, invoice-check 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Price SheetListed, routable
Before each appraisal, draft the vendor's one-page price evidence from comparable sales chosen by written rules, each sourced, and hold it for the agent to approve.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the agency's listing system, which issues the listing_id for the appraisal and holds the subject property, the recorded sales source the agency already licenses, the document store the approved page and its record of what was shown are published into, which issues the report_id
- Evidence:
- self-run, price-one-pager 9 green, 1 with_us (2026-11-03)
Based on CMA Specialist Bot by Daniel Ledo. Rebuilt and maintained by AI Pathway.Show the original
This is Daniel Ledo’s own bot, not the version above, and it won’t pass the job along: CMA Specialist Bot. - Progress DeskListed, routable
Each month, draft every builder contract's progress claim from the schedule, the project manager's site walk and the signed variations, and hold it for the project manager to sign and serve.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the builder's contract record (Simpro, Buildxact, a SharePoint list or the claims sheet the builder runs) that holds each contract's sum, schedule of values and what was claimed before, the project manager's site assessment per line per month, the signed variations and the waiver acceptance, and issues the contract record's id (carried as job_id) and the held draft's id (carried as report_id)
- Evidence:
- self-run, progress-claim-draft 8 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Quote KeeperListed, routable
Keep every quote we send on the register and follow each quiet customer up on our cadence and in our wording until they decide, then hand a no, a dispute or the cap to a person.
- Woken by:
- schedule.tick (schedule), quote.sent (webhook), quote.accepted (webhook), quote.declined (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the job system that issues the quote_id and job_id (ServiceM8, Simpro, or for Tradify a register kept beside it), the exception desk the business runs (a sheet or a task list that issues the exception_id)
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-03)
Based on The Follow-Up Machine — Quotes Don't Die in the Inbox Anymore by News Gurus. Rebuilt and maintained by AI Pathway.Show the original
This is News Gurus’s own bot, not the version above, and it won’t pass the job along: The Follow-Up Machine — Quotes Don't Die in the Inbox Anymore. - Quote NudgeListed, routable
Each morning, find the flooring quotes customers have not answered, draft a low-pressure nudge for the rep to send within the cap, and hand any no or dead quote to a named person.
- Woken by:
- schedule.tick (schedule), quote.sent (webhook), quote.accepted (webhook), quote.declined (webhook), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the job system that issues the quote_id and job_id (ServiceM8, Simpro, or a quote register kept beside Tradify, which has no public API), Gmail or Outlook (the rep's outbox for the drafted nudge, and the customer's reply by message_id), the exception desk the business runs (a sheet or a task list that issues the exception_id)
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-03)
Based on Quote Closer by Mark G. Rebuilt and maintained by AI Pathway.Show the original
This is Mark G’s own bot, not the version above, and it won’t pass the job along: Quote Closer. - Rack WatchListed, routable
Keep each client warehouse's AS 4084 racking inspection dated from our rules, draft the booking, file every damage finding against its bay, and draft the repair summary for us to send.
- Woken by:
- schedule.tick (schedule), document.received (webhook), exception.closed (webhook)
- Hands on:
- asset.service_due, evidence.filed, exception.raised
- Systems:
- the racking inspector's register of client warehouse racking installations (its dated rule store per state, and the document store the signed inspection reports are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Receipt ChaseListed, routable
Each weekday, find the bank and card lines in Xero with no receipt, ask the person who spent each one for it, attach it when it comes back, and hand a no or a silence to the bookkeeper.
- Woken by:
- schedule.tick (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- Xero, where each spend line in the bank feed has its bank transaction id and the receipt is attached to that line, the receipt register kept beside it, one open item per line with no receipt, owed by the person who spent it, the practice's mailbox (Gmail or Outlook), where a receipt sent back on the chase thread arrives with its message id
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Renewal WatchListed, routable
Keep our licences, insurances and site services on a calendar worked out from each state's rules, file the certificates when they come in, and put anything late in front of a named person.
- Woken by:
- schedule.tick (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the business's obligation register (its compliance calendar, rule set and the document store certificates are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-03)
Based on Duly by Logan Brown. Rebuilt and maintained by AI Pathway.Show the original
This is Logan Brown’s own bot, not the version above, and it won’t pass the job along: Duly. - Rent WatchListed, routable
Every day, work out which tenancies are really behind on rent, chase only those, and hand anything past a reminder to a named person.
- Woken by:
- schedule.tick (schedule), rent.overdue (webhook), exception.closed (webhook)
- Hands on:
- exception.raised
- Systems:
- the property management system that issues the tenancy_id (its tenancy ledger and message log)
- Evidence:
- self-run, rent-arrears 5 green, 1 with_us (2026-11-03)
Based on Landlord Ledger by Daniel Masarsky. Rebuilt and maintained by AI Pathway.Show the original
This is Daniel Masarsky’s own bot, not the version above, and it won’t pass the job along: Landlord Ledger. - Rental Safety WatchListed, routable
Keep every rental's smoke alarm, gas and hot water valve checks dated from the state's rules, draft the booking before each lapses for the property manager to release, and file the certificate.
- Woken by:
- schedule.tick (schedule), document.received (webhook), exception.closed (webhook)
- Hands on:
- asset.service_due, evidence.filed, exception.raised
- Systems:
- the property management system that issues each rental's asset_id and tenancy_id (its safety check register, dated rule set per state, and the document store the contractor's certificates are filed in)
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Repair BoardListed, routable
Send each triaged repair to a licensed trade at a time inside the resident's window, text the resident once, and hand what cannot be placed to the property manager.
- Woken by:
- job.created (webhook), job.updated (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- job.updated, exception.raised
- Systems:
- the property management system that issues the maintenance job_id (its work orders, trade panel and licence records)
- Evidence:
- self-run, dispatch-board 8 green, 1 with_us (2026-11-03)
Based on Miffy - Maintenance Triage by Miffy. Rebuilt and maintained by AI Pathway.Show the original
This is Miffy’s own bot, not the version above, and it won’t pass the job along: Miffy - Maintenance Triage. - Retention BookListed, routable
Keep the retention held on each contract, work out when each half is due back and when the defects period ends, and draft the release request for a named person to send.
- Woken by:
- schedule.tick (schedule), job.updated (webhook), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the job system that issues the job_id (Simpro, ServiceM8 or similar): the contract job, its practical completion date and retention terms, the exception desk the business runs, which issues the exception_id, the document store (Drive or SharePoint), where remittances and release certificates are filed against the job
- Evidence:
- self-run, compliance-calendar 7 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Review AskListed, routable
After each finished job, line up the same Google review message for every customer, one reminder then stop, hold jobs with an open callback or dispute, and a person releases each batch.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), email.received (webhook), job.updated (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the job system that issues the job_id and holds its status, callbacks, invoice dispute and complaint (ServiceM8, Simpro, Fergus, Jobber or AroFlo), the SMS or email account the business owns (the ask, the reminder and the reply, by message_id), the review record and the exception desk the business runs (a sheet or a list that issues the exception_id)
- Evidence:
- self-run, review-request 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Ring ListListed, routable
Every weekday morning, tell me who to ring today from my own database, why each one, with a short opener drafted, and nothing past the do-not-call flags.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the agency CRM, or the copied Contacts sheet, that holds each contact row, its last outcome and the do-not-contact register, the place the agent opens each morning (CRM tasks, the Today tab or a morning email), which issues the report_id for each day's list
- Evidence:
- self-run, database-reactivation 8 green, 1 with_us (2026-11-03)
Based on Realtor Morning Brief by Bryan Dunleavy. Rebuilt and maintained by AI Pathway.Show the original
This is Bryan Dunleavy’s own bot, not the version above, and it won’t pass the job along: Realtor Morning Brief. - Route PlanListed, routable
Each morning, suggest the order of every tech's jobs and which licensed tech takes each recurring visit so the vans drive less, and book only the lines the dispatcher accepts.
- Woken by:
- schedule.tick (schedule), job.created (webhook), job.updated (webhook), exception.closed (webhook)
- Hands on:
- job.updated, exception.raised
- Systems:
- the job system that issues the job_id and holds its schedule (ServiceM8, Simpro or Jobber), the tech licence register the business keeps
- Evidence:
- self-run, dispatch-board 8 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Safety Cert DeskListed, routable
When a smoke alarm and RCD job is done, draft the property's compliance pack from the tech's results for our licensed electrician to sign, and hold it if any result is missing.
- Woken by:
- job.completed (webhook), job.updated (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the job system that issues the job_id (ServiceM8, Simpro or similar: the completed job, its test form results and attachments), the asset register that issues the asset_id (each smoke alarm and RCD on the property, by the tag printed on it), the exception desk the business runs (a sheet, a task list or a ticket queue)
- Evidence:
- self-run, fire-service-pack-standard 11 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Seller BookListed, routable
Each morning, show me which past sellers and appraisals in my own database to text today and why, drafted for my OK, and keep every outcome and follow-up on the contact.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the agency CRM (Agentbox, VaultRE, Rex or similar), or the copied Contacts sheet, that holds each contact row, its last outcome and date, its texts and the do-not-contact register, the place the agent opens each morning (CRM tasks or the Today tab), which issues the report_id for each day's list of drafted texts
- Evidence:
- self-run, database-reactivation 8 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Seller WeeklyListed, routable
Every Monday, publish each seller a report on their listing: buyer enquiries, inspections and online views, every figure traced to its source, for the listing agent to send.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the agency's sales CRM (such as Rex, VaultRE or Agentbox) that holds buyer enquiries and online listing views, issuing the listing_id, the inspection register the agency keeps for open homes and private inspections, the agency's report store or vendor portal the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-03)
Based on Send weekly seller property reports from Google Sheets via Gmail by Christophe REVOIRE. Rebuilt and maintained by AI Pathway.Show the original
This is Christophe REVOIRE’s own bot, not the version above, and it won’t pass the job along: Send weekly seller property reports from Google Sheets via Gmail. - Service DueListed, routable
When a job is done, keep its equipment on our register, work out each unit's service and warranty dates from our schedule, draft reminders for us to release, and turn a yes into one booking request.
- Woken by:
- job.completed (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- asset.service_due, job.created, exception.raised
- Systems:
- the job system that issues the job_id (ServiceM8, Simpro, Fergus, Jobber or AroFlo) and the equipment register on it that issues the asset_id
- Evidence:
- self-run, next-service 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Sign-In Follow-UpListed, routable
Take the open-home sign-in sheet, follow up only the people who said yes with a message I approved, sort their replies, and draft the vendor's report from them.
- Woken by:
- listing.feedback_due (webhook), document.received (webhook), email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the open-home sign-in register, exported from the sign-in app or the agency CRM, or the paper sheet typed up, which issues the document_id and the listing_id each row belongs to, the agent's mail and SMS sender, which holds the approved drafts, the sends and the replies (message_id), the report store the agent and the vendor open, which issues the report_id per version
- Evidence:
- self-run, open-home-feedback 9 green, 1 with_us (2026-11-03)
Based on Automate Real Estate Open House Follow-ups with SignSnapHome, HubSpot, and Twilio by Kaden Reese. Rebuilt and maintained by AI Pathway.Show the original
This is Kaden Reese’s own bot, not the version above, and it won’t pass the job along: Automate Real Estate Open House Follow-ups with SignSnapHome, HubSpot, and Twilio. - Site DropListed, routable
File every site photo, chat update and bit of paperwork the crew send onto the right job by the job number they wrote on it, and park anything with no clear job for a named person.
- Woken by:
- document.received (webhook), exception.closed (webhook), schedule.tick (schedule)
- Hands on:
- evidence.filed, report.published, exception.raised
- Systems:
- the job system that issues the job_id and the purchase order (order_id) each item is filed on, e.g. Simpro, ServiceM8, AroFlo or Fergus, the crew chat or office mobile the photos and updates come in on, e.g. a WhatsApp group exported to the office inbox, Xero, for customer and supplier contacts
- Evidence:
- self-run, document-filing 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Site OrdersListed, routable
Turn the build's material list into one purchase order per supplier, from stock first and the supplier's own prices, and match every delivery docket back.
- Woken by:
- schedule.tick (schedule), job.updated (webhook), document.received (webhook), exception.closed (webhook)
- Hands on:
- exception.raised
- Systems:
- the job system that issues the job_id and holds its material list, the supplier portal or job-system purchasing that issues each order's external id
- Evidence:
- self-run, material-order 9 green, 1 with_us (2026-11-03)
Based on Foreman by Jonah. Rebuilt and maintained by AI Pathway.Show the original
This is Jonah’s own bot, not the version above, and it won’t pass the job along: Foreman. - Site Test CheckListed, routable
When a fire service visit is done, check each test against the site's asset register, hold any with no tagged asset or tag photo, and draft the site report for the person who signs.
- Woken by:
- job.completed (webhook), job.updated (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system that issues the job_id (Simpro, ServiceM8 or similar: the completed service visit, its test results and attachments), the asset register that issues the asset_id (every extinguisher, hydrant, fire door and exit light on the site, by the tag printed on it), the document store that issues the report_id (the site's pack folder in SharePoint or Google Drive), the exception desk the business runs (a sheet, a task list or a ticket queue)
- Evidence:
- self-run, fire-service-pack-standard 11 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Software AuditListed, routable
Each month, publish what we pay for software on bills and company cards, with owners and renewals due, and flag duplicates and unused ones to a named person, every figure sourced.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the ledger (Xero or MYOB): supplier bills and company card spend coded to the software subscriptions account, the software register the office keeps (a SharePoint list or Google Sheet): each subscription with its named owner, renewal date and whether it is still used, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Spend WatchListed, routable
Every Monday, publish the builder's spend report from the job system and the ledger, every figure with its definition, source and as-of time, and say so when one cannot be read.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (Buildertrend, or Simpro and the like): supplier bills, subcontractor invoices, variations and bills awaiting approval, against each job, the ledger (Xero or MYOB): bills posted with a job tracking category, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-03)
Based on Buildertrend Invoice Desk by Brian Payton. Rebuilt and maintained by AI Pathway.Show the original
This is Brian Payton’s own bot, not the version above, and it won’t pass the job along: Buildertrend Invoice Desk. - Starter PackListed, routable
Chase each new starter for the TFN declaration, super choice, bank details and work rights evidence they still owe, file each as it arrives, and hold the pack for payroll to set up.
- Woken by:
- schedule.tick (schedule), email.received (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the payroll system (Xero Payroll, KeyPay or MYOB), where each new starter has an employee record id before their first pay, the starter register kept beside it, one open item per document a starter still owes against their employee record, owed by the starter, the business's mailbox (Gmail or Outlook) and document store, where a document sent back on the chase thread or through the item's upload link arrives with its message id
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Sub Pay CheckListed, routable
Before a subbie's payment claim is approved, check their licence, insurance, cover and statements are on file and current, file each one, and hold the payment for a named person.
- Woken by:
- bill.received (webhook), email.received (poll), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, bill.checked, exception.raised
- Systems:
- Xero (the subcontractor's bill, which issues the bill_id), Gmail (the message each statement or certificate arrived on), Google Drive (the document store that issues each document_id), a Google Sheet as the exception desk (exception_id, exception_owner)
- Evidence:
- self-run, rejected-pack 9 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- SWMS DeskListed, routable
Draft each job's SWMS or risk assessment from its scope and our approved templates, list who on the crew has not signed, and hold the pack until the supervisor accepts it.
- Woken by:
- job.created (webhook), job.updated (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system that issues the job_id the pre-start pack belongs to, with its scope, site, start date, supervisor and crew (Simpro, ServiceM8 or Tradify's job export), the document store that holds the approved SWMS and risk assessment templates and receives the accepted pre-start pack (SharePoint, OneDrive or Google Drive), the exception desk the business runs, holding each held or failed pre-start pack with its named owner
- Evidence:
- self-run, rejected-pack 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Task ClockListed, routable
Keep one list of office follow-up tasks on each job, quote or invoice, with an owner and due time from our table, nudge once when one goes late, and leave ticking off to a person.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- exception.raised, report.published
- Systems:
- the job system that issues the job_id (ServiceM8), which each task is read back against, the ledger that issues the invoice_id or quote_id (Xero), for tasks about an invoice or a quote, the task list the business runs (a sheet with Tasks and Routing tabs, a SharePoint list, or Office Voice's exception queue), which issues the exception_id, the office's email or Teams channel, where the morning list lands
- Evidence:
- self-run, exception-desk 6 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Tenant InboxListed, routable
Read the agency's shared inbox, file every tenant, landlord and tradie message against its tenancy, work order or creditor, and hand each tenant complaint whole to its property manager.
- Woken by:
- email.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the mail system that issues the message_id (the agency's shared Gmail or Outlook mailbox), the property management system that issues the tenancy_id and holds the maintenance work orders and creditor records messages are filed against (PropertyMe, Console Cloud or similar), the exception desk the agency runs, holding the queue table and its items
- Evidence:
- self-run, inbox-triage 9 green, 1 with_us (2026-11-03)
Based on Triage tenant complaints with GPT-4.1, Slack, email and Google Sheets by Hyrum Hurst. Rebuilt and maintained by AI Pathway.Show the original
This is Hyrum Hurst’s own bot, not the version above, and it won’t pass the job along: Triage tenant complaints with GPT-4.1, Slack, email and Google Sheets. - Test Sheet CheckListed, routable
When a job's test result sheet comes in, check every test is filled in and in range before the certificate is written, and put any failed or blank test in front of the licensed electrician.
- Woken by:
- email.received (webhook), job.completed (webhook), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the job system that issues the job_id the test sheet belongs to (ServiceM8, Simpro or Tradify's job export), the mail system that issues the message_id the test sheet arrived on (the office's Gmail or Outlook mailbox), the document store that holds the filed original sheet (SharePoint, OneDrive or Google Drive), the exception desk the business runs, holding each stopped test sheet with its named owner
- Evidence:
- self-run, rejected-pack 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Threshold WatchListed, routable
Every Monday, check job margin, debtors and cash, and when one has moved past the line we set since last week, tell the person we named, with both weeks' figures and where they came from.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the job system (Simpro, ServiceM8 and the like): gross margin on jobs completed in the week, read only, the ledger (Xero or MYOB): debtors outstanding, debtors over sixty days and the reconciled bank balance, read only, the system the report is published into, which issues the report_id
- Evidence:
- self-run, recurring-report 9 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
- Van BoardListed, routable
Turn each service work order into a dispatch package: verified address, a licensed tech at a time that fits, customer and tech told once, the rest handed to the dispatcher.
- Woken by:
- job.created (webhook), job.updated (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- job.updated, exception.raised
- Systems:
- the job system that issues the job_id and holds its schedule (ServiceM8, Simpro or Jobber), the tech licence register the business keeps
- Evidence:
- self-run, dispatch-board 8 green, 1 with_us (2026-11-03)
Based on Claire by Thomas Matteson. Rebuilt and maintained by AI Pathway.Show the original
This is Thomas Matteson’s own bot, not the version above, and it won’t pass the job along: Claire. - Van StockListed, routable
Reserve what the van and store already hold for each job, order only the shortfall from the approved wholesaler at catalogue price, and match every docket back.
- Woken by:
- schedule.tick (schedule), job.updated (webhook), document.received (webhook), exception.closed (webhook)
- Hands on:
- order.sent, delivery.recorded, exception.raised
- Systems:
- the job system that issues the job_id, holds its material list and its van and store stock (ServiceM8, Simpro, Tradify, Fergus or similar), the wholesaler portal or job-system purchasing that issues each order's external id
- Evidence:
- self-run, material-order 9 green, 1 with_us (2026-11-03)
An original build by AI Pathway.
- Variation ChaseListed, routable
Each weekday, chase the signature on every variation the office has approved, stop the day it comes back signed, and hand a no or a silent party to a named person.
- Woken by:
- schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- evidence.filed, exception.raised
- Systems:
- the job system's variation register, one open item per approved variation awaiting signature on the job (Simpro, ServiceM8 or a Google Sheet kept beside the job system), which issues the job_id and the item id, the office mailbox (Gmail or Outlook) the signed variation comes back to, which issues the message_id
- Evidence:
- self-run, follow-up 10 green, 1 with_us (2026-11-03)
Based on Review, approve, and chase subcontractor change orders with forms, DeepSeek, Gmail, and Google Sheets by Khaisa Studio. Rebuilt and maintained by AI Pathway.Show the original
This is Khaisa Studio’s own bot, not the version above, and it won’t pass the job along: Review, approve, and chase subcontractor change orders with forms, DeepSeek, Gmail, and Google Sheets. - Vendor ActualsListed, routable
Check each supplier invoice against its purchase order and what the supplier has claimed to date, clear what matches for a person to approve, and hand the rest to a named owner.
- Woken by:
- bill.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- bill.checked, exception.raised
- Systems:
- Xero or MYOB (the ledger that issues the bill_id and holds the purchase orders), the record of work marked complete against each purchase order (the job system or schedule of rates), the document store where the invoice copies and written variation approvals live (Google Drive or SharePoint)
- Evidence:
- self-run, invoice-check 7 green, 1 with_us (2026-11-03)
Based on Invoice Coordinator by SpaceX. Rebuilt and maintained by AI Pathway.Show the original
This is SpaceX’s own bot, not the version above, and it won’t pass the job along: Invoice Coordinator. - Vendor PackListed, routable
Read each vendor's licence and insurance papers as they land, log the key fields and expiry dates, and hold anything unsure, missing or expired for a named person.
- Woken by:
- document.received (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- report.published, exception.raised
- Systems:
- the document store that issues the document_id (Google Drive or SharePoint), the vendor register that holds the graph and the pack queues, issuing the report_id and exception_id
- Evidence:
- self-run, rejected-pack 9 green, 1 with_us (2026-11-03)
Based on Monitor vendor compliance documents and expiries with Google Drive, OpenAI, Sheets, Gmail, and Slack by Javed Iqbal. Rebuilt and maintained by AI Pathway.Show the original
This is Javed Iqbal’s own bot, not the version above, and it won’t pass the job along: Monitor vendor compliance documents and expiries with Google Drive, OpenAI, Sheets, Gmail, and Slack. - Visit OfferListed, routable
Offer the customer real visit times off the licensed tech's calendar, book the one they pick as the job's single slot, and tell the customer and the tech once.
- Woken by:
- job.created (webhook), job.updated (webhook), schedule.tick (schedule), exception.closed (webhook)
- Hands on:
- job.updated, exception.raised
- Systems:
- the job system that issues the job_id and holds its schedule (ServiceM8, Simpro or Jobber), the tech licence register the business keeps
- Evidence:
- self-run, dispatch-board 8 green, 1 with_us (2026-11-03)
Based on Offer and confirm technician visit slots with Google Calendar, Gmail, Sheets, and Telegram by Dmytro. Rebuilt and maintained by AI Pathway.Show the original
This is Dmytro’s own bot, not the version above, and it won’t pass the job along: Offer and confirm technician visit slots with Google Calendar, Gmail, Sheets, and Telegram. - Visit RoundListed, routable
Each period, book the next visit on every maintenance contract with a licensed tech inside the customer's window, and hand lapsed contracts and visits no tech is free for to a named person.
- Woken by:
- schedule.tick (schedule), job.created (webhook), job.updated (webhook), exception.closed (webhook)
- Hands on:
- job.updated, exception.raised
- Systems:
- the job system that issues the job_id, raises each contract's next visit job and holds its schedule (ServiceM8, Simpro or Jobber), the tech licence register the business keeps
- Evidence:
- self-run, dispatch-board 8 green, 1 with_us (2026-11-04)
An original build by AI Pathway.
3. The team contract
Every listed bot keeps all six. The directory's gate refuses a bot that does not declare them, and the conformance run proves them.
- One id, carried. The id comes from the system of record (ServiceM8, Simpro, Xero, the property system) and is on every hop.
- Woken by a named event. A webhook, a schedule or a poll, using the mesh's event names. Nothing needs a live chat session.
- Read by id. After intake, a bot reads the upstream record by its id. Never by a customer name or a phone number.
- An open exception stops the chain. If an exception with a named owner is open on the record, the bot does nothing. When that person closes it, the chain picks up from the record.
- A write counts only with an id that reads back. Every handover names how its external id is read back. “Done!” in a chat is not a write.
- Durable state lives on the record. The job, quote or invoice, or a thin mirror of the Cash Seam fields. A bot's own memory holds preferences at most.
4. Working across runs and days
Each bot runs the same short loop every time it is woken, and keeps nothing between runs:
- Woken by a named event, with the id in hand. A scheduled bot lists records by status and takes each one's id.
- Reads the record by that id from the system of record.
- Stops if an exception is open on it.
- Does its one step.
- Writes to the system of record and reads the external id back. No id means it was not written: it raises an exception with a named owner and stops.
- Stamps the seam fields on the record and exits.
The next bot is woken by the system of record's own event, or by a Grok Bot routine seeing the new status. It can run an hour later, on another account, as a different bot. That works because what passes between them is the event, the id and the exception owner, not a conversation.
5. Who it is for
Business-to-business office work in five areas, and nothing outside them:
- Trades and building. Plumbers, electricians, HVAC, builders, any business that runs jobs out of ServiceM8, Simpro, Tradify, Fergus or similar.
- Fire and electrical compliance. Asset registers, service cycles, defect quotes, compliance packs.
- Accounting and bookkeeping. Practices and the businesses they keep books for: Xero, MYOB, receivables, payables, reporting.
- Property and real estate. Property management and sales agencies: arrears, compliance, vendor reporting, open homes.
- B2B office work. Back-office work any business-to-business firm shares: inbox, filing, follow-up, knowledge, exceptions. Consumer-facing bots do not qualify.
6. Adding a bot
- Find a public bot that does an office job, and the standard its job maps to.
- Rewrite it to that standard and run the checks:
npx @aipathway/conformance init <standard>, wire the bot to the ports, thennode run.mjs. On the cash path, run Cash Seam too. - Describe it in a
mesh.json: the events it is woken by and hands on, how each write reads back, who owns its exceptions, and the bot it is a port of. - Open a pull request adding it under
mesh/nodes/in the public repo, or use the submission form. The gate says what is missing in plain words.
Listings are marked self-run: the gate checks that the run is green, complete and under 90 days old, and a person reviews the rest. A bot whose run passes 90 days stays on this page as stale and drops out of routing until it is run again. Bots copied from a directory without being rewritten are never listed.
7. Credit, and taking a port down
Every port names the bot it came from, its author and its link, above the name of the person who ported it. Listing a port never transfers ownership of the original.
If you wrote a bot that someone has ported here, you can have the port taken down at any time without giving a reason, or keep it listed with your name taken off. Use the removal form or write to hello@aipathway.com.au. We act within two business days, and every port of your bot's link comes down with it.
8. For orchestrators and other bots
/mesh.json lists only the routable bots and the handovers between them: which bot hands which event, carrying which id, to which other bot. Route only to what is in it. Stale and removed bots are never in it.