WHAT IT DOES

Automations move data from A to B (and sometimes C) without you lifting a finger. In n8n, you build workflows from small blocks called nodes. With just ~17 nodes you can cover ~80% of real-world use cases: start a flow (trigger), store/retrieve data (storage), reshape it (data processing), branch it (logic), combine it (merge), call other apps (HTTP/Webhooks), and add intelligence (AI steps & AI agents). MOBLE connects these workflows to your website, Chatbots, Voicebots, CRM (Sales Lead Desk), Support Ticket Desk, Project Task Desk, and SPIBoard.

THE 10 CORE NODES YOU NEED TO KNOW

These ten nodes form the backbone of nearly every automation. Master these and you’ll handle 80% of all use cases you’ll build within MOBLE and n8n.

1. Manual Trigger — Start workflows manually for testing or ad-hoc runs.
2. Schedule Trigger — Automate actions at set times or intervals (daily, weekly, or via cron).
3. Webhook Trigger — Receive data from a form, chatbot, or third-party app in real time.
4. If — Create simple yes/no logic to route data based on conditions.
5. Switch — Create multi-branch logic to route different data types down different paths.
6. Merge — Combine data streams or bring multiple branches back into one flow.
7. Split In Batches (Split Out) — Break down lists (arrays) into individual items for processing.
8. Google Sheets — Store or retrieve data using simple rows and columns.
9. HTTP Request — Send data to, or pull data from, any API endpoint.
10. AI Node — Generate or transform text, summaries, or structured data using OpenAI.

7 ADVANCED NODES FOR EXPERTS

Once you’ve built a few workflows, these seven unlock more powerful, enterprise-grade automations.

11. Respond to Webhook — Send a confirmation or response back to the originating system.
12. n8n Data Tables — Use native storage for internal databases and quick lookups.
13. Code Node — Write custom JavaScript for advanced data manipulation.
14. Aggregate — Combine multiple data items into a single record or array.
15. AI Agent — Create a context-aware assistant that can “think,” remember, and act across tools.
16. AI Agent Tools — Extend an AI Agent’s capabilities (e.g., Gmail, Notion, Airtable integration).
17. Webhook (Respond & Test Pair) — For advanced two-way communication between apps and servers.

HOW TO REMEMBER THEM

You can think of these 17 nodes as three layers:

• Start: Triggers (Manual, Schedule, Webhook)
• Decide: Logic (If, Switch) + Process (Split, Merge, Aggregate)
• Act: Data (Sheets, Tables) + Connect (HTTP, Webhooks) + Intelligence (AI Node, AI Agent)

KEY CONCEPTS & NODES (BEGINNER-FRIENDLY)

1) Triggers — how a workflow starts

• Manual Trigger: Run a flow on demand. Perfect for testing while you build.
• Schedule Trigger: Run on a timetable (every X minutes/hours/days) or via cron (e.g., “2:00 pm every Tuesday”). Example: generate & post content daily at 00:00.
• App/Event Triggers (e.g., Typeform): Start when something happens in another app (a form is submitted, a payment succeeds, etc.). Under the hood, these use webhooks.

2) Storage Solutions — where your data lives

• Google Sheets / Airtable / Notion: Append a row like Name, Email, Phone, Location. (Tip: avoid leading “+” or “=” in Sheets—they’re formulas.)
• n8n Data Tables: Lightweight built-in database. Same idea as Sheets, but native to n8n and fast for internal lookups.
• MOBLE: Use storage to log to SPIBoard and your CRM/Tickets/Tasks, then sync outward to Sheets or your warehouse.

3) Universal Data Processing — reshape data to fit the next step

• Split Out: You have a list (an “array”) of people; split into individual items to handle one person per pass (great before writing rows to a table).
• Aggregate: The reverse—combine many items back into one bundle before sending onward.

4) Logic — route based on rules

• If: Two paths only—true or false. Example: “If Name contains ‘Sarah’, go left; otherwise go right.”
• Switch: Many named paths. Example: route emails into buckets (FAQ, Promo, Sales, Other) from a single decision point.

5) Merge — bring branches back together

• Combine: Take results from multiple branches (e.g., LinkedIn post, Facebook post, Tweet, Article) and output them together for one “write to Google Sheet” step.
• Append: Output each incoming item separately (useful in some fan-in patterns).

6) Code — when you need one block to do the work of many

