I Built a Tool That Turns Any OpenAPI Spec Into n8n Workflow Nodes in Seconds
Source: Dev.to
The Pain Points
- Every API endpoint means a new HTTP Request node to configure manually.
- Copy‑pasting URLs, headers, and parameters is tedious and error‑prone.
- Complex APIs with dozens of endpoints can take hours of clicking.
- OpenAPI specs contain all the needed information, but n8n can’t read them directly.
- One typo in the endpoint path and the workflow breaks silently.
What If You Could…
Paste an OpenAPI spec and get ready‑to‑use n8n nodes instantly.
How It Works
- Paste your OpenAPI/Swagger spec – provide a URL, upload a file, or paste raw JSON/YAML.
- Select the endpoints you need – cherry‑pick only the ones you’ll use.
- Copy → Paste into n8n – one click copies the node configuration, ready to drop into your workflow.
That’s minutes of manual work compressed into seconds.
Interface Options
- URL fetching – point to any public OpenAPI spec URL.
- File upload – drop your local spec files.
- Direct paste – copy‑paste spec content directly.
- Popular APIs – pre‑configured examples (GitHub, Stripe, Slack, Discord, etc.).
Features
| Feature | Description |
|---|---|
| Multi‑format support | OpenAPI 3.x & Swagger 2.0, JSON & YAML |
| Selective conversion | Pick specific endpoints, skip the rest |
| Base URL override | Point to staging, production, or localhost |
| Browser persistence | Conversions are saved automatically |
| Multi‑tab workflow | Manage multiple API conversions at once |
| One‑click copy | Clipboard‑ready n8n node configurations |
| Zero friction | Browser‑based, no install, no account required |
| Spec as source of truth | Uses existing OpenAPI documentation |
| Selective imports | Avoid bloating your workflow |
| Time savings | What took 30 minutes now takes ~30 seconds |
Try It
- Converter:
- Popular APIs: GitHub, Stripe, Slack, Discord, etc. (pre‑loaded in the tool)
- GitHub repo:
quochuydev/n8n-openapi - Live demo:
How do you currently handle integrating complex APIs into n8n? Feel free to share any endpoints or specs that break the converter—PRs are welcome!