Last updated September 2026
n8n's native AI nodes let a workflow call an LLM mid-process -- not a separate AI tool bolted on, but a step inside the same automation that's already handling your data.
Quick answer: An n8n workflow can call OpenAI, Anthropic, or a self-hosted model at any point -- summarizing a call transcript, classifying a support ticket, or drafting a follow-up -- then continue the workflow based on what comes back. The AI step is just another node, not a separate system to maintain.
We'd rather tell you honestly than sell you AI for its own sake.
Every implementation starts with the same process we use for everything — audit first, then build what the audit actually finds, not the other way around.
n8n's native AI nodes work with OpenAI, Anthropic, and most other major LLM providers via API, plus self-hosted open-source models if you want the AI layer to stay on your own infrastructure too.
Yes, when a workflow calls a hosted model (OpenAI, Anthropic, etc.), that specific data goes to that provider's API for processing. For genuinely sensitive data, self-hosted open-source models keep everything on your own infrastructure -- something we scope during the audit if compliance is a factor.
No -- n8n's execution-based pricing (or free self-hosted) covers running the workflow itself. Each AI API call has its own separate cost from the model provider, billed directly to your account with them, not through n8n.
No -- calling an LLM from an n8n workflow doesn't require training or fine-tuning a model, just a well-designed prompt and the right trigger conditions. That's the workflow design work we handle.
That's exactly what a Discovery Call is for — an honest look at whether AI actually helps here before we recommend anything.
Tell us about your business →