Kevin

n8n Workflow Automation Specialist

Freelancer.com • ZZP

Jan 2023 - Present • 3 yrs 6 mos

As a self-employed automation specialist, I design and build n8n workflows for small businesses and agencies looking to cut out repetitive manual work. My process always starts with understanding the client's actual day-to-day process, not just the tools they name, since the most valuable automation is often one step upstream of what a client originally asks for. I've built lead-capture pipelines connecting web forms directly to CRMs with instant Slack alerts, e-commerce order and inventory sync workflows across multiple sales channels, and AI-assisted document processing using OpenAI and Claude models for summarizing and classifying incoming requests. I put real effort into error handling on every build — retry logic on API calls, fallback paths for missing data, and alerts routed to a human whenever the workflow hits something it can't confidently resolve — because an automation that fails silently is often worse than the manual process it replaced. I also handle a steady stream of Zapier-to-n8n migrations for clients wanting to reduce recurring software costs while gaining more flexibility in their automation logic. Every project ships with documentation written in plain language plus a short walkthrough, so clients aren't left dependent on me for basic edits. I offer self-hosted n8n deployment for clients who want full control over where their data lives.

AI Workflow Developer

Property Options & Developments • Freelance

Aug 2023 - Jan 2024 • 5 mos

Engaged by a property management company to automate tenant maintenance request handling, which had previously funneled through a shared inbox that one coordinator manually triaged and forwarded to the right vendor each day, a process prone to delay when that coordinator was out. I built an n8n workflow that captures maintenance requests submitted through a form, uses an AI model to classify urgency and category, automatically routes standard requests to the correct pre-assigned vendor with request details attached, and flags anything ambiguous or marked urgent for the coordinator's direct attention rather than routing it automatically. Tenants receive an automatic acknowledgment with an estimated response window immediately on submission, which noticeably reduced follow-up calls asking whether a request had been received at all. I integrated the workflow with the company's property management software so every request and its resolution status stayed logged against the correct unit, giving management visibility into recurring maintenance issues at specific properties over time. I also built a monthly summary report of request volume, average resolution time, and vendor performance, automatically compiled and emailed to the operations director, replacing a manual spreadsheet compilation that had taken hours each month. The coordinator reported the automation cut her daily triage time by more than half.

Automation Consultant

Fitness First UK • Freelance

Feb 2023 - Jun 2023 • 4 mos

Hired by a growing fitness studio chain operating three locations to automate class booking notifications and membership renewal reminders that had previously been handled manually by front-desk staff at each location, inconsistently and often too late to actually prevent a lapsed membership. I built an n8n workflow tied into their booking platform that automatically sends class reminders and waitlist notifications, and a separate renewal pipeline that detects upcoming membership expirations and triggers a reminder sequence timed well before the renewal date rather than after it had already lapsed. Failed payment attempts were flagged to the studio manager for a personal follow-up call rather than an automated dunning email, since the chain wanted renewal conversations with long-standing members handled by a person, not a bot. I also built a simple win-back sequence for members who hadn't booked a class in several weeks, which recovered a handful of memberships that would otherwise have quietly ended. Because the chain operated across three locations with slightly different schedules and staff, I built the workflow with location-specific branching so one system served all three without needing three separate builds. Documentation was kept deliberately simple given the studio's non-technical staff, including a short recorded walkthrough anyone at the front desk could reference.