Most automation tools are built for SaaS companies in San Francisco. n8n is the first workflow automation platform we found that handles the realities of Philippine business operations — intermittent connectivity, SMS-based communication, non-English data sources, and the GCash/Maya/bank transfer ecosystem that every PH business runs through. Here's what 60+ deployed systems across 8 ventures taught us.
By Diosh Lequiron, PhD, MBA, CSM — President & CEO, HavenWizards 88 Ventures OPC Last updated: May 9, 2026
Why Philippine Businesses Need Different Automation Tooling
Zapier and Make.com work well when your inputs are English-language SaaS tools with standardized APIs. Most Philippine businesses don't operate that way.
At Bayanihan Harvest, our agritech platform, farmer data comes in through a combination of form submissions, SMS messages (GlobeSMS gateway), WhatsApp Business API, and occasionally photos of handwritten records that need OCR before they can enter a database. A Zapier workflow handles the first type. It cannot handle the other three.
The second issue is cost. Zapier charges per task — every trigger, every action. At the automation density we run (60+ workflows firing across 8 ventures, some running every 15 minutes), Zapier would cost ₱150,000–₱200,000 per month. We run n8n self-hosted on a Digital Ocean droplet for ₱5,000–₱8,000 per month. Same workflows. One-fortieth the cost.
The third issue is control. When a workflow breaks in Zapier, you get a notification and a limited error log. In n8n, you get the full execution data — the exact payload that failed, the step that errored, and the ability to re-run just that execution with corrected data. For operations involving actual farmers and actual orders, this matters.
What n8n Is and How It Works
n8n is an open-source workflow automation platform. You build workflows visually — nodes connected by edges. Each node either triggers something (webhook, schedule, event) or does something (HTTP request, database query, email, transformation).
The key difference from Zapier: n8n is a full programming environment with a visual interface, not a visual interface that limits you to pre-built integrations. You can write JavaScript or Python directly inside a node. You can loop, branch, merge, and run sub-workflows. You can connect to anything with an API, even if n8n doesn't have a native integration, via the HTTP Request node.
Two deployment options:
- n8n Cloud — Hosted by n8n, subscription-based, no infrastructure management. Good for teams that want to start fast.
- Self-hosted — You run it on your own server. More control, lower cost at scale, requires basic DevOps knowledge.
We run self-hosted on a DigitalOcean droplet (4 GB RAM, 2 vCPU is enough for our current load). Setup took about 4 hours the first time, including SSL and Nginx configuration.
How We Use n8n Across Our Ventures
Bayanihan Harvest (Agritech)
Our most complex n8n deployment. Key workflows:
Farmer onboarding pipeline: A farmer submits data through a form → n8n receives the webhook → validates the data against our Supabase schema → if valid, creates the farmer record and sends a welcome SMS via Globe API → if invalid, logs the error and notifies our operations team via Slack. What would be manual data entry for a staff member is now fully automated.
Order routing: When a buyer places an order on the Bayanihan Harvest platform → n8n checks inventory against Supabase → assigns the order to available farmers based on crop type and location → sends assignment notifications via WhatsApp Business API → creates a delivery record → updates the dashboard in real time.
What failed first: We initially used a single monolithic workflow for the entire order process. When step 5 failed, the entire workflow failed and we couldn't resume. The fix: split into modular sub-workflows with explicit error handling and retry logic. This was a 2-week rebuild that we should have designed correctly from the start.
AHA eCommerce
Inventory sync: n8n polls our Shopify store every 30 minutes → compares inventory levels against our Supabase database → if a SKU goes below threshold, creates a reorder request and notifies our supplier via email → logs all sync events for audit.
Order fulfillment status: When an order ships from our warehouse → n8n receives the tracking update from the courier API → updates the Supabase order record → sends a status SMS to the customer via Semaphore → logs the event.
HW88 Education
Lead nurture automation: When someone downloads a free resource → n8n adds them to our Supabase leads table → triggers a multi-step email sequence via Resend (our transactional email provider) → after 7 days, if no conversion, moves them to a long-term nurture segment.
The n8n Features That Matter Most for Philippine Operations
HTTP Request node: Connects to any API. We use this for Globe SMS, GCash webhook processing, local payment gateways, and any tool that doesn't have a native n8n integration.
Error handling and retry logic: Every workflow has an "On Error" branch. Critical workflows retry 3 times with exponential backoff before alerting the operations team. Without this, 2 AM failures wake up people who don't need to be woken up.
Execution data persistence: n8n stores every workflow execution. When something breaks, we can see exactly what payload came in, which node failed, and why. This is the single feature that saves the most debugging time.
Webhook response modes: n8n can respond to webhooks immediately (before processing) or after processing. For payment webhooks that require a fast 200 response, this is critical — if processing takes 5 seconds and the payment gateway times out, you get duplicate webhook events.
Code nodes: When built-in transformations aren't enough, you write JavaScript or Python directly in the workflow. We use this for parsing Philippine address formats, computing peso values from dollar-denominated API responses, and cleaning SMS data before database insertion.
What n8n Does Not Do Well
It is not a database. n8n workflows should write to Supabase, Airtable, or another database — not try to store data inside workflows themselves.
Long-running processes need care. n8n is not designed for workflows that take 30+ minutes to execute. For video processing or large data imports, use a queue system and trigger n8n when the job is complete rather than running it inside n8n.
The visual interface slows down at scale. Workflows with 50+ nodes become difficult to navigate visually. We break large workflows into named sub-workflows and call them from a parent workflow. This is a discipline issue, not a platform limitation.
Team collaboration is limited on self-hosted. n8n Cloud has better team features. On self-hosted, you need to manage access carefully. We use separate instances per venture team to prevent one team's changes from breaking another team's workflows.
Frequently Asked Questions
Do I need a developer to use n8n? For simple workflows (webhook → database → email), no. For complex multi-branch workflows with code nodes and API integrations, yes. Our operations staff build simple workflows independently; our developers build the complex ones. The split is roughly 60/40.
How is n8n different from Zapier? Zapier is optimized for non-technical users connecting popular SaaS tools. n8n is optimized for technical operators who need control, custom code, and high-volume execution at lower cost. Both have their place — Zapier for simple, n8n for anything complex.
What does n8n cost? n8n Cloud starts at around $24/month (as of May 2026). Self-hosted is free for the software — you pay only for server infrastructure. A DigitalOcean droplet sufficient for most small-to-medium deployments runs ₱2,800–₱5,600/month.
Can n8n connect to GCash or Maya? Not natively. Both GCash and Maya expose webhooks and APIs for business accounts. Use the HTTP Request node in n8n to connect. You'll need a business GCash/Maya merchant account for API access.
What do I automate first? Start with the task your team does most frequently that follows a predictable pattern. For most Philippine businesses, this is: customer inquiry → response → follow-up. Map that flow exactly, then build it in n8n.
Getting Started Checklist
- Identify 3 repetitive workflows your team runs manually every day
- Choose deployment: n8n Cloud (faster start) or self-hosted (lower cost at scale)
- Sign up at n8n.io or spin up a DigitalOcean droplet with n8n Docker image
- Build workflow #1 with a webhook trigger and one action (database insert or email send)
- Add error handling: "On Error" branch that sends a Slack notification
- Test with real data, not sample data — behavior is different
- Add logging: every workflow should write an execution record to your database
- Run for 2 weeks, measure time saved vs. time spent maintaining
- Expand to workflow #2 only after #1 is stable