November 2026 Summaries

Webflow describes an architecture for using natural-language prompts to create and operate n8n workflows headlessly, with n8n serving as the orchestration layer behind an editor and chat interface. Tenant isolation is handled through separate n8n Projects, while hot and cold infrastructure shards separate urgent executions from bulk workloads to reduce noisy-neighbor effects. Webflow centrally manages third-party OAuth credentials through its own Secret Store and mirrors them into n8n, while all workflow triggers, including scheduled jobs, invoke webhook-based workflows from Webflow services. A stateless builder service converts prompts into TypeScript using an n8n workflow SDK, compiles it into workflow JSON, validates permitted nodes and structure, and retries model-generated code failures up to four times; this approach was adopted because typed SDK generation catches invalid connections and unsupported APIs before runtime more reliably than raw JSON. The platform limits supported n8n nodes through a version-pinned allowlist, rebuilds complete workflows for user-requested edits, and uses a planning step to ask clarifying questions when prompts omit essential details. Operational challenges included reconciling missed n8n execution events through polling and telemetry, while evaluation suites assess whether workflows build, execute in sandboxes, and fulfill requests. Load tests found that a queue-mode deployment with one main node and four workers sustained roughly 500 CPU-intensive executions per second before the main node became unstable, with Redis and Postgres remaining resilient.