n8n, APIs, and the technical tier

The wall between $900 and $2,000 a month

Here is the ceiling, stated plainly by the market: the automation VA who stays inside GoHighLevel and Zapier's comfort zone plateaus around the $900/mo generalist band (~₱52k). The one who learns n8n, APIs, webhooks, and JSON is the $2,000+/mo specialist (~₱116k+) that 785 open n8n listings on Upwork can't fill. Same job title. The difference is whether "there's no integration for that" stops you.

What n8n is and why it matters

n8n is an open-source automation platform you can self-host — meaning it runs on a cheap server the client controls, with no per-task fees and no data leaving their infrastructure. Builds are graphs of nodes (like Make's modules) with two upgrades that matter: an HTTP Request node that can talk to any API on the internet, and native AI agent nodes that let a model call tools and make multi-step decisions inside the flow.

That's why complex, AI-heavy client work concentrates in n8n: high-volume flows that would rack up Zapier task fees, logic too branchy for a linear Zap, and agent builds where the model reads an email, checks a calendar, and books a slot. When a client says "we tried Zapier and hit a wall" — that's an n8n engagement, and it prices accordingly.

JSON without fear

JSON is just structured text — labels and values in curly braces. Every API you'll ever touch speaks it, and you already read it in lesson 4's prompt output. Here's a webhook payload from a form:

{"lead": {"name": "Jennifer Cruz", "budget": 2500, "tags": ["facebook", "hot"]}}

Reading it is a path game: lead.name is "Jennifer Cruz", lead.budget is 2500, lead.tags[0] is "facebook" — square brackets mean a list, and counting starts at zero. That's genuinely 90% of the JSON skill an automation VA uses: follow the dots, grab the value, map it into the next node. You don't write JSON from scratch; the tools do. You read it and point at the right field.

APIs: the four things that actually matter

An API is an app's back door for other software. Every request you'll ever send has four parts: the endpoint (the URL, like api.stripe.com/v1/customers), the method (GET reads data, POST creates it), the auth (usually a header like Authorization: Bearer sk_live_... — an API key is a password, treat it like one), and sometimes a body (the JSON you're sending). The response comes back as JSON plus a status code:

Reading API docs like a professional

API documentation intimidates people because they read it like a novel. Seniors read it like a menu:

Webhooks, inbound

In lesson 3 you consumed webhooks; in n8n you create them. Add a Webhook node and n8n mints a unique URL. Paste that URL into any app that can "send a webhook on event" — Stripe on payment, Calendly on booking, Typeform on submit — and your flow now triggers instantly from an app no connector library even lists. Classic client build: Stripe fires checkout.session.completed → your webhook catches the JSON → extract customer email and amount → create the client record, send the onboarding email, post to Slack. That flow, sold as "your customers get onboarded in 10 seconds, 24/7," is a real deliverable Filipino specialists are charging real money for.

Do this now

Twenty minutes, no code written. Pick one public API — OpenWeather, Stripe, or HubSpot — and open its documentation. In a doc titled API Recon — [API name], answer four questions: (1) How does it authenticate, and what's the exact header format? (2) What's the full URL of one useful endpoint, and is it GET or POST? (3) Paste one example request from the docs. (4) From the example response, which JSON path would you map into a CRM — written in dot notation, like data.customer.email?

If you finish early: sign up at n8n.cloud's free tier, drop a Webhook node on the canvas, and hit its test URL from your browser. Watching your own ping arrive as JSON is the moment APIs stop being scary.