0.0.3 • Published 8 months ago

@n-octo-n/n8n-nodes-curl v0.0.3

Weekly downloads
-
License
MIT
Repository
github
Last release
8 months ago

n8n-nodes-curl

This n8n node lets you call out to the cURL binary to do any kind of supported HTTP operation, via the standard curl command-line syntax.

n8n is a fair-code licensed workflow automation platform.

The statically-compiled cURL binaries used by this node are provided by stunnel/static-curl. Refer to that repository for a list of the features provided by the binaries.

Installation
Compatibility
Usage
Quirks
Resources

Installation

Follow the installation guide in the n8n community nodes documentation. The npm name for this package is @n-octo-n/n8n-nodes-curl.

Compatibility

Tested on n8n 1.4.0 as of 2023/08/29.

Usage

This node simply provides an input field to pass shell command-line arguments to cURL, and outputs the following object in case of success:

{ key           | example
----------------|----------------------------------------------------
  data          | <p>This is not the string you were expecting.</p>
  statusCode    | 200
  statusMessage | OK
  headers       | { "content-type": "text/html; charset=utf-8" }
}

In case the response includes a set-cookie header, the node's output will also include a setCookie key with the following content, that allows for easy retrieval of all cookies sent by the server within your workflow:

{ key    | example
---------|----------------------------------------------------
  array  | [ "Yummy=1", "SessionId=cafebabe" ]
  string | "Yummy=1; SessionId=cafebabe"
  object | { "Yummy": { "value": "1" }, "SessionId": { "value": "cafebabe", "domain": "example.com" } }
}

Be careful of what data you pass to the input field of this node, as everything is simply handed to the system shell to be passed to cURL. Be especially mindful of using shell quotes and escapes when needed; use JavaScript functions if you need to filter data.

On first use, the node automatically downloads the correct cURL binary for your system architecture (~3 MB, but varies), then stores it for future use. Just wait if it seems like the node takes a while to elaborate.

Quirks

  • Currently, this node only supports dealing with text data. If any HTTP endpoint you call with this node returns binary data, there's no guarantee that the result will be fine.
  • Currently, only Linux hosts are supported. All kinds of containers work fine, but Windows and macOS don't work yet.

Resources