AiAdvisors
Back to the index
//Weekly

Week 41 / 2026.

A short record of changes between issues. Full answers and charts live on the question pages.

Data window
Oct 5–11, 2026
Last updated
Oct 23, 2026
Author
Romuald Członkowski

Commentary

Between 5 and 11 October, n8n-mcp produced 80,197 workflows, 11,457 a day on average, across 2,054,044 tool calls with a 0.10% error rate. That is 10% more workflows a day and 22% more calls than the previous issue, and the data does not show what sits behind the move. There are 151,238 active installs, 8% of them create workflows, and 319 installs hold 31 workflows or more, 2.7% of the creators.

This is the first retention figure after the telemetry move. Of the 6,965 installs that started in the week of 28 September, 45% were still active a week later, which is this window. That cohort's week one covers the whole window, so this is not a reading taken mid-week. I don't hold the figure against issues from before 27 September.

Each workflow created draws 7.3 updates. The window holds 140,248 edits, 2.67 operations and 1.45 changed properties each on average, a median of 877 ms, a verifiable improvement in 56% of them. Among the edits with a recognised intent, changing configuration leads (52,448), adding functionality is more than twice as rare (19,602), and fixing validation accounts for 4,394. Reads make up 61% of tool calls, writes 11%, and fetching executions alone 36% of everything. Budget an implementation for seven returns to a workflow, not for building it once.

This window added 31,558 workflows to the corpus, which now holds 1,190,875, with a median of 7 nodes. Code appears in 77% of them, HTTP Request in 59%, an LLM model node in 6%, an AI Agent in 4%; among model nodes, OpenAI holds 34%, Anthropic 21% and Google Gemini 19%. Data Table is in 12.1% of this window's workflows and has been climbing since March, when it stood at 3.3%; in the October data it sits at 12.2%. "data table" was also the most searched phrase, asked for by 192 unique installs, ahead of webhook at 137.

Changes versus the previous issue

figurevaluechange
Workflows created80,197—
Workflows per day11,457+10%
Tool calls2,054,044+22%
Calls ending in error0.10%-25%
Failed validation0.7%-8%
Active installs151,238+6%
Week-1 retention45.2%—
Workflows added to corpus (week)31,558+22%

This week's answers

Most searched nodes

data table (192) · Webhook (137) · http request (74) · Telegram (44) · google sheets (42) · schedule trigger (41) · anthropic (37) · whatsapp (34) · Slack (27) · gemini (27)

n8n pitfalls · high

Webhook node response must be sent explicitly

When using the Webhook node with "Respond to Webhook" set to "Using Respond to Webhook Node", you must include a "Respond to Webhook" node in your workflow. Without it, the webhook caller will timeout waiting for a response. For simple acknowledgments, use "When Last Node Finishes" response mode instead.

//Contact

Let's talk about AI in your business

Tell Alicja what takes up time in your business. She'll book you a free strategy consultation with me.

Prefer a calendar? Pick a time

or write: romuald@aiadvisors.pl · +48 695 263 884