Expertise / 01
AI Automation
I map a process end to end, decide which steps a system should own and which stay with a person, and build the rest in n8n — with error handling, idempotency and a refusal path in place from the first node.
14 systems, 7 delivered, 7 built
01 — Tools and stack
What this work is built on. Every tool below is part of at least one of the systems further down this page. HoverTap a card to see what it is used for.
n8n
Workflow engine
Sub-workflows, Code nodes, error workflows, webhooks and schedules, self-hosted or cloud. Every system on this page runs on it.
JavaScript
Workflow engine
Code nodes, for the parsing, validation and scoring that the built-in nodes cannot express.
Google Sheets
State and records
The state store when the client has to be able to read it: each record carries its own stage, sequence position and timing.
PostgreSQL
State and records
Where a sheet stops: the single SQL condition that decides which follow-up is due, and the search an assistant answers from.
Google Drive
State and records
Documents filed to the right folder, and watched so that only what has changed is read again.
Gmail
Messages and alerts
Threaded sends and reply detection, so a sequence stops by itself the moment someone answers.
Slack
Messages and alerts
Approvals as signed, one-time callbacks, and an alert when spend or call volume looks wrong.
Telegram
Messages and alerts
Escalations to a person, with the order’s context already attached.
Twilio
Messages and alerts
SMS sent only with consent, and a booking link by text inside a minute of a missed call.
OpenAI
Models in the workflow
Classification and extraction into locked schemas, so that no branch depends on parsing free text.
Google Gemini
Models in the workflow
Replies drafted from data the CRM has confirmed, while the gates around the model decide what happens.
Apify
Lead sourcing and browser automation
Discovery runs that are polled until they finish. A failed or partial scrape never reaches the CRM.
Skyvern
Lead sourcing and browser automation
A browser agent for the one step a vendor leaves without an API.
Also offered
- Make
- Zapier
- Microsoft Power Automate
- Pipedream
- IFTTT
- Pabbly Connect
- Node-RED
- Activepieces
- Apache Airflow
- Workato
What each of these covers is on the Integrations page.
02 — Delivered
Lead-to-Cash CRM for Three Contractors
Eight lead sources call one hub, the only workflow allowed to write a lead. The stage is stamped before any follow-up fires, so nothing runs twice.
AI Voice Agent System for a Training Academy
The orchestration around the voice agents: details sent while the caller is still on the phone, and every outcome written back to the CRM with no human transcription.
Shopify Support Inbox, Handled End to End
One Gmail trigger reads every support email. Five intents are resolved end to end against the real order, and anything else is escalated rather than guessed.
Google Local Services Ads Lead Responder
New leads are polled every 15 minutes and live conversations every 5, and each lead’s last-answered message is tracked, so nothing is answered twice.
Construction Lead Generation & Email Outreach
Discovery on Google Maps, a CRM in which each record carries its own schedule, and a four-step sequence, capped per run, that stops the moment someone replies.
Labor Law Firm Outreach & Follow-Up
One four-hour cycle checks for replies and then sends what is due, so there is no window in which someone answers and is chased anyway.
LinkedIn Lead Generation Pipeline
Keywords rotate so that every run covers new ground. A failed scrape takes its own path, and every profile is checked against the CRM before a row is written.
03 — Built, not yet deployed
The workflow JSON is in the repository and imports into n8n; the node counts are taken from it. None of these has yet run against live accounts.
AI Front Desk — Missed Calls, After Hours and Booking
The workflows around a voice agent: overflow routing, the tools it has to call, booking, missed-call recovery and the write-back to the CRM.
Invoice & Document Intake into Your Accounting System
From a mailbox to Xero: each invoice classified, extracted, arithmetic-checked, matched to a purchase order and checked for a duplicate immediately before it is posted.
Company Knowledge Assistant That Cites Its Sources
Ingestion that re-indexes only what has changed, every six hours, and a weekly digest of the questions it could not answer.
Client Onboarding — Signature to Kickoff without Chasing
Contract, signature, payment and provisioning, each done exactly once: Stripe’s event ID is recorded before anything is created.
The Weekly Number, Assembled and Sent
Five sources pulled separately, so one outage cannot block the rest, then upserted into one row a week in a sheet the client owns.
Content Repurposing Line with a Human Approval Gate
One recording becomes drafts for each platform, and the graph has exactly one path to publishing: through a person’s approval.
CRM Rebuild & Migration, with the Automations on Top
A migration that defaults to a dry run and reserves a rollback row before each record is created, then routing and follow-up rebuilt on the new model.
04 — Book a call
Have a process that still runs by hand?
Book a call and walk me through it. I will tell you which steps a system should own, and which should stay with a person.