extended-salmon•16mo ago
Help Needed with Inconsistent POST API Responses via make.com
Hi everyone,
TLDR: I'm experiencing inconsistency with POST API calls via make.com in my Voiceflow project. Despite identical setups, calls intermittently return either a successful (Status 200) or failed (Status 400) response, primarily differing in the content-length field
I've been working on a project using Voiceflow and have come across an error with POST API calls that I'm making through make.com. Initially, everything works perfectly with a successful response, but subsequent attempts are hit or miss, even though I'm not changing anything between calls. Here are the details of what I'm seeing:
Successful Call: - Status: 200 - Content-Length: 8 - Example Response:
Failed Call: - Status: 400 - Content-Length: 48 - Example Response:
I don’t understand what the problem could be since the only apparent difference is the
content-length
. Could you perhaps shed some light on why this might be happening or guide me on what steps I could take to fix this? Any insights or tips would be hugely appreciated!
The screenshots of the problem are attached:
Picture 1: My API call from make.com as web-hook
Picture 2: My initial successful API call:
Picture 3: My second failed call (look at the time difference between picture 3 and 2, I truly did not change anything in between)
Thanks so much for your help!
Best,
Oscar


3 Replies
Content length is going to change every run based on what you're doing in Make.
What are you passing into the body of the webhook / returning on the webhook capture?
extended-salmonOP•16mo ago
he, thanks for your response! this is what i am passing to make.com

You don’t need that header info