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 fin

Clay's webhook receiver has quirks with certain content types, and application/vnd.api+json is one of them. The parser expects standard application/json and doesn't handle JSON API spec formatting well.

Quick workaround: Set up a simple middleware layer using Zapier or n8n to receive the webhook from Outreach, then forward it to Clay with proper application/json headers. Takes 5 minutes to build and costs basically nothing.

If you're technical, you can also use a lightweight Node.js function on Vercel or Railway. Just strip the JSON API wrapper and forward the actual data payload to Clay's webhook URL.

Alternative approach: Instead of webhooks, consider pulling data from Outreach via their API directly in Clay using the HTTP API enrichment. You lose real-time updates but gain more control over the data format. Set up a scheduled run every 15-30 minutes depending on your volume.

I've seen teams also use Outreach's Salesforce sync as an intermediary - sync to SFDC first, then webhook from there to Clay. More steps but rock solid reliability.

The JSON API content type limitation isn't documented anywhere obvious, but it's a known issue. Clay's engineering team is aware but no timeline on native support. The middleware approach is your cleanest bet for now.

Great! Let me know if you have any other questions or need further assistance.

Your JSON structure looks valid - the issue is definitely the application/vnd.api+json content type. Clay expects application/json for webhooks. [clay.com 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. [clay.com

{ "data": { "attributes": { "createdAt": "2025-12-04T1019.000Z", "updatedAt": "2025-12-04T1019.000Z", "activeAt": "2025-12-04T1019.000Z", "stateChangedAt": "2025-12-04T1019.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-04T0220.226-08:00", "eventName": "sequenceState.created", "jobId": "a193b1b2-b33f-4cb8-ac33-68f13118a1c5", "actor": { "id": 22, "type": "User" } } }

Clay expects application/json content type for webhooks. [documentation 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.