Short answer: use the new n8n Agents tab when you want a reusable assistant that decides its own steps and can be reached from chat, Slack or a schedule. Use the AI Agent node when a fixed workflow should stay in control and the model handles just one step. For scraping and monitoring jobs that must run the same way every time, a plain workflow with an Apify actor is still the safer default.

What did n8n actually launch?

In September 2026 n8n announced n8n Agents. According to n8n's community announcement and coverage by Kingy.ai, an agent is now its own object in the product: you set it up once with a model, instructions, tools and channel connections such as Slack. It can then run on a schedule, answer in chat, or be called from a workflow through a new Message an Agent node. The feature is described as a preview and needs n8n 2.32.3 or higher.

The existing AI Agent node was not removed. The launch post says everything you built with it keeps working. That leaves three things with confusingly similar names, so here is how they differ.

What is the difference between the Agents tab, the AI Agent node and a workflow?

Plain workflowAI Agent nodeAgents tab + Message an Agent
Who controls the stepsYou, node by nodeYou, with the model handling one stepThe agent decides its own steps
Where it livesInside a workflowInside a workflowA reusable object, callable from chat, Slack, schedules or workflows
Output is the same every runYesMostlyNo, by design
StatusStableExisting feature, unchangedPreview

The n8n docs for the Message an Agent node say it sends a message to an agent from a workflow and passes the reply to the nodes that follow. They also note that channels and schedules only run the published version of an agent, and that each message you send counts as one execution. That last point matters for cost: a chatty agent can burn through executions faster than a workflow that runs once.

Which one should a scraping workflow use?

Ask one question: does the job have a fixed shape? If yes, build a workflow. If the input is open-ended, consider an agent.

  • Fixed shape (use a workflow): "Every morning, run the scraper, keep only new rows, post them to Telegram." Same steps, same output, nothing to decide. Adding an agent here only adds cost and variance.
  • One fuzzy step (use the AI Agent node): "For each scraped lead, classify whether it is a real buying request." The workflow stays in control and the model does one judgement.
  • Open-ended requests (try the Agents tab): "A teammate asks in Slack: what changed on our competitor's pricing page this week?" The agent picks the tool and answers. This is where a reusable agent with several tools earns its keep.

A useful rule: put the data collection in a deterministic step and let the agent read the result. Scrapers that return clean, structured records give an agent far less room to improvise than a model browsing pages on its own.

How do you give an n8n agent reliable web data?

An agent is only as good as its tools. Three actors from our catalogue fit the "tool for an agent" pattern because they return structured output on a schedule instead of free text:

  • Company Domain to Job Postings turns company domains into their open roles in one schema, a hiring signal an agent can call and summarise.
  • Website Change Monitor returns a clean added/removed diff of a page with severity scoring and keyword watching, with alerts to Slack, Discord, Telegram or any webhook. That makes "what changed on this page?" a question an agent can answer from data.
  • Dataset Diff returns only new, edited and removed rows between runs of any Apify actor. Its listed pricing is $0.00002 per item compared, $0.0015 per change returned and $0.004 per alert, so checking 10,000 unchanged rows costs $0.20. Feeding an agent the delta instead of the full dataset keeps prompts small.

The pattern is the same each time: the actor does the collection, n8n handles scheduling and delivery, and the agent (if you use one) reads a small, structured result. If you are still comparing orchestrators, see n8n vs Zapier vs Make. If you run scraping workflows on n8n already, check the n8n 3.0 upgrade checklist first, and read what n8n is and is not before planning around its licence and pricing.

What are the risks of moving to agents too early?

  • Preview status. n8n describes the feature as a preview, so interfaces and behaviour can change. Do not move a production alerting job onto it yet.
  • Execution counts. Per the docs each message to an agent counts as one execution. Check your plan before wiring an agent to a busy Slack channel.
  • Non-repeatable output. An agent that decides its own steps can answer differently on two runs. For reporting you need to reproduce, use a workflow.
  • Published versus draft. Schedules and channels run only the published version, so an edit you made but did not publish will not take effect.

A simple migration plan

  1. Keep every existing scheduled scraping workflow as it is.
  2. Pick one low-stakes question people ask repeatedly, such as "any new leads today?".
  3. Create an agent for it with one tool: the actor run that already feeds your sheet.
  4. Compare its answers with the sheet for two weeks before trusting it.
  5. Only then add a second tool or a second channel.

What does each option cost you in practice?

We have not benchmarked these three options against each other, so no timing or accuracy figures are claimed here. What can be said from the docs is structural. A workflow run is one execution however many nodes it has. An agent reached from chat or Slack counts one execution per message, so a team that asks ten questions a day creates ten executions a day before any scheduled run. The model calls behind an agent are billed by whichever model provider you connect, and the scraping itself is billed by the actor, for example per result or per event on Apify. Add those three lines (n8n executions, model usage, actor usage) and compare them to the cost of the same job as a plain workflow. For a daily job with a fixed shape the workflow almost always wins on both cost and predictability.

Which questions suit an agent, and which do not?

Agents shine when the question is phrased differently each time and the answer needs a choice of tool. "Which of our tracked competitors changed pricing this week, and is any change above 10 percent?" is a good example, because the agent can call a monitor, read the diff and answer in plain language. They are a poor fit for anything you must audit line by line, such as invoicing totals or compliance checks, where the same input must always give the same output.

A second test is blast radius. If a wrong answer only costs someone a minute, an agent is fine. If a wrong answer triggers an email to a customer or a purchase, keep a deterministic workflow in the middle and add a human approval step before the action happens.

How do you keep an agent from calling the wrong tool?

  • Give each tool one clear job. A tool called "list open roles for these company domains" is easier for a model to choose correctly than a generic "search the web" tool.
  • Return small outputs. Pass only the delta or the top ten rows. Long tool results crowd out instructions.
  • Write the instructions as rules. State when to use each tool, what to do when a tool returns nothing, and that the agent must say so rather than guess.
  • Test on the draft, then publish. Because schedules and channels run only the published version, publish deliberately and note the date.

FAQ

Is the n8n AI Agent node deprecated?

No. The launch announcement says the AI Agent node is unchanged and existing workflows keep working. The Agents tab is a separate, newer way to define reusable agents.

What does the Message an Agent node do?

It sends a message to an agent from inside a workflow and returns the reply to the following nodes, according to the n8n docs. It can also define an agent inline in the node.

Do I need a new n8n version for Agents?

The launch post says n8n 2.32.3 or higher, and the feature is labelled a preview. Check the n8n release notes for the current state before you rely on it.

Should an agent scrape websites directly?

For repeatable jobs we would not. Let a purpose-built scraper return structured data and let the agent read it. That keeps cost, speed and output predictable.

Try it

Browse the developer tools hub for actors that work well as n8n or agent tools, then try the actors on Apify and plug one into a schedule.

Sources: n8n community announcement "Introducing n8n Agents", n8n docs for the Message an Agent node, and Kingy.ai coverage, as summarised in search results in November 2026. Details may change while the feature is in preview.

Last updated: November 2026

Need help implementing this?

I build custom automation, scraping pipelines, and AI solutions for businesses. 170+ projects delivered with a 5.0 rating across 174 reviews. Tell me about your project - I reply within 24 hours.

Start Your Project →