Using ChatGPT’s Conversation action event, I set the Response format to Strucutred Output.
In the OpenAI documentation, this requires me to either provide a JSON Schema in text or with pydantic, which I can do in Jupyter Notebook to test my schema.
For some reason, Zappier requests an URL for the JSON schema. I have uploaded my schema to an open github repo (using their example schema at first), but I can’t make it work, no matter how I try I recieve the following error when testing the step: “Failed to fetch JSON schema from the provided URL”
Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? This will help me take a closer look at the issue.
Please don't include personal information in the screenshot, or be sure blur out any personal information.
If i select ‘text’ as the response format it works, so I know it works without json. I dont understand why it cannot get the JSON schema?
Hi @VinnieH,
If you're experiencing an issue fetching the JSON schema from a URL in your Zapier integration. First, verify that the URL is correct and accessible, and check for CORS restrictions that might block Zapier from retrieving the file. Ensure the server returns the correct Content-Type (application/json) and properly format the JSON using a validator tool. Double-check Zapier's configuration to confirm it's expecting a JSON schema. Lastly, network issues could be causing the problem, so retrying after some time may help.
Feel free to reach out if you have any questions or need further assistance.
It looks like I’m having the same issue as berszi and VinnieH. Checked and server returns “application/json” (screenshot attached). Tried hosting at both github and netlify, but getting the same error message.
Hi friends,
This might be a possible bug with ChatGPT and needed attention with our Zapier support team to report it directly to OpenAI. Kindly contact our Zapier support team on this link. https://zapier.com/app/get-help and choose report a bug.
I tested via curl and validated the json was findable and readable.
Been tearing out my hair reading documentation with OpenAI, but Zapier is fairly silent on specs.
Going to submit a support ticket - leaning towards this being a bug
Let me know if y’all find anything out
Hi friends,
This might be a possible bug with ChatGPT and needed attention with our Zapier support team to report it directly to OpenAI. Kindly contact our Zapier support team on this link. https://zapier.com/app/get-help and choose report a bug.
@JammerS I opened a trouble ticket for this issue. Is anyone else successfully using the JSON Schema? Since it such a new feature in Zapier, I’d love to connect with other users and see how they are making it work.
Hi @chris-protos,
Review the official documentation for guidance on exploring Zapier's JSON Schema feature and troubleshooting issues. Sharing your specific use case with the community may help uncover targeted solutions and best practices.
Our Zapier support team will provide you with specific guidance. In the meantime, gathering insights from other users can be beneficial.
Hi folks,
This has been resolved, with the request for fetching the JSON schema from a URL no longer erroring. Using that action with a publicly accessible link should work as expected now
Hi folks,
This has been resolved, with the request for fetching the JSON schema from a URL no longer erroring. Using that action with a publicly accessible link should work as expected now
Really?
Please share an example of a valid publicly accessible link. Still broken for me when I use a raw public gist link and raw github link for a repo that has the JSON schema. When I saw “raw” I mean just like the links given in this thread from other users.
Were those links tested by the dev team? feels like something was missed here..
Hi @Terrell,
Thank you for reporting the issue with publicly accessible JSON schema links. To troubleshoot, first, ensure the links are truly public by testing them in an incognito window. Confirm the format is correct, especially for raw GitHub links, and validate the JSON schema's structure using an online tool. Try substituting a known working link to isolate the problem. Please share example links (without sensitive data) to help diagnose the problem more effectively.
If you have any more questions or need further assistance, feel free to ask. We're here to help.
Using ChatGPT’s Conversation action event, I set the Response format to Strucutred Output.
In the OpenAI documentation, this requires me to either provide a JSON Schema in text or with pydantic, which I can do in Jupyter Notebook to test my schema.
For some reason, Zappier requests an URL for the JSON schema. I have uploaded my schema to an open github repo (using their example schema at first), but I can’t make it work, no matter how I try I recieve the following error when testing the step: “Failed to fetch JSON schema from the provided URL” home security leads
The error you're encountering — “Failed to fetch JSON schema from the provided URL” — when using Zapier with ChatGPT's structured output usually stems from URL formatting, content type headers, or file accessibility. Let's go step by step:
Test this in your browser to confirm it's accessible and returns valid JSON.
Double Check These Things:
The file is public (which it is, since you’re using GitHub’s raw link).
Valid JSON Schema — The file must be a proper JSON Schema, not just any JSON.
Content served correctly — GitHub’s raw URL should work, but make sure no extra HTML, errors, or headers are interfering.
Zapier-specific requirement — Zapier might expect Content-Type: application/schema+json or application/json. GitHub's raw files usually serve text/plain, which could be the issue.
Workaround Options:
1. Use a JSON hosting service with correct content type headers, like:
If you'd like, paste your JSON Schema here and I’ll help validate it or recommend a hosting method that guarantees it works with Zapier.
I can confirm, it’s now working as expected.
Hi @VinnieH,
Thank you for confirming that the issue is now resolved. We're glad to hear that everything is working as expected. If you have any further questions or encounter any other problems, please don't hesitate to contact us. We're here to help!
But no matter what I do the GPT step says the same: Failed to create a conversation in ChatGPT (OpenAI) Failed to fetch JSON schema from the provided URL
But no matter what I do the GPT step says the same: Failed to create a conversation in ChatGPT (OpenAI) Failed to fetch JSON schema from the provided URL
To add on - I used Vercel so I can specify the header type as well from my repo:
Zapier’s “failed to fetch JSON schema” actually covers two different failure points:
What Zapier does behind‑the‑scenes
Typical error text
Step A – Download the file.Needs a public HTTPS URL, ≤5 MB, no auth.
“couldn’t download” / “403/404”
Step B – Hand the file to OpenAI’s structured_output validator.If the validator throws any exception, Zapier bubbles it up as “failed to fetch JSON schema” even though the fetch succeeded.
Exactly the message you’re seeing
So the schema is downloading fine; OpenAI is rejecting it. (OpenAI Community)
OpenAI’s structured‑output (and function‑calling) validator insists that the root of the schema be an object, not an array. If you give it a schema whose top level is "type": "array", the API throws:
Invalid schema … schema must be a JSON Schema of 'type: "object"', got 'type: "array"' (OpenAI Community)
Zapier doesn’t surface that detail, hence the confusing error.
Two clean fixes:
Option A – Wrap the array in an object (OpenAI‑compliant)
Option B – Keep the array but ditch Zapier’s schema field If you really want a bare array, skip the schema URL entirely and:
Use JSON Mode (response_format: { "type": "json_object" }) and validate the output yourself in a downstream Code step, or
Ask OpenAI for a string and JSON.parse() it later.
N.B. Hosting still matters
Gist raw links come back as text/plain; that’s fine for Step A, but if you ever do hit a real “can’t download” issue, use a GitHub‑repo raw URL (raw.githubusercontent.com) or jsDelivr CDN which both serve application/json.
Hi - I’m getting the dreaded error, and the file is reachable, and I’ve tested the schema in the playground.
Failed to create a conversation in ChatGPT (OpenAl) Failed to fetch JSON schema from the provided URL
—-
Any ideas? @JammerS ?
Using ChatGPT’s Conversation action event, I set the Response format to Strucutred Output.
In the OpenAI documentation, this requires me to either provide a JSON Schema in text or with pydantic, which I can do in Jupyter Notebook to test my schema.
For some reason, Zappier requests an URL for the JSON schema. I have uploaded my schema to an open github repo (using their example schema at first), but I can’t make it work, no matter how I try I recieve the following error when testing the step: “Failed to fetch JSON schema from the provided URL” home security leads
The error you're encountering — “Failed to fetch JSON schema from the provided URL” — when using Zapier with ChatGPT's structured output usually stems from URL formatting, content type headers, or file accessibility. Let's go step by step:
Test this in your browser to confirm it's accessible and returns valid JSON.
Double Check These Things:
The file is public (which it is, since you’re using GitHub’s raw link).
Valid JSON Schema — The file must be a proper JSON Schema, not just any JSON.
Content served correctly — GitHub’s raw URL should work, but make sure no extra HTML, errors, or headers are interfering.
Zapier-specific requirement — Zapier might expect Content-Type: application/schema+json or application/json. GitHub's raw files usually serve text/plain, which could be the issue.
Workaround Options:
1. Use a JSON hosting service with correct content type headers, like:
Here’s my raw URL (incognito extracted). I’m still having the same problem.
Hi @berszi and @VinnieH,
Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? This will help me take a closer look at the issue.
Please don't include personal information in the screenshot, or be sure blur out any personal information.