Skip to content
Skills Library
Sales & customer service · Tool integration

r7-api

/r7-api

Use when connecting other systems or AI agents to R7 One (the CRM of R7 Treinamentos) through its public integration API. Covers sending leads into R7 One with the universal lead webhook (POST /webhooks/leads/{token}), receiving R7 One events on your own server through signed outbound webhooks (lead.created, deal.won, appointment.completed and more), verifying HMAC signatures, landing page tracking, and R7 Calls meeting webhooks. Trigger on R7 One webhook, r7one integration, api.r7one.app, lead webhook, or Zapier, n8n or Make sending data to R7 One. Not for the internal app API.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
11
Scripts
3
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 3 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/send_lead.py, scripts/verify_signature.js, scripts/verify_signature.py

What it does and when to use it

Use when connecting other systems or AI agents to R7 One (the CRM of R7 Treinamentos) through its public integration API. Covers sending leads into R7 One with the universal lead webhook (POST /webhooks/leads/{token}), receiving R7 One events on your own server through signed outbound webhooks (lead.created, deal.won, appointment.completed and more), verifying HMAC signatures, landing page tracking, and R7 Calls meeting webhooks. Trigger on R7 One webhook, r7one integration, api.r7one.app, lead webhook, or Zapier, n8n or Make sending data to R7 One. Not for the internal app API.

Original author description

Use when connecting other systems or AI agents to R7 One (the CRM of R7 Treinamentos) through its public integration API. Covers sending leads into R7 One with the universal lead webhook (POST /webhooks/leads/{token}), receiving R7 One events on your own server through signed outbound webhooks (lead.created, deal.won, appointment.completed and more), verifying HMAC signatures, landing page tracking, and R7 Calls meeting webhooks. Trigger on R7 One webhook, r7one integration, api.r7one.app, lead webhook, or Zapier, n8n or Make sending data to R7 One. Not for the internal app API.

How it works

  1. Escolha a integração
  2. O que você precisa ter
  3. Começo rápido
  4. Regras que valem sempre
  5. Como foi verificado
Original SKILL.md headings · 60 lines, 742 words
SKILL.md preview
---
name: r7-api
description: >-
  Use when connecting other systems or AI agents to R7 One (the CRM of R7 Treinamentos) through its public
  integration API. Covers sending leads into R7 One with the universal lead webhook (POST /webhooks/leads/{token}),
  receiving R7 One events on your own server through signed outbound webhooks (lead.created, deal.won,
  appointment.completed and more), verifying HMAC signatures, landing page tracking, and R7 Calls meeting
  webhooks. Trigger on R7 One webhook, r7one integration, api.r7one.app, lead webhook, or Zapier, n8n or Make
  sending data to R7 One. Not for the internal app API.
---

# R7 One: API pública de integração

O R7 One (CRM com IA da R7 Treinamentos, `https://api.r7one.app`) se conecta a outros sistemas por **webhooks**. Esta skill documenta essa API de integração: o que enviar, o que receber, campos obrigatórios, erros e segurança. Tudo foi conferido contra o código do R7 One.

## Escolha a integração

| Quero... | Direção | Leia |
|---|---|---|
| **Mandar leads** de um sistema, formulário, Zapier/n8n/Make ou agente para o R7 One | entra | `references/lead-webhook.md` |
| **Receber avisos** no meu servidor (lead novo, venda ganha, reunião realizada...) | sai | `references/outbound-webhooks.md` |
| Registrar **visitas e cadastros de uma landing page** do R7 One | entra | `references/tracking-webhook.md` |
| Plataforma de chamadas avisar que a **reunião terminou** (com transcrição) | entra | `references/calls-webhook.md` |
| Contrato formal (OpenAPI 3.1) | todos | `references/openapi.yaml` |
| Divergências com a página do app e pegadinhas | | `references/known-issues.md` |

## O que você precisa ter

- **Webhook de leads:** o **token da empresa**. No app R7 One: **Configurações › Integrações** (ou menu **Documentação da API**). Quem tem acesso: owner/admin da empresa.
- **Webhooks de saída:** uma URL pública HTTPS do seu servidor e a chave secreta (`secret_key`) do webhook, cadastrada em **Configurações › Webhooks de saída**.
- **Webhook de chamadas:** token emitido pelo time do R7 One.
- Não existe API key pública: as outras rotas do app (leads, funis, agenda, chat, relatórios) são a **API interna autenticada** do front-end, não documentada aqui e sujeita a mudar sem aviso.

## Começo rápido

```bash
# 1) Teste sem criar nada (valida o token e mostra como os campos serão lidos)
curl -X POST "https://api.r7one.app/webhooks/leads/$R7_WEBHOOK_TOKEN?test=1" \
  -H "Content-Type: application/json" -d '{"name":"Teste","phone":"+5585999990000"}'

# 2) Envio real (o mínimo é telefone OU e-mail). Idempotency-Key evita duplicar em retry
curl -X POST "https://api.r7one.app/webhooks/leads/$R7_WEBHOOK_TOKEN" \
  -H "Content-Type: application/json" -H "Idempotency-Key: pedido-123" \
  -d '{"name":"Maria Souza","phone":"+5585999990000","email":"maria@exemplo.com","utm_source":"google"}'
```