• Code Node: Optional but powerful. Transform complex data in one place instead of chaining many processors. Most beginners won’t need it often—but it’s there when things get fancy.

7) Connectivity & APIs — talk to any app

• HTTP Request: The “Swiss Army Knife.” If n8n doesn’t have a native node, call any API using its docs (GET/POST, headers, auth, body, etc.). Example: fetch weather, send SMS, create invoices.
• Webhook (Incoming): Get data the moment something happens (e.g., a form is submitted). You’ll see a Test URL (for development) and a Production URL (once active).
• Respond to Webhook: Send a message back (e.g., “Workflow complete”)—handy when the source app expects confirmation.

8) AI Integration — add intelligence

• AI Node: A single, linear AI action. Provide prompts (System/User/Assistant) and get structured or written output (e.g., “Draft a LinkedIn post about X”).
• AI Agent: Conversational + tool-using. The agent “remembers” context and can use connected tools (Gmail, Airtable, Notion, etc.) to take actions from one input stream—like a real assistant.

HOW TO USE (YOUR FIRST MOBLE + n8n WORKFLOW)

Goal: Capture a website enquiry, score it, store it, and notify your team—automatically.

1) with a Trigger

Choose Webhook (recommended) or a native form trigger (e.g., Typeform). In MOBLE, your Chatbot/Form can post to the workflow URL when a visitor submits.

2) Validate & Reshape

If the submission arrives as a list (multiple items), use Split Out. Clean up fields (e.g., trim spaces, normalise casing). Use If/Switch to branch on things like intent, budget, or urgency.

3) Store the Data

Append to n8n Data Tables or Google Sheets. In MOBLE, also log to the Sales Lead Desk (or Support/Project) and display in SPIBoard for Status–Priority–Importance scoring.

4) Add Intelligence

Use an AI Node to summarise the enquiry and propose a next action (e.g., “Is this a quote request or general question?”). Optionally, let an AI Agent draft the human follow-up and file it in your CRM.

5) Notify & Close the Loop

Merge any branches (content + classification + storage) and then: send email/slack, update your CRM record, respond to the webhook with “received,” or return a personalised confirmation to the user.

EXAMPLE SETUP

Use Case: “Daily Content + Central Log”

• Schedule Trigger: Run every day at 00:00.
• AI Node: Generate LinkedIn, Facebook, and X copy from a single brief.
• Merge: Combine all three posts, plus a long-form article, into one payload.
• Storage: Append a single row to Google Sheets with four columns (or push to n8n Data Tables).
• Optional: Use an HTTP Request to auto-schedule posts via your social tool, then log completion back to SPIBoard.

BEST PRACTICES

1) Build with Test Data First

• Use Manual Trigger and Webhook (Test URL) while iterating. Confirm fields before touching live systems.

2) Keep Nodes Small & Readable

• Prefer simple nodes over giant code blocks. Use the Code node sparingly for complex transforms.

3) Shape Data Early

• Split lists before storage; validate emails/phones; normalise keys; name fields consistently (e.g., firstName, company).

4) Route with Intent

• Use If/Switch to send Sales to the Lead Desk, Support to the Ticket Desk, Projects to the Task Desk, all visible in SPIBoard.

5) Centralise Before You Broadcast

• Merge content from branches and write once to your sheet/table—then fan out emails, posts, or updates.

6) Respect API Docs

• When in doubt, the HTTP Request node + the app’s API docs can reach anything. Secure keys, set headers, and test responses.

7) Close the Loop

• If a source expects acknowledgment, use Respond to Webhook with a clear success message or error details.

WHERE THIS FITS IN MOBLE

• Website & Chatbots: Replace old forms with AI Chatbots; send submissions to n8n via Webhook.
• SPIBoard: Every enquiry/lead/ticket/task gets a Status–Priority–Importance score for clean handover.
• Desks: Route automatically—Sales Lead Desk, Support Ticket Desk, Project Task Desk—then notify humans.
• Automation: Use Make/HTTP nodes to integrate anything else; keep Sheets/Data Tables for quick auditing.

NEXT STEP

Now that you understand the building blocks, you’re ready for a guided “Hello World” workflow: form → webhook → split → if/switch → store → notify → SPIBoard. When you’re comfortable, add an AI Node to summarise enquiries—and graduate to an AI Agent for multi-step, tool-using tasks.