Workflow Automation
Workflow automation built around the tools you already run on
Automating one trigger is easy. The actual work is making a workflow hold up once it has to move real data between several tools without dropping a handoff, silently failing, or breaking the moment a field changes upstream.
Is this the right fit?
This is the general entry point if you know something needs to be automated but aren't sure which platform fits — I'll recommend n8n, Make or Zapier based on your team's technical comfort, budget and how complex the logic actually is, rather than defaulting to whichever tool I'd rather use. See the dedicated n8n and Make pages if you already know which platform you're on.
Problems this solves
- Manual, repetitive steps between tools eat hours every week
- Handoffs between people or systems get dropped or delayed
- Existing automations break silently, or can't express the conditional logic a process actually needs
- Nobody on the team can tell why a workflow failed last week, because nothing was logged
What I build
- A new form submission automatically creates records, notifies the right person and updates a tracker
- A set of n8n and Make workflows connecting seven core tools for a business, running since 2023
- Scheduled workflows that keep data synchronized across tools without manual exports
- Conditional routing and data transformation so each destination tool gets information in the format it expects
Tools
Real proof, not a promise
Habfract Ltd.: Business Operations Automation
An ongoing set of automated workflows connecting the business's core tools end to end.
Read the case studyLead workflow automationLead Generation Web Scraping System
A Python and n8n system that scrapes and structures lead data automatically.
Read the case studyHow this works
Every engagement starts with how the process actually runs today, then moves through design, build, and testing against real data before handover. See the full five step process for the details.
Further reading
Frequently asked
How do you decide between n8n, Make and Zapier?
By the logic and who maintains it afterward. n8n suits complex branching logic and teams comfortable with a more technical, self-hostable tool. Make suits fast-moving visual builds most teams can read at a glance. Zapier suits simple, high-reliability single-purpose zaps. Habfract, for example, runs all three where each genuinely fit best rather than forcing one tool to do everything.
What happens when a workflow fails?
It shouldn't fail silently. Every workflow I build logs failures and triggers a notification instead of quietly dropping the run, which is the difference between catching a problem in minutes and finding out a week later that records stopped syncing.
Can you take over an automation someone else built?
Yes — a real example is a n8n workflow bug resolution project where the existing Notion integration was breaking; I diagnosed and fixed it without a rebuild. Handoff and documentation are part of every engagement so you're not dependent on me for routine changes.
Have a process like this to automate?
Tell me what's slow or manual right now. I'll tell you what it takes to fix it.