hey, I'm sending webhooks to Clay from Outreach receiving application/vnd.api+json content type. Clay is parsing this as a blank json payload. is this content type just not supported and I need to find a workaround, or is there anything that can be done here?
Clay expects application/json content type for webhooks. [1] The application/vnd.api+json format from Outreach might be causing the parsing issue.
Can you copy and paste the JSON payload you're sending so I can help troubleshoot this further? This will help identify if it's a content type issue or something with the JSON structure itself.
{ "data": { "attributes": { "createdAt": "2025-12-04T10:36:19.000Z", "updatedAt": "2025-12-04T10:36:19.000Z", "activeAt": "2025-12-04T10:36:19.000Z", "stateChangedAt": "2025-12-04T10:36:19.000Z", "state": "active" }, "relationships": { "batchItemCreator": { "type": "batchItemCreator", "id": 125079 }, "mailbox": { "type": "mailbox", "id": 23 }, "prospect": { "type": "prospect", "id": 317041 }, "sequence": { "type": "sequence", "id": 46 }, "user": { "type": "user", "id": 22 } }, "type": "sequenceState", "id": 58081 }, "meta": { "deliveredAt": "2025-12-04T02:36:20.226-08:00", "eventName": "sequenceState.created", "jobId": "a193b1b2-b33f-4cb8-ac33-68f13118a1c5", "actor": { "id": 22, "type": "User" } } }
Your JSON structure looks valid - the issue is definitely the application/vnd.api+json content type. Clay expects application/json for webhooks. [1]
You'll need to configure Outreach to send the webhook with Content-Type: application/json instead. If Outreach doesn't allow changing the content type, you might need a middleware service (like Zapier or n8n) to receive the webhook and forward it to Clay with the correct content type.
The JSON payload itself is properly formatted, so once the content type is fixed, it should parse correctly in Clay. [2]
Is that what you were looking for?
yep
Great! Let me know if you have any other questions or need further assistance.
