[Custom Node] cURL Request (beta)

Built with n8n
1

Hi everyone

I recently created a custom cURL Request Node in n8n that enables users to directly execute cURL commands within their workflows. This node allows for greater flexibility and makes it easier to bypass limitations like special headers, request formats, or authentication methods that might not be easily handled with the regular HTTP Request node.

Why This Custom Node?
While n8n’s HTTP Request node is extremely versatile, there are instances when you need to send a request in a way that’s close to what you would do in a terminal using cURL. This could be due to:

  • Custom headers and methods that are specific to cURL.

  • Postman-like request formats that are easier to configure directly in cURL.

  • Bypassing security restrictions that might be more lenient with cURL requests.

  • Mimicking real-world use cases where API access is limited to tools like cURL.

  • Predefined and generic authentication (WIP)

With this custom node, you can now execute any cURL command directly within n8n, making it as easy as possible to integrate those “trickier” API calls.

image
image227×182 4.02 KB

{E15D81C7-5EF6-4484-B626-A61403F6034F}
{E15D81C7-5EF6-4484-B626-A61403F6034F}1858×833 71.8 KB

This is my first custom node, so there might be a few bugs along the way. I’d really appreciate any feedback you have! :slightly_smiling_face:

Download: https://github.com/hussainalhaddad/n8n-nodes-curl-request

2

Hey @hussainalhaddad, hope all is good. Welcome to the community.

This looks great. Could you please provide an explicit example or examples of which shortcomings of HTTP Request node can be avoided by using this node?

1個讚
3

Hi @jabbson

Thanks for the warm welcome! :slightly_smiling_face:

I have many cases where I face issues with the HTTP Request either not returning any response or those which are protected by bot protection, but they work just fine using Postman.

4

Absolutely. Providing concrete examples will help users to understand when to use your node as opposed to HTTP Request node.