None of my GPTs can call actions

GPT builders Plugins / Actions builders
1

I just signed up today for ChatGPT Pro to get going on creating my own GPTs
All went until I tried to to test my custom actions. none of them work. Open AI is simply not calling my server, even if I just use of the the examples and change the url to point to my server the endpoint is never called by the custom GPT .
I get:

[debug] Calling HTTP endpoint
[debug] Response received
{}

it says it is calling my server but never does and assumes the response in an empty document.

If I use the example from GetCurrentWeather is also never works I get:

[debug] Calling HTTP endpoint

There was an error generating a response

This is driving me crazy, is this happening to anyone else?

1 Like
2

This seems to be something that I encountered as well.

Can you share your OpenAPI schema?

Also, did you try to click the Test button that is visible when creating actions?

3

I used the Weather example from the dropdown and literally just changed the url with my Ngrok server and I can’t get it working

{
  "openapi": "3.1.0",
  "info": {
    "title": "Get weather data",
    "description": "Retrieves current weather data for a location.",
    "version": "v1.0.0"
  },
  "servers": [
    {
      "url": "https://xxx.eu.ngrok.io"
    }
  ],
  "paths": {
    "/location": {
      "get": {
        "description": "Get temperature for a specific location",
        "operationId": "GetCurrentWeather",
        "parameters": [
          {
            "name": "location",
            "in": "query",
            "description": "The city and state to retrieve the weather for",
            "required": true,
            "schema": {
              "type": "string"
            }
          }
        ],
        "deprecated": false
      }
    }
  },
  "components": {
    "schemas": {}
  }
}
4

Found the GPT actions work only once published, never works in editor

1 Like
5

That didn’t fix anything for me, but if that’s that case, it doesn’t make any sense to me.

Oh well, this whole thing feels a bit sketchy still, I think it needs to mature a little bit, I’ll come back in a few months

Thanks anyway

1 Like
6

Yup, same here :frowning_face: Burnt a day trying to get something to work, then thought "I’ll just try one of their examples - the weather. Tried @matcha72’s advice and like @paulotaylor, even after publishing it still threw errors. I’ll post a bit more after I’ve submitted the additional feedback - so need this to link to - BRB…

7

OK - here’s the test from the published version:

Weather Test GPT

Me

Invoke the weather.example.com action

Weather Test GPT

  • Error talking to

  • It seems there was an error trying to retrieve the weather for New York, NY. The service might be temporarily unavailable. Please try again later or ask for the weather in a different location.

Now - here’s the Configuration

Name: Weather Test GPT
Description: Invokes the Weather example action
Instructions: Just invoke the weather.example.com action
Conversation starters: Invoke the weather.example.com action
Actions: weather.example.com
Authentication: None
Schema (straight from Weather (JSON) Example)

{
  "openapi": "3.1.0",
  "info": {
    "title": "Get weather data",
    "description": "Retrieves current weather data for a location.",
    "version": "v1.0.0"
  },
  "servers": [
    {
      "url": "https://weather.example.com"
    }
  ],
  "paths": {
    "/location": {
      "get": {
        "description": "Get temperature for a specific location",
        "operationId": "GetCurrentWeather",
        "parameters": [
          {
            "name": "location",
            "in": "query",
            "description": "The city and state to retrieve the weather for",
            "required": true,
            "schema": {
              "type": "string"
            }
          }
        ],
        "deprecated": false
      }
    }
  },
  "components": {
    "schemas": {}
  }
}

This would be a pretty serious bug, or are we all missing something? Hoping OpenAI can help :pray:

Finally, here’s the Preview when I click Test

Me
Call the weather.example.com API with the GetCurrentWeather operation
Weather Test GPT

[debug] Calling HTTP endpoint

{
  "domain": "weather.example.com",
  "method": "get",
  "path": "/location",
  "operation": "GetCurrentWeather",
  "operation_hash": "5bdb6b5aaf8d3125da7b98633e18049c57c2febf",
  "is_consequential": false,
  "params": {
    "location": "San Francisco, CA"
  }
}

[debug] Response received

{}

Error talking to

It seems there was an error while attempting to retrieve the weather data for San Francisco, CA. If you have another location in mind or wish to try again later, please let me know.

Link to that GPT

Not sure if it works, but Weather Test

8

weather.example.com is a fake server and this needs to be replaced with a real server. It won’t work because there is no server at the “example.com” domain if this is in fact the server url that you are using. You would need to find a weather service API online and use that. I am unsure why Open AI included this as an example where the server URL is throwing many people off since its just a dummy URL if it is not changed. And something else to note is that the open api spec here may change after you find an online weather service api to use and import their api spec.

9

DOH! OK - I just tried the APIs.guru Search from the OpenAPI Actions Compendium and it WORKED! :tada:
Thanks @michael_1 :slightly_smiling_face:
Must be something wrong with the way I’m spec’ing the API I’m trying to use… Will report back when I figure that out.

10

So I had this same issue where the request works on Swagger but not on the custom GPT, even when published. Plus, a developer on my team said it works for him, sometimes. I tried waiting for months, but just now I managed to get it to work. I duplicated the custom gpt and experimented with using YAML instead of JSON (with ChatGPTs help) and it worked, but I also noticed that the duplicated one didn’t have authentication (I was using API key authentication). On the original GPT, I experimented without the API key and it worked, but then when I re-added the API key, it still worked! And switching back to JSON instead of YAML also worked. In other words, nothing changed, I just had to remove and then re-add authentication I guess.