bulaev.ai

n8n

Open source

Agents · Work OS

Visual workflow automation you can self-host, with AI agent nodes, human-in-the-loop steps and MCP support.

Open n8n.io

What it is

n8n is a workflow automation platform: a canvas where nodes (HTTP request, database, Slack, Gmail, a hundred SaaS APIs) are wired into flows triggered by webhooks, schedules or events. Unlike the no-code incumbents, every node can drop into JavaScript or Python, and the product has grown an AI layer: agent nodes with tool calling, RAG pipelines with vector stores, memory, multi-agent flows, guardrails and explicit human-approval steps, and connections to MCP-compatible tools. You can point a flow at a hosted model or a local one without rebuilding it.

The source is on GitHub under a "fair-code" license (free to self-host and modify, with restrictions on reselling as a service), a Docker image runs it in one command, and n8n Cloud is the managed option with its own plans.

Where it fits in the AI OS

Work OS, the scheduled and event-driven glue between systems for the parts of the company that do not deserve a code repository: "when a Stripe payment fails, wait two days, email, then post to Slack", "every Monday, pull last week's analytics and draft the digest". It is also the fastest way to give a non-developer teammate an agent with approvals.

Insider notes

members

How Serge's stack uses it

The membership's scheduled jobs (digests, star refreshes, sync to git and Telegram) are Worker crons in code rather than n8n flows; automation appears in the ideas taxonomy as a topic ("n8n, queues, cron, an agent on a schedule").

[SERGE: fill in]

Setup in 5 minutes

  1. docker run -it --rm -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n, open http://localhost:5678, create the owner account.
  2. New workflow: Schedule trigger (Monday 08:00) → HTTP Request to your analytics endpoint.
  3. Add an AI Agent node with a chat model credential and the HTTP output as context; prompt it to write a five-line summary.
  4. Add a Slack node to post the summary; add a "Wait for approval" step before it if the output goes to customers.
  5. Activate the workflow and run it once manually to check the log.

Alternatives

  • Zapier / Make — hosted, larger app catalogs, per-task pricing.
  • Windmill / Activepieces / Trigger.dev — open-source alternatives with a more code-first feel.
  • Cloudflare Workers cron + Queues — no UI, full control; what this stack uses for its own jobs.