Agentic AI in Business · Workshop II

A page of your own, with n8n and Claude Code behind it

Morning 2 of 3 · first we talk, then you build your page, then a look at this afternoon

Frank Huettner · 16 November 2026

Today: first we talk, then you build

1–3Laptops closed
  • System architecture
  • Setting up Claude Code
  • Product architecture
4Your taskslaptops open, with the workbook: a page that asks your mailbox, a better search flow, your team's rulesYour own page asks your mailbox
5This afternoonthe voluntary tutorialn8n automation in your team's project

While we talk, nothing to type: the workbook has every step.

Today we build this: a web page to ask your mailbox

localhost:8080/ask.html Ask your mailbox Who arranges tours of the trading floor? Ask question answer n8nruns the steps Langflowthinks PostgreSQLholds your mails Gmailtest account copy

Your laptop: Windows, Ubuntu inside, kingo-pod in it

WindowsUbuntu, a Linux inside Windows (WSL)kingo-pod· a folder

kingo-pod: a folder of scripts and settings

WindowsUbuntu, a Linux inside Windows (WSL)kingo-pod· a folderkingothe scriptcompose.ymlthe servicesbackups/flows/copies of your flowsshared/Langflow sees itclaude/Claude Code's folder

./kingo up: Podman starts one container per service

WindowsUbuntu, a Linux inside Windows (WSL)kingo-pod· a folderkingothe scriptcompose.ymlthe servicesbackups/flows/copies of your flowsshared/Langflow sees itclaude/Claude Code's folderPodman · one container per servicePostgreSQLlocalhost:5432CloudBeaverlocalhost:8978Langflowlocalhost:7860n8nlocalhost:5678up

The containers talk by name; you reach them at localhost

WindowsUbuntu, a Linux inside Windows (WSL)kingo-pod· a folderkingothe scriptcompose.ymlthe servicesbackups/flows/copies of your flowsshared/Langflow sees itclaude/Claude Code's folderPodman · one container per servicePostgreSQLlocalhost:5432CloudBeaverlocalhost:8978Langflowlocalhost:7860n8nlocalhost:5678uptheir own networkn8n calls http://langflow:7860Browserin Windowslocalhost:5678

Your flows live in PostgreSQL, with copies on disk

WindowsUbuntu, a Linux inside Windows (WSL)kingo-pod· a folderkingothe scriptcompose.ymlthe servicesbackups/flows/copies of your flowsshared/Langflow sees itclaude/Claude Code's folderPodman · one container per servicePostgreSQLflows, workflows, mailslocalhost:5432CloudBeaverlocalhost:8978Langflowlocalhost:7860n8nlocalhost:5678uptheir own networkn8n calls http://langflow:7860Browserin Windowslocalhost:5678

shared/: a folder that you and Langflow both see

WindowsUbuntu, a Linux inside Windows (WSL)kingo-pod· a folderkingothe scriptcompose.ymlthe servicesbackups/flows/copies of your flowsshared/Langflow sees itclaude/Claude Code's folderPodman · one container per servicePostgreSQLflows, workflows, mailslocalhost:5432CloudBeaverlocalhost:8978Langflowlocalhost:7860n8nlocalhost:5678uptheir own networkn8n calls http://langflow:7860Browserin Windowslocalhost:5678

nono: Claude Code reaches your tools, not your laptop

WindowsUbuntu, a Linux inside Windows (WSL)kingo-pod· a folderkingothe scriptcompose.ymlthe servicesbackups/flows/copies of your flowsshared/Langflow sees itclaude/Claude Code's folderPodman · one container per servicePostgreSQLflows, workflows, mailslocalhost:5432CloudBeaverlocalhost:8978Langflowlocalhost:7860n8nlocalhost:5678uptheir own networkn8n calls http://langflow:7860Browserin Windowslocalhost:5678nono, the sandboxClaude Codewrites only in claude/OpenRouterthe models, on the internetoutside your laptop

Tell Claude Code your team's rules: one file, read at every start

Why: every teammate's Claude Code builds the same way, and nobody has to say it again in every session.

