A node-based workflow tool as an agent runtime
Using n8n as the "tool provider" for an LLM agent. Sub-workflows become tools the model can call. Changing agent capabilities becomes a workflow edit, not a deploy.
ReadSenior full-stack engineer with thirteen-plus years across backend services, web apps, and AI-agent platforms. This is where I write about architectures I've shipped, patterns I've come to trust, and side-projects I return to on weekends.
Building Model Context Protocol servers for two very different jobs — fronting a SaaS with an OAuth broker, and exposing an internal knowledge base to authenticated users.
ReadOne service becomes the audit trail and the dispatcher. How persistence-before-fanout, HMAC replay protection, and presigned-URL attachment sync fit together.
ReadA hand-rolled state machine for LLM-driven chat: intent routing, tool invocation, SSE streaming, and out-of-band completion — and why we skipped LangGraph.
ReadThe front-of-funnel decision — direct answer, clarify, or call a tool — and why building it as a small, dedicated service pays off.
ReadA policy-driven router that sits between a chat frontend and an LLM stack — classifies intent, dispatches to tools, workflows, or direct answers, and streams the result back over SSE.
The front-of-funnel decision for an LLM assistant — direct-answer vs clarify vs call-tool — using a live agent registry and structured LLM outputs.
A durable event bus for agent platforms — authenticate, persist, and fan out to Slack, ticketing, email, and audit consumers via EventBridge + SQS.
Model Context Protocol servers that expose internal capabilities — HR systems, knowledge search — as LLM-callable tools with OAuth 2.1 + PKCE.
Using a node-based workflow engine as the "tool provider" for an LLM agent — sub-workflows become tools the model can call.
A secure browser-based chat assistant — React + Server-Sent Events streaming from an LLM middleware over AWS Lambda, with per-user history in DynamoDB.
A reusable React + JSS component library documented in Storybook — used across a fleet of internal tools to enforce consistency and accessibility.
A React 18 SPA for raising, tracking, and approving support tickets across multiple business groups — with contextual guided tours and knowledge-base search.
I'm always happy to talk about backend architecture, LLM stacks, and the tricky bits between them. Best reached over email.