GPT Actions library

While GPT Actions should be significantly less work for an API developer to set up than an entire application using those APIs from scratch, there’s still some set up required to get GPT Actions up and running. A Library of GPT Actions is meant to provide guidance for building GPT Actions on common applications.source

If you’ve never built an action before, start by reading the getting started guide first to understand better how actions work.source

Generally, this guide is meant for people with familiarity and comfort with calling API calls. For debugging help, try to explain your issues to ChatGPT - and include screenshots.source

The OpenAI Cookbook has a directory of 3rd party applications and middleware application.source

GPT Actions can integrate with HTTP services directly. GPT Actions leveraging SaaS API directly will authenticate and request resources directly from SaaS providers, such as Google Drive or Snowflake.source

GPT Actions can benefit from having a middleware. It allows pre-processing, data formatting, data filtering or even connection to endpoints not exposed through HTTP (e.g: databases). Multiple middleware cookbooks are available describing an example implementation path, such as Azure, GCP and AWS.source

Are there integrations that you’d like us to prioritize? Are there errors in our integrations? File a PR or issue on the cookbook page's github, and we’ll take a look.source

If you’re interested in contributing to our library, please follow the below guidelines, then submit a PR in github for us to review. In general, follow the template similar to this example GPT Action.source

Guidelines - include the following sections:source

• Application Information - describe the 3rd party application, and include a link to app website and API docs
• Custom GPT Instructions - include the exact instructions to be included in a Custom GPT
• OpenAPI Schema - include the exact OpenAPI schema to be included in the GPT Action
• Authentication Instructions - for OAuth, include the exact set of items (authorization URL, token URL, scope, etc.); also include instructions on how to write the callback URL in the application (as well as any other steps)
• FAQ and Troubleshooting - what are common pitfalls that users may encounter? Write them here and workarounds

This action library is meant to be a guide for interacting with 3rd parties that OpenAI have no control over. These 3rd parties may change their API settings or configurations, and OpenAI cannot guarantee these Actions will work in perpetuity. Please see them as a starting point.source

This guide is meant for developers and people with comfort writing API calls. Non-technical users will likely find these steps challenging.source