Intelligent Automation in Kenya
I build workflow automations that remove manual steps from a business — WhatsApp order flows, M-Pesa payment confirmation, rent and booking reminders, and back-office sync — mostly on n8n, Make and direct API integrations.
Automation work starts with a specific complaint, not a platform. Someone is confirming M-Pesa payments by hand at 11pm. Enquiries sit unanswered for four hours because nobody is at a desk. Numbers get copied out of WhatsApp into a spreadsheet, and occasionally copied wrong.
Each of those is one workflow, not a transformation project. I map the step, build the system that removes it, and instrument it so you can see whether it actually worked. A WhatsApp flow that confirms an order, triggers the STK push, and writes the record typically costs less than one month of doing the same work by hand.
The integrations I reach for most are the ones East African businesses actually run on: the M-Pesa Daraja API for payments and callbacks, the WhatsApp Business API for the channel customers already use, and n8n for the orchestration — self-hostable, so the workflows stay yours.
Where a system is doing real volume, it gets tested like software. The WhatsApp sales agent in the case studies carries 176 automated assertions across five test suites, and was refactored from 11 workflows and 172 nodes down to 6.
What this fixes
- Repetitive tasks
- Human error
- Time-consuming workflows
Work that proves it
- WhatsApp AI Sales Agent with M-Pesa CheckoutAn AI sales agent that runs entirely inside WhatsApp — search a real catalogue, get a grounded recommendation, and pay by M-Pesa — with the owner SMS’d the moment a sale lands.
- WhatsApp Bundle Sale AutomationA WhatsApp bot that sells data bundles and confirms M-Pesa payment end to end.
- Order-to-Dispatch Bot for Boutiques & ShopsA WhatsApp bot that takes the order, takes the money, updates stock and calls the rider.
Tools and platforms
- n8n
- Make
- Zapier
- Webhooks
- M-Pesa API
- WhatsApp API
- Meta API
- Google Workspace
- Airtable
- Supabase
n8n
Make
Zapier
Webhooks
M-Pesa API
WhatsApp API
Meta API
Google Workspace
Airtable
SupabaseCommon questions
- Can you integrate M-Pesa with WhatsApp?
- Yes — that is one of the most common systems I build. A customer places an order in WhatsApp, the workflow triggers an M-Pesa STK push, listens for the Daraja callback, confirms the payment back in the chat, and writes the record to wherever you keep them. No one confirms anything by hand.
- Do you use n8n, Make or Zapier?
- All three, chosen per job. n8n is the default for anything with real logic or volume because it can be self-hosted, has no per-task pricing, and the workflows remain your property. Make suits visual, mid-complexity flows. Zapier is worth it when a client already lives in it and the job is simple.
- How long does an automation take to build?
- A single well-defined workflow — one trigger, one outcome — is usually days rather than weeks. Multi-step systems with payments, approvals and reporting take longer. The scoping conversation gives you a fixed figure in writing before anything is built.
- What happens if the automation breaks?
- Systems are built with error branches and failure notifications rather than silent failure, so you find out from the system instead of from a customer. Where the work is ongoing, monitoring and maintenance are part of the arrangement.