Atenta + ChatGPT

Your business as a ChatGPT connector.

A custom GPT with Actions on top of your Atenta's OpenAPI, with a token of your own.

Details for the Actions

Esquema OpenAPI 3.1:  https://api.atenta.mx/v1/openapi.json
Autenticación:        API Key · Bearer · atk_TU_TOKEN
Documentación:        https://api.atenta.mx/v1/docs

01 · What you can do

Three things you do with ChatGPT and your Atenta.

“How many appointments do I have tomorrow, and with whom?”

The citas_listar action checks your schedule and ChatGPT lists them with time and person.

“Write me the monthly summary for my accountant”

With reports permission, it pulls sales by day, payments by method and satisfaction, and writes it up the way you need.

“Note that Laura prefers delivery at 2”

With customers permission, it adds the note to her profile. Atenta uses it the next time Laura writes.

02 · How it connects

From your app, with a permission you grant.

Nothing connects unless you turn it on. Every token and every webhook is listed in Settings → Integrations, with its last use, and is revoked with one tap.

Generate your token in the app
Settings → Integrations → ChatGPT → “Connect”. Suggested permissions: read conversations, orders, appointments, customers, reports and base. It's shown only once.
Create a GPT with Actions
In ChatGPT → Explore GPTs → Create → “Actions” → import from URL https://api.atenta.mx/v1/openapi.json. Authentication “API Key”, type “Bearer”, value: your token. The schema already brings one action per operation (chats_listar, pedidos_crear, citas_disponibles…).
Give it instructions and ask
Suggested instruction for the GPT: “Use Atenta's actions to answer with the business's real data; never make up prices or hours; if an action fails, state the reason it returns”. Whatever it does is logged in your activity log; you revoke the token whenever you want.

ChatGPT is a trademark of OpenAI. ChatGPT's MCP connectors authenticate with OAuth or with no authentication; Atenta authenticates with a token, which is why the route is Actions. Any MCP client that accepts an Authorization header can use the MCP server directly.

More connections