Issue with a Rest API Call trigger
I have an issue with a Rest API Call trigger, I am triggering a webhook from Inoreader with the content of an RSS in Json. When I post it from Postman or Hoppscotch it works, but when it's coming from Inoreader Buildship most times the body has no content.
Any idea what could be causing this? I cannot change the way the webhook is sent from Inoreader, is there anything I can change in Buildship to make sure the content is read properly?
I tried sending the same webhook to webhook site and this is what is received.
Request Details
POST https://webhook.site/7748369e-de5c-4661-b250-d2be4740ff62
Host 92.247.181.45 Whois Shodan Netify Censys VirusTotal
Date 13/10/2024 22:00:42 (13 minutes ago)
Size 3.8 kB
Time 0.000 sec
ID 99e0eab4-72b4-4599-85ac-8da0613ba15d
Note Add Note
Headers
content-length 3869
x-inoreader-rule-matches-total 31
x-inoreader-rule-matches-today 13
x-inoreader-rule-name Summarize with Buildship
x-inoreader-user-id 1005111691
content-type application/json
accept /
user-agent Inoreader Webhook Processor/1.0
host webhook.site
Query strings
(empty)
Form values
(empty)
2 Replies
AI Support Bot Information
<@222952796721250306> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
It seems like you are facing an issue where the body of the webhook from Inoreader is empty when received in Buildship, but it works fine when tested via Postman or Hoppscotch. This could potentially be due to how Buildship is handling the incoming webhook requests.
Here are a few troubleshooting steps and considerations that might help resolve the issue:
1. Webhook Configuration: Double-check the Inoreader webhook settings and ensure that the configuration matches the expected format for the Buildship trigger. Sometimes, minor mismatches in configuration can cause parsing issues.
2. Content-Type Header: Verify that the
Content-Type header is correctly set to application/json by Inoreader, as this indicates that the payload is in JSON format.
3. Inspect the Payload: Compare the payload received from Postman/Hoppscotch and Inoreader to see if there are any differences in the JSON structure or headers.
4. Buildship Trigger Settings: Ensure that the REST API Call trigger in Buildship is correctly set up to handle JSON payloads. The trigger should not have any restrictions or conditions that could cause the body to be ignored.
5. Debugging and Logging: Add logging or return nodes in your Buildship workflow after receiving the webhook to capture the raw request payload and headers. This can help identify what is being received by Buildship.
6. Middleware or Proxy: Use a middleware or proxy service (like webhook.site) to capture the webhook payload from Inoreader before it reaches Buildship. This can help verify the content and troubleshoot issues.
If these steps do not resolve the issue, it may be beneficial to consult Buildship's support or community channels for further assistance【4:2†buildship-support-site.json】.
BuildShip AI Support