Skip to content

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

Updated on 2026-10-04

Magento 2 (Adobe Commerce) — connector

Reads orders, products and customers from the Magento 2 / Adobe Commerce REST API (paged searchCriteria) and loads into the Bronze layer.

On this page (15)

Read first: ../conectores.md (state map) and fichas.md (datasheet index).


What it is#

Reads orders, products and customers from the Magento 2 / Adobe Commerce REST API (paged searchCriteria) and loads into the Bronze layer.

Supported ingestion modes:

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

What it's for#

Bring Magento 2 (Adobe Commerce) data into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and the natural language question wizard.

When to use / when not to use#

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

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

Plan and permissions#

  • Plan: core product (connectors are part of all plans; the limit is the number of sources allowed by the plan).
  • Access: requires an active workspace — with subscription overdue, suspended or canceled, the run is blocked.
  • Disablement: the ingestion run can be temporarily disabled (maintenance or incident). When this happens, the UI indicates the feature is unavailable at the moment.

Prerequisites#

  • A Magento 2 (Adobe Commerce) account with access to the data you want to ingest.
  • In the Magento admin, go to System → Extensions → Integrations, create an integration with read access to Sales, Catalog and Customers, activate it and copy the Access Token. The token is encrypted (AES-256-GCM) and is never shown again.

Credentials#

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 are never kept 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 the external credential vault is an explicit choice made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Access token da integração (tokenIntegracao) — Static integration token (System → Integrations). Admin tokens expire — use the integration token.

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

Form fields#

CampoRótuloTipoObrigatórioObservação
urlLojaStore URLtextyesMagento address (HTTPS); the API is at /rest/V1.
tokenIntegracao 🔒Integration access tokenpassword/secretyessecret (encrypted; external vault optional); Static integration token (System → Integrations). Admin tokens expire — use the integration token.

Step-by-step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose Magento 2 (Adobe Commerce) in the catalog.
  3. Fill the form fields (see the table above).
  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. Saving DOES NOT start any ingestion.
  6. On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. In review, Publicar (agenda desligada) creates version 1 without running anything. After that, Ativar agenda and Executar agora are separate actions.

Example — connection test#

Example configuration (all values are fictitious; secrets appear masked):

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

Expected result#

The Testar conexão returns the list of discovered tables/resources. After the first load, rows appear in your workspace's Bronze layer, ready for the pipeline.

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~0.5 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (chargeable).

Security#

  • Scope by 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 enabled per connection; without it, the encrypted value remains in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: every error/log goes through secret redaction (raw, URL-encoded and in JSON).
  • No mocking in production: a path that would fall into a mock triggers production guard (explicit failure instead of simulating success).

Common errors#

  • Credential rejected (401/403) — the provider did not accept the credential: expired, revoked or lacking required permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Rate limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, report) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If it happens in consecutive runs, open a support ticket indicating the connector and the resource.
  • Empty records path — the response arrived without records at the expected path. 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 connector observability (error rate, p50/p95, freshness).
  • A schema change at the source is signaled by schema drift (new column = info; removed/changed type column = attention).

Related#


Last review: 2026-10-04. Datasheet automatically generated from the product connector catalog.

Related links