Scripts prontos em `scripts/`: `send_lead.py` (envia ou simula um lead), `verify_signature.py` e `verify_signature.js` (validam a assinatura dos webhooks de saída; `--selftest` roda com um vetor do código real).

## Regras que valem sempre

- **O token é segredo.** Nunca em repositório, front-end público, log, chat ou mensagem. Leia de variável de ambiente (`R7_WEBHOOK_TOKEN`, `R7_WEBHOOK_SECRET`).
- **É produção.** Um envio real cria lead e oportunidade de verdade e pode disparar alertas e automações. Use `?test=1` para testar e peça confirmação ao usuário antes de envios reais em massa.
- **Dados de leads são pessoais (LGPD).** Envie só o necessário e não repasse a terceiros.
- **Sempre use `Idempotency-Key`** em envios que podem ser repetidos (retry, filas). Em `5xx`/timeout repita com a **mesma** chave; não repita `400`/`404`/`409`/`423`.
- **Defina um `User-Agent`** nas chamadas: o Cloudflare bloqueia bibliotecas padrão (`403 error code: 1010`).
- **Verifique sempre a assinatura** dos webhooks de saída, sobre o **corpo bruto**, e deduplique por `X-Rastreia-Delivery` (a entrega é at-least-once).
- **Não invente campos.** Use só os documentados. Campos desconhecidos no webhook de leads viram `extra` (não dão erro).
- Domínio: lead = pessoa (deduplicada por telefone/e-mail); oportunidade (deal) = card no funil, no máximo uma ativa por lead; fuso de negócio `America/Fortaleza`.

## Como foi verificado

Gerada em 2026-11-12 contra o código do R7 One e **testada de ponta a ponta** numa instância local isolada (clone descartável do banco de teste, sem credenciais de produção):

- **119 verificações de caixa-preta** passaram: webhook de leads (aliases, limites de campo, idempotência, deduplicação, conflitos, CORS, 423), rastreio de landing, webhook de chamadas (2 MB, duplicado e **assinatura**), login/refresh/logout (incl. rate limit do login), CRUD de webhooks de saída, bloqueio SSRF, entrega assinada de **`lead.created`, `deal.created`, `deal.stage_changed`, `deal.won`, `deal.lost`, `negotiation.opened|updated|cancelled`, `appointment.scheduled` e `appointment.completed`** (assinatura conferida com os scripts desta skill), `Retry-After`, 5xx com **8 tentativas até falha definitiva** e 4xx como falha permanente.
- **Testes do próprio R7 One** para essas rotas e para `funnel.*` passaram (121 e 39 em duas rodadas).
- Smoke em todas as 723 operações da API (incluindo a interna): nenhuma travou; 2 devolveram `500` em casos de borda (já em Issues #859 e #860).
- **Limites de entrada (implementados, Epic #878):** corpo máx. 1 MiB (`413`), 300/min por IP, 600/min por token, 20 404/min por IP (`429` + `Retry-After`). Confirmado em produção pelo QA (IP real gravado, `413` e `429` ok; ver `known-issues.md`).

Em **produção** só verifiquei ao vivo as respostas de erro das rotas públicas (token inválido, GET, JSON inválido, bloqueio de User-Agent), sem envios reais. Se algo divergir, vale o servidor.
Files in this package (11)
  • SKILL.md 6 KB
  • references/calls-webhook.md 4 KB
  • references/known-issues.md 5 KB
  • references/lead-webhook.md 9 KB
  • references/openapi.json 52 KB
  • references/openapi.yaml 31 KB
  • references/outbound-webhooks.md 11 KB
  • references/tracking-webhook.md 3 KB
  • scripts/send_lead.py 2 KB
  • scripts/verify_signature.js 2 KB
  • scripts/verify_signature.py 3 KB

Versions

The database has no other skills named r7-api.

Database snapshot: 13.11.2026 · package version 28469d3302f0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100open-crm-integration
    Integrate this product with Euron Open CRM so sales agents see what customers do in it. Covers pushing the catalog and prices, sending product events (page views, trials, checkout), identity stitching for anonymous visitors, lead capture, receiving CRM webhooks, and answering…
  • 100pipeline-crm-webhooks
    Receive and verify Pipeline CRM (pipelinecrm.com) webhooks sent by automations' "Call an API" action. Use when setting up a Pipeline CRM webhook endpoint, enabling Request signing and getting the whsec_ secret, debugging webhook-id / webhook-timestamp / webhook-signature…
  • 100breakcold-webhooks
    Receive and verify Breakcold webhooks (the sales CRM at breakcold.com). Use when setting up a Breakcold outbound webhook handler, debugging X-Webhook-Signature verification, or handling record.created, record.updated, note.created, task.completed, relation.added, call.linked or file.uploaded events.
  • 100odoo-crm-lead
    Integrazione Odoo CRM Lead via API - form frontend, webhook, protocollo invio dati. Use when building forms that submit to Odoo CRM, creating lead capture integrations, or implementing Odoo webhook connections.
  • 90backend-webhooks
    Use this skill when the user says 'webhook', 'webhook receiver', 'webhook delivery', 'signature verification', 'HMAC', 'event delivery', 'outgoing webhook', 'incoming webhook', 'retry webhook', 'webhook endpoint'. This skill implements receiving, verifying, retrying, and…
  • 100webhook-handling-verification
    Use this skill when receiving, verifying HMAC signatures, and processing third-party webhooks with replay attack prevention.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.