Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

Eduzz — connector

Reads sales, products and subscriptions from the My Eduzz API and loads into the Bronze layer.

On this page (15)

Leia antes: ../conectores.md (state map) e fichas.md (index of fichas).


O que é#

Reads sales, products and subscriptions from the My Eduzz API and loads into the Bronze layer.

Supported ingestion modes:

  • Nós buscamos — We pull the data from your source.

Para que serve#

Bring Eduzz data into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and the natural language question wizard.

Quando usar / quando não usar#

Use quando you need to consolidate this source into the datalake on a scheduled basis, with isolation per workspace.

Remember that the first run with a real credential is followed by our team before the connector is fully released.

Plano e permissões#

  • Plano: core product (connectors are part of all plans; the limit is the number of sources in the plan).
  • Acesso: requires an active workspace — with the subscription overdue, suspended or canceled, the run is blocked.
  • Desligamento: the ingestion run can be turned off temporarily (maintenance or incident). When that happens, the UI shows the resource is unavailable at the moment.

Pré-requisitos#

  • An Eduzz account with access to the data you want to ingest.
  • In Eduzz, go to the developer console (console.eduzz.com) with the producer account and generate an API My Eduzz access token with read permission for sales, products and subscriptions. Paste it below; the token is encrypted (AES-256-GCM) and never shown again. If the token expires, generate another and update the connection.

Credenciais#

Authentication method: Access Token pasted by you. It is encrypted (AES-256-GCM) and never shown again, nor appears in logs or error messages.

Sensitive fields. They are encrypted (AES-256-GCM) and never remain in the connection config, pipeline definition, export or DAG. By default the encrypted value is stored in the database; moving this connection's credential to an external credential vault is an explicit choice made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Token de acesso (My Eduzz) (tokenApi) — Bearer Token generated in Eduzz's developer console for your producer account.

Secrets are never re-displayed and go through redaction on every error/log (raw token, URL-encoded and in JSON).

Campos do formulário#

CampoRótuloTipoObrigatórioObservação
tokenApi 🔒Token de acesso (My Eduzz)senha/segredosimsegredo (cifrado; cofre externo opcional); Token Bearer gerado no console de desenvolvedor da Eduzz para a sua conta de produtor.

Passo a passo#

  1. No menu Dados → Conexões, use Nova conexão.
  2. Escolha Eduzz no catálogo.
  3. Preencha os campos do formulário (veja a tabela acima).
  4. Use Testar conexão. The result is shown broken down into Conectividade, Autenticação and Listagem/leitura — each with OK, Failed, Not applicable or Not tested. A capability with no test of its own for this connector shows as Not applicable, and Not applicable never counts as success.
  5. Use Salvar conexão. Salvar NÃO inicia ingestão nenhuma.
  6. No cartão da connection, use Montar extração (ou vá em Orquestração → Pipelines e use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. Na revisão, Publicar (agenda desligada) cria a versão 1 sem executar nada. Depois, Ativar agenda e Executar agora são ações separadas.

Exemplo — teste de conexão#

Configuração de exemplo (todos os valores são fictícios; segredos aparecem mascarados):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
tokenApi = •••••• (cifrado — nunca exibido)

Resultado esperado#

O Testar conexão retorna a lista de tabelas/recursos descobertos. Após a primeira carga, as linhas aparecem na camada Bronze do seu workspace, prontas para o pipeline.

Limites e custos#

  • Paginação: hard ceiling per run (default 10.000 pages / 5.000.000 rows); anti-loop guard.
  • Carga SaaS: default batchSize 5.000, maxRows 200.000 per resource.
  • Volume estimado: ~0.3 GB/month (catalog estimate, not a measurement).
  • Custo: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Segurança#

  • Scope per workspace: each customer reads and writes only to their own datalake (<prefix>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being written. The external credential vault is optional and linked per connection; without it the encrypted value remains in the database. Changing the value here DOES NOT revoke the credential at the origin.
  • Redaction: every error/log goes through secret redaction (raw, URL-encoded and in JSON).
  • Production does not fake: a path that would fall into a mock triggers the production guard (explicit failure instead of simulating success).

Erros comuns#

  • Credencial recusada (401/403) — the provider rejected the credential: expired, revoked or lacking necessary permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Limite de requisições (429) — the provider asked to wait. The extraction respects Retry-After and retries; if repeated, wait and reduce the schedule frequency.
  • Recurso não encontrado — check the resource identifier (account, object, report) and the permissions granted.
  • Cursor de paginação travado — the extraction stops when the API cursor does not advance (anti-loop guard). If this happens on successive runs, open a support ticket informing the connector and the resource.
  • Caminho de registros vazio — the response arrived without records in the expected location. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network problems before scheduling.
  • Monitor runs in the observability per connector (error rate, p50/p95, freshness).
  • A schema change at the source is flagged by schema drift (new column = info; removed column/type change = attention).

Relacionados#


Última revisão: 2026-10-04. Ficha gerada automaticamente do catálogo de conectores do produto.

Related links