How do I convert a cURL POST file upload request to an n8n workflow?

Below is one approach to mimicking your cURL command using the HTTP Request node:

---

Key Steps

1. Configure the URL and Query Parameters
   • Set the HTTP method to POST.
   • In the URL field, use the endpoint up to the query string (e.g. https://ff-data-importer.example.com/autoupload).
   • Under Send Query Parameters, add a query parameter with:
     - Name: secret
     - Value: xxxxxx

2. Set Request Headers
   • Under Send Headers, add your headers:
     - Name: Accept  Value: application/json
     - Name: Authorization  Value: Bearer eyJxxxxxx
   (Avoid setting a Content-Type header manually—the node sets the right multipart boundary when using form-data.)

3. Configure the Request Body as Form-Data with a File Upload
   • Enable Send Body and choose the Body Content Type as Form-Data.
   • Click Add Parameter. For the parameter representing your file upload:
     - Change the Parameter Type to n8n Binary File.
     - For Name, enter the field name expected by the API—in your cURL you used json.
     - In Input Data Field Name, specify the name of the binary property coming from your Nextcloud node (for example, if that node outputs the file under the property data, you would enter data; adjust based on your workflow).

4. Ensure the File is Properly Passed
   Make sure that the file downloaded from Nextcloud is available in the binary data under the specified key. The HTTP Request node will pick that binary file and pass it as a multipart/form-data field.

---

Troubleshooting the “Service Refused the Connection” Error

• Endpoint Verification:
  As the cURL works, double-check that you are not inadvertently modifying the endpoint. Using query parameters via the node (instead of appending directly in the URL) can help manage the request URL.

• Header Configuration:
  Ensure you are not setting a conflicting Content-Type header manually. Let the HTTP Request node handle the multipart boundaries automatically.

• Binary File Key:
  Verify the field name in Input Data Field Name exactly matches the binary property name from your previous node. Otherwise, no file data will be attached.

• Network/Proxy Issues:
  Since you’re running n8n in Docker on Linux, also check your Docker network configuration to make sure the container has access to https://ff-data-importer.example.com.

---

Example Walkthrough

1. URL & Query Parameter

   • URL:

https://ff-data-importer.example.com/autoupload

• Query parameter:

secret : xxxxxx

2. Headers:

Accept: application/json
Authorization: Bearer eyJxxxxxx

3. Body (Form-Data):
   Add a new field with:

Name: json
Type: n8n Binary File
Input Data Field Name: <your binary field name from Nextcloud node, e.g., "data">

---

Following the above configuration, your n8n HTTP Request node should effectively emulate the cURL command by sending a POST request with a file upload. If you’re still getting the connection refused error, recheck the Docker networking and firewall settings to be sure that n8n can reach the external service.

This setup follows the guidance for configuring the HTTP Request node to send multipart form-data with an uploaded file.