Atenta + n8n

Your n8n workflows with Atenta's events and API.

n8n workflows (in the cloud or on your own server) that receive Atenta's events and write to it through the API or MCP.

Verifying the webhook signature

Cabecera:  X-Atenta-Firma: t=<unix>,v1=<hmac>
Cálculo:   v1 == HMAC-SHA256(secreto, t + "." + cuerpo_crudo)
Rechaza el envío si no coincide o si |ahora − t| > 300 s. X-Atenta-Entrega es el id único: úsalo para no procesar dos veces.

01 · What you can do

Three things you do with n8n and your Atenta.

Save every escalated conversation in your database

The escalacion event arrives with the chat; the Postgres or MySQL node stores it wherever you want.

An n8n agent that queries Atenta over MCP

The “MCP Client” node talks to https://mcp.atenta.mx with your token: orders, appointments, customers and reports as tools.

Sync your catalog from your ERP

A scheduled workflow reads your ERP and updates stock and prices in Atenta through the API.

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.

“Webhook” node in n8n
Copy its production URL.
Register the webhook in your app
Settings → Integrations → Webhooks → “New”: URL, events, test with the ping. Verify the signature with a Crypto or Code node and the whsec_ secret Atenta gives you.
“HTTP Request” or “MCP Client” node
With a token from Settings → Integrations → n8n: API at https://api.atenta.mx/v1 (OpenAPI at https://api.atenta.mx/v1/openapi.json) or MCP at https://mcp.atenta.mx, Bearer authentication.