I wanted to share something I’ve been working on because I think a few of you might find it helpful. Like most of you, I’ve spent more time than I’d like manually setting up HTTP Request nodes in n8n based on API documentation — copying URLs, setting methods, working out query parameters, building the schema, it’s quite repetitive.
So I built a browser extension to automate the entire process.
You open it on any API documentation page, and it scans the content to identify valid endpoints. Once it finds them, you can select which requests you want, and the extension will package them into properly structured n8n HTTP node — ready to import straight into your workflow.
At the moment it doesn’t handle authentication (by design), so you’ll still need to plug in your credentials or headers manually, but everything else — URL, method, path params, query params, body schema — it sets that all up for you.
It’s been a bit of a time-saver on my end already, so I figured it might help others here too.
The site is n8endpoint.dev I’ve put up a waiting list just to get a sense of whether people are actually interested before scaling things out.
I don’t love the idea of waiting lists either, but I just wanted to check whether this is actually something people in the community would use before going all-in. Here’s a quick demo video below so you can get a feel for how it works.