Thanks @RicardoE105 , but it does not work. I got this error
{
"status": "rejected",
"reason": {
"message": "Request failed with status code 400",
"name": "Error",
"stack": "Error: Request failed with status code 400 at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15) at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (internal/streams/readable.js:1327:12) at processTicksAndRejections (internal/process/task_queues.js:80:21)"
}
}
@RedPacketSec I totally agree with your idea. It’s a bit tricky to transpose curl request that I get as example in Postam to N8N object.
@RedPacketSec ahh yes, that would be amazing. We have talked about it internally. I guess at some point it is going to make it to the roadmap.
@mcc37 I used postman to map the curl request to the request library, which n8n “uses” behind the scenes. Do you have the docs of his API so that I can have a look at it and might spot the issue?