n8n Assistant: describe the job, keep the workflow you can edit

Most automation projects stall in the same place. You can say what you want in a sentence — “new form → enrich company → route to sales or reply” — but that isn’t the same as knowing which nodes to pick, how to wire them, or what to do when the first run fails.

n8n just shipped n8n Assistant for that gap: plain language in, a real workflow on the canvas out.

Job to be done: get from “I know the outcome” to a workflow your team can see, edit, and run again next month — not a one-shot script that dies with the chat.

Why this matters for UK operators

There’s no shortage of AI that will “build an automation” from a prompt. The pain shows up later:

• Nothing to inspect — you get code someone has to host, secure, and own
• Nothing that persists — the assistant does the task once; there’s no handoff next week
• Nothing to explain — “the model decided” doesn’t help a colleague who didn’t write the prompt

n8n’s bet is different: Assistant builds standard n8n workflows on your canvas — same nodes, same execution history, same project. You can open a node, change a filter, add a confirmation step. The person who typed the prompt doesn’t own the result forever.

What it actually does (plain English)

From n8n’s own write-up:

• Asks before it assumes (which form? which channel?)
• Builds on your canvas — not a separate black-box product
• Requests credentials when a node needs them, not in a giant setup quiz first
• Runs the workflow, reads the execution, debugs failed nodes, and iterates with you
• Asks before anything consequential (credentials, activation)

That’s the same bar we use on digitalbydefault.ai under Automation: triggers you understand, steps you can see, failure modes you can fix.

What it isn’t (yet)

Worth saying out loud so expectations stay honest:

• First build isn’t guaranteed production-ready — review before you rely on it
• It can’t create third-party accounts you don’t have
• It isn’t proactive (won’t invent automations you didn’t ask for)
• Preview flag — active development; Cloud on by default for many new instances; self-hosted Docker from 2.36 with your own keys

Credits come from your plan’s AI allocation. Treat it like a build tool with a meter, not free magic.

How to use this on the directory

1. Open Automation on digitalbydefault.ai

2. Start with workflow builders in the n8n / Make class before buying another vertical SaaS that “has AI” but won’t talk to your stack

3. If you’re evaluating n8n specifically, read their Assistant docs and try a real job (inbound form routing, spreadsheet → CRM sync, failed-run daily summary)

Bottom line

If the pain is “we keep describing the automation and never shipping the graph,” n8n Assistant is a serious step: language in, editable workflow out. Keep the canvas you can hand to a colleague. That’s the kind of Automation listing that belongs in an operator directory — not another chat that forgets what it did yesterday.

Source: Introducing n8n Assistant · n8n Blog · 9 Sep 2026