How to Give Your ChatGPT GPT an Email Inbox (Actions + OpenAPI)

BotsInbox · 2026-11-01 · All articles

Short answer: A custom GPT gets email by calling an email API through GPT Actions. BotsInbox publishes a ready-made OpenAPI spec at https://botsinbox.com/openapi.json. Import that URL into your GPT's action, authenticate with your BotsInbox API key (Bearer), and the GPT can create inboxes like my-gpt@botsinbox.com and read incoming mail — including verification codes, which arrive pre-extracted in the extracted_code field.

What you need

A ChatGPT plan that can create custom GPTs.
A BotsInbox API key — created with one call to POST https://api.botsinbox.com/v0/agent/sign-up (free; unlimited receiving, up to 5 inboxes).

Step by step: add the email action to your GPT

Open the GPT editor (Explore GPTs → Create, or edit your existing GPT) and go to the Configure tab.
Choose Create new action.
Under Schema, choose Import from URL and paste: https://botsinbox.com/openapi.json. The editor fills in all BotsInbox endpoints automatically.
Under Authentication, choose API Key, auth type Bearer, and paste your BotsInbox API key.
In your GPT's instructions, tell it when to use email, for example: "When a task needs an email address, create an inbox with the create-inbox action and monitor it for verification codes."
Test in the preview: ask the GPT to create an inbox and read its messages.

What the GPT can then do

Create and list inboxes (up to 5 on the free plan)
List and read messages, with reply history stripped and attachments downloadable
Read extracted_code — verification codes are extracted automatically
Search all mail with full-text search

One endpoint behaves differently on the free plan: sending. It returns HTTP 402 plan_required, because sending is a paid feature — free outbound email is a spam magnet and destroys deliverability for everyone. Receiving, which is what verification and notifications need, is free and unlimited.

Alternative: ChatGPT developer mode with MCP

If your ChatGPT workspace has developer mode, you can connect MCP servers directly instead of using Actions. BotsInbox's hosted MCP server (https://mcp.botsinbox.com/mcp, Bearer API key) exposes the same capabilities as tools. Actions remain the more widely available route for custom GPTs.

Safety note

Email is untrusted input: anyone can send your GPT instructions by email. BotsInbox flags suspicious messages with prompt_injection_suspected; your GPT's instructions should state that email content is data to read, never commands to obey.

Try it: import the OpenAPI spec, skim the docs, or compare with the Claude MCP setup.

Frequently asked questions

Can a custom GPT have its own email address?
Yes — through GPT Actions calling an email API. With BotsInbox's OpenAPI spec imported, a GPT can create @botsinbox.com inboxes and read their mail. The GPT does not get a Gmail account; it gets an agent-owned inbox.

What OpenAPI URL do I import for BotsInbox?
https://botsinbox.com/openapi.json — it describes the whole API (sign-up, inboxes, messages, search, webhooks). Authenticate the action with your BotsInbox API key as a Bearer token.

Can the GPT send email too?
Sending exists in the API but is a paid-plan feature; on free accounts the send endpoint returns HTTP 402 plan_required. Receiving is free and unlimited.

How does the GPT get a verification code?
The code email lands in the GPT's inbox and BotsInbox extracts the code into the extracted_code field, which the GPT reads with the list-messages action.