Evidence boundary: n8n documents an OpenAI node and credential setup. The source supports the integration path only; workflow economics depend on each user's nodes, prompts, models, and retry behavior.
Documented integration pattern
- Create the documented OpenAI credential.
- Choose a model and operation explicitly.
- Limit retries and make side effects idempotent.
- Measure token use across the full workflow, including failed runs.
Relevant provider records
- OpenAI API · official channel
First-party evidence
- n8n OpenAI node documentationFirst-party node documentation.
What this page does not claim
It does not claim that the project's hosted service uses these providers in production, that the integration handles every feature, or that any private cost or revenue figure is known.
Questions developers ask
Does this page prove n8n's private production stack?
No. It documents only the linked public repository or first-party documentation evidence and makes no private deployment claim.
Does APIDir know this project's provider spend or revenue?
No. APIDir does not infer private usage, cost, customer, or revenue information from a public integration.
How should I reuse this integration pattern?
Open the cited source, confirm its current license and configuration, then test the relevant provider record against your own workload.