Unable to POST request from Pabbly Connect to Zoho Desk’s Articles API for creation of Article

[taxajca]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZkMDYzNDA0MzA1MjY0NTUzMzUxMzYi_pc

Your Task History ID

IjU3NjcwNTZkMDYzNDA0MzA1MjY0NTUzMzUxMzYi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

I am trying to send a POST request from Pabbly Connect to Zoho Desk’s Articles API, but the step consistently fails with the following error returned by Zoho:

ErrorCode: UNSUPPORTED_MEDIA_TYPE
Message: The given content type is not supported. Please provide the input Content-Type as application/json

However, inside Pabbly I have already:

1. Set the HTTP action to POST
2. Selected Raw / JSON as the payload format
3. Added the header Content-Type: application/json manually
4. Added Authorization and orgId headers correctly
5. Used the exact same JSON body that works successfully when tested through cURL outside Pabbly

Despite this, Zoho Desk is receiving a different Content-Type (most likely text/plain), which is causing the API to reject the request.

Details:
API Endpoint:

https://desk.zoho.in/api/v1/articles?orgId=60020823734

Headers added in Pabbly:
Content-Type: application/json
orgId: 60020823734
Authorization: Zoho-oauthtoken <TOKEN>


JSON Body sent (shortened for support):
{
"title": "New TDS Rules for Freelancers in 2025",
"seoDescription": "Latest 2025 TDS updates...",
"permission": "ALL",
"authorId": "22372000000094004",
"seoTitle": "New TDS Rules 2025",
"seoKeywords": "TDS, freelancers, 2025",
"tags": ["TDS", "freelancers"],
"expiryDate": "",
"isSEOEnabled": true,
"answer": "<h2>Introduction</h2><p>...</p>",
"isTemplate": false,
"permalink": "tds-rules-2025",
"categoryId": "22372000000094160",
"status": "Draft"
}


Request for help:

1. Can you please check whether the Webhook/HTTP module is overriding the Content-Type header or forcing text/plain when JSON is pasted into the body field?
2. How can I ensure that Pabbly sends the body with Content-Type: application/json exactly as required by Zoho Desk?
3. Is there a way to inspect the raw request Pabbly is actually sending so I can compare it with my working cURL request?
4. If your team can test a sample JSON POST to Zoho Desk from your end, it will help confirm whether the issue is internal to Pabbly’s encoding.

This automation is critical for generating and publishing articles programmatically from Pabbly → OpenAI → Zoho Desk, so your quick assistance will be highly appreciated.


Thank you,
Team TAXAJ
TAXAJ Corporate Services LLP