Português · English

n8n and automations

Create a service key with the "Automation (n8n, Make, Zapier)" template.

n8n with the REST API

Use the HTTP Request node:

• Authentication: Generic Credential Type → Header Auth; Name: Authorization; Value: Bearer atl_live_….
• URL: https://atende.suporteja.com.br/v1/... (see the reference).
• To react to events, create a webhook in Atendlly pointing at n8n's Webhook node (see webhooks) and check the signature in a Code node.

Example: label the conversation when an order is paid.

curl -X POST "https://atende.suporteja.com.br/v1/conversations/1543/labels" -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" -d '{"add": ["paid"]}'

n8n with the MCP client

n8n's MCP Client node works too: endpoint https://atende.suporteja.com.br/mcp, HTTP Streamable transport, header Authorization: Bearer atl_live_…. n8n's AI agents see only the tools the key allows.

Sending messages

A service key sends messages to customers only after a person approves them, unless an administrator turned on automatic sending for it (Settings → Integrations → API keys and MCP). Even in automatic mode, messages with other people's data or external links wait for approval. Limits: see rate limits.