WHAT IT DOES

n8n lets you automate work across MOBLE and your app stack. A workflow starts with a Trigger (e.g., a form submission or a webhook from a MOBLE Chatbot) and then runs one or more Actions (e.g., route with logic, call an API, store to a sheet, notify Slack). Each node receives an array of items, processes each item, and outputs an array to the next node—this “items in, items out” contract is the core mental model.

THE MINI WORKFLOW WE’LL BUILD

• Trigger: n8n Form (or your MOBLE Chatbot → Webhook into n8n).
• Logic: “Is the preferred install date within 7 days?”
• Action (true path): Send a Slack message.
• Action (false path): Placeholder (No Operation) you can replace later.

STEP 1 — CREATE A NEW WORKFLOW & ADD A TRIGGER

Option A: n8n Form Trigger (great for learning/testing)

1. In n8n, click New workflow to open the canvas.
2. Click + → search “Form Trigger” → add it. You’ll see a ⚡ icon on trigger nodes.
3. Fill the required Parameters:
   • Title: Request an Installation
   • Description: Fill out this form to request an installation. We’ll contact you via email.
   • Form Elements:
     • Email (type: Email, Required)
     • Preferred install date (type: Date, Required)
4. Click Execute node to open the test form, submit a sample.

Option B: MOBLE Chatbot → n8n Webhook (for production)

1. In n8n, add a Webhook node (Method: POST, Path: /moble/chatbot/enquiry).
2. Copy the Production URL from the node.
3. In MOBLE: AGENTS → EDIT → Integrations → paste into n8n: Webhook URL, then Save.

Tip: Use the Form Trigger while you learn. Switch to the Webhook when you plug in your MOBLE Chatbot or web forms.

STEP 2 — UNDERSTAND “ITEMS” & PIN YOUR TEST DATA

• Every node outputs an array of items. Your test form created one item, so the output array length is 1.
• Nodes run their operation once per incoming item—you rarely need a separate “loop” node.
• Pin Data: On the trigger node, click Pin data. Now test runs reuse the pinned payload (no need to re-fill forms). Pin is ignored in production.

STEP 3 — ADD CONDITIONAL LOGIC (7-DAY CHECK)

1. Click + after the trigger → add an If node.
2. Set one condition:
   • Value 1: click the field → switch to Expression → drag in the date from your trigger (or use {{ $json["preferredInstallDate"] }}).
   • Operation: is before or equal to
   • Value 2 (Expression): {{ $now.plus(7, 'days').toDateTime() }}
3. Rename the If node to “Is within 7 days?” (question phrasing makes true/false branches obvious).
4. (Optional) On the false branch, add a No Operation node and rename to “Queue / schedule later”.

STEP 4 — SEND A SLACK MESSAGE (TRUE BRANCH)

1. From the If node’s true output, click + → add Slack → choose Send a message.
2. Create/select your Slack credential (OAuth is easiest on n8n Cloud).
3. Channel: choose your team channel (e.g., #sales).
4. Message Text (Expression). Example:

   New install request within 7 days Contact:  Preferred date:  

5. Click Execute node to test (you should see a green check in n8n and a message in Slack).

STEP 5 — SAVE, ACTIVATE & VIEW EXECUTIONS

• Click Save, then Activate the workflow.
• Form Trigger: use the Production URL (shown in the node) to open the live form and submit.
• Webhook Trigger (from MOBLE): submit your MOBLE Chatbot/form; n8n will receive the POST instantly.
• Open the Executions tab to inspect production runs (no beaker icon). You can “Copy to editor & pin” a production payload to keep building.

MAPPING & TRANSFORMING DATA (THE BASICS)

• Drag & drop fields from earlier nodes into later nodes (or write expressions).
• Common expressions:
  • Field reference: {{ $json["email"] }}
  • Now + 7 days: {{ $now.plus(7, 'days').toDateTime() }}
  • Combine static + dynamic: {{ "Lead: " + $json.fullName }}
• Views: Switch output view between JSON, Table, and Schema to understand structure.

WHERE THIS FITS IN MOBLE

• AGENTS → EDIT → Integrations: paste your n8n Webhook into n8n: Webhook URL (or the general Webhook URL). MOBLE Chatbots/Forms will POST submissions to n8n.
• Knowledge Feeds (GET): use n8n HTTP Request to read your MOBLE JSON endpoints (FAQ, PAGE, FILE, BLOG, VOICE, PRODUCT) with Authorization: Bearer ak_… header.
• SPIBoard + Desks: after routing (If/Switch), write the record to your CRM/Tickets/Tasks and surface it in SPIBoard with Status–Priority–Importance for clean human handover.

BEST PRACTICES

• Pin data during build; unpin or use live payloads when ready.
• Name nodes clearly (e.g., “Is within 7 days?”). Future you will thank you.
• Validate inputs (email required, date present) before downstream actions.
• Secure keys in n8n credentials (never hard-code ak_… keys).
• Idempotency: avoid duplicates (e.g., check if lead exists via email before creating).

NEXT STEPS

• Swap the Form Trigger for your MOBLE Chatbot Webhook and go live.
• Add an AI Node to summarise enquiries and propose next actions.
• Append records to n8n Data Tables or Google Sheets for audit and analytics.
• Extend the true/false branches (e.g., book a calendar, create a CRM deal, open a Support Ticket).

TL;DR

• Triggers start workflows; actions do the work. Every node in n8n passes an array of items to the next node.
• Build a simple conditional route (7-day date check), then notify Slack for urgent cases.
• Connect MOBLE by pasting your n8n Webhook URL in AGENTS → EDIT → Integrations; use MOBLE API/JSON feeds with HTTP Request.

::contentReference[oaicite:0]{index=0}