you senda requestwith the six principles, from the workbook
asks you, one principle at a timeClaude Codewrites your team's rules
you check themclaude/AGENTS.mdread at every start

Your names

for workflows, nodes, tables

Example: Blue - Intake by Mail

Your contracts

what goes in, what comes out

Example: Triage returns action

Where a person decides

which step waits for an OK

Example: a draft waits for your OK

What Claude Code remembers

  • it writes down what it learns, in claude/memory/
  • you can read it, correct it, delete it

Another project: ./kingo claude --in ~/projects/thesis

  • Your team's AGENTS.md stays in kingo-pod: Claude Code does not read it when working in a different folder.
  • Instead, it reads that folder's own ~/projects/thesis/CLAUDE.md or ~/projects/thesis/AGENTS.md; kingo does not put files there.

Webhook or HTTP Request: who calls whom?

Webhook: someone calls n8n a page, your browser “here is a question” n8n Example: WS2.4. Your browser calls n8n for the page of drafts (Approvals Page), then with your OK, from a draft's form. HTTP Request: n8n calls someone n8n “here is a mail, sort it” Langflow Example: WS2.3 - Triage New Mail. n8n calls the Langflow flow Triage and reads its answer.

Both ways, an answer comes back. Only the direction differs: who starts the call.

Why a Webhook, and not HTTP?

A Webhook is HTTP: the address where n8n listens. HTTP Request is the node with which n8n calls out.

Why not the other way round?

Langflow's own webhook answers only “started”, never with the answer. And if Langflow called n8n, the model would start actions.

Claude Code can easily write webpages

Claude Code writes the page, and changes the workflows and flows behind it Your page claude/site/ask.html in your browser, at localhost:8080 question answer n8n WS2.11 - Ask its Webhook takes the question, runs the steps Langflow Ask Mailbox searches your mails and answers the page shows · n8n runs the steps · Langflow thinks
  • n8n works behind the page. The page knows only one address. The key for Langflow and all the steps stay in n8n.
  • The page is one file in Claude Code's folder. A tiny web server hands it to your browser.
  • Claude Code checks how the page looks (look), and can click through it (clickthrough).
  • Claude Code can also change the flows: it changes a copy, you test it and switch it on.

Now you build: open your laptop and the workbook

Blocks 1–3

Build a web page that asks your mailbox, and improve the search flow

  1. a simple webhook in n8n
  2. Ask in n8n, and Claude Code writes your page
  3. Claude Code improves the search flow

Outcome: your own page asks your mailbox

Block 4now, or this afternoon

Write your team's rules, together with Claude Code

  1. Claude Code asks you, one principle at a time
  2. you answer and check
  3. it writes them into claude/AGENTS.md

Outcome: Claude Code names your rules

Open the workbook: ws2_s2_workbook.html in your download. With short quizzes along the way.

Something does not work? Ask Claude Code what you see, or raise your hand.

This afternoon: we integrate n8n automation into your project

A mail arrivesor a form on your page n8n takes itand asks Langflow Langflow reads itwho, what, how much n8n checks itwith fixed rules Your page Approve Reject A person decideson your page
  • The automation takes the routine off people: reading the request, looking things up, checking the rules.
  • Your users work on the page. n8n works behind it.

Ideas for your project: what comes in, what waits, who decides

A · KSMC

  • comes in: a mail asking for a quote
  • waits: a draft quote, priced from your price tiers
  • decides: a sales engineer; Approve sends the quote

WS2.12 - KSMC - Quote Intake, … - Quote Queue

B · Kgoda

  • comes in: a trip request on your page
  • waits: trips outside the travel policy
  • decides: the traveller's manager

WS2.12 - Kgoda - Trip Request, … - Trip Queue

C · K-Motor

  • comes in: a supplier's bid by mail
  • waits: every bid, with the rules it breaks
  • decides: the buyer

WS2.12 - K-Motor - Bid Intake, … - Bid Queue

Your team's page is in your download: ws2_s2_team_….html. You set up the templates, let Claude Code explain them, and change them for your team. The tutorial is voluntary.