Describe the problem/error/question
I have 5 APIs with OpenAPI specifications that I want to use in n8n. While I could technically use HTTP Request nodes for each call, this creates a lot of extra work and makes reuse difficult across workflows.
I’m looking for a way to automatically generate n8n nodes from OpenAPI specifications. I’ve found several scripts and tools online but they either:
- Don’t work properly
- Have very limited documentation
- Are too complex for me to figure out
Question: Has anyone successfully generated n8n custom nodes from OpenAPI specs? I’m looking for:
- A working method/tool to convert OpenAPI to n8n nodes
- Someone who has done this before and can guide me
- Or someone willing to help us with this for compensation
The goal is to have proper custom nodes for each API that handle authentication, parameters, and responses cleanly rather than manually configuring HTTP requests every time.
What is the error message (if any)?
No specific errors - the tools I’ve tried either fail silently or the documentation is insufficient for me to use them properly.
Please share your workflow
Not applicable - looking for development solution rather than workflow help.
Share the output returned by the last node
Not applicable.
Information on your n8n setup
- n8n version: [Your version here]
- Database (default: SQLite): SQLite
- n8n EXECUTIONS_PROCESS setting (default: own, main): own
- Running n8n via (Docker, npm, n8n cloud, desktop app): npm
- Operating system: Ubuntu
Additional context:
- I have 5 different APIs, all with proper OpenAPI 3.0 specifications
- Currently using HTTP Request nodes but this is becoming unmaintainable
- Open to paid solutions or hiring someone to help implement this
- The APIs handle different business functions so having dedicated nodes would greatly improve workflow clarity and reusability