Skip to content

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

Updated on 2026-10-04

NetSuite — connector

Reads sales orders (transactions), customers and items via SuiteQL queries on the NetSuite REST API and loads into the Bronze layer.

On this page (15)

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


What it is#

Reads sales orders (transactions), customers and items via SuiteQL queries on the NetSuite REST API and loads into the Bronze layer.

Supported ingestion modes:

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

What it's for#

Bring NetSuite 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 of the product (connectors are part of all plans; the limit is the number of sources allowed by the plan).
  • Access: requires an active workspace — with the subscription overdue, suspended or canceled, the run is blocked.
  • Shutdown: the ingestion run can be turned off temporarily (maintenance or incident). When this happens, the UI will report that the feature is unavailable at the moment.

Prerequisites#

  • A NetSuite account with access to the data you want to ingest.
  • In NetSuite, enable Token-Based Authentication, create an integration (Setup → Integration → Manage Integrations) to obtain Consumer Key/Secret and an Access Token (Setup → Users/Roles → Access Tokens) to obtain Token ID/Secret for a role with SuiteAnalytics Workbook and read access to Transactions, Customers and Items. Provide the account ID (e.g.: 1234567 or 1234567_SB1).

Credentials#

Authentication method: OAuth 1.0a signed per request (consumer and token keys).

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

  • Consumer Secret (consumerSecret)
  • Token ID (tokenId) — From the Access Token generated for the integration user/role.
  • Token Secret (tokenSecret)

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

Form fields#

CampoRótuloTipoObrigatórioObservação
accountIdID da contatextosimSetup → Company → Company Information → Account ID (sandbox: 1234567_SB1).
consumerKeyConsumer KeytextosimFrom the integration created in Manage Integrations.
consumerSecret 🔒Consumer Secretsenha/segredosimsecret (encrypted; external vault optional)
tokenId 🔒Token IDsenha/segredosimsecret (encrypted; external vault optional); From the Access Token generated for the integration user/role.
tokenSecret 🔒Token Secretsenha/segredosimsecret (encrypted; external vault optional)

Step by step#

  1. In the Dados → Conexões menu, use Nova conexão.
  2. Choose NetSuite 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 the review, Publicar (agenda desligada) creates version 1 without executing anything. Afterwards, 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)
accountId = <accountId>
consumerKey = <consumerKey>
consumerSecret = •••••• (cifrado — nunca exibido)
tokenId = •••••• (cifrado — nunca exibido)
tokenSecret = •••••• (cifrado — nunca exibido)

Expected result#

Testar conexão returns the list of discovered tables/resources. After the first load, rows appear in the Bronze layer of your workspace, 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: ~2 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Scope per workspace: each customer reads and writes only to their own datalake (<prefixo>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Secrets encrypted: 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 stays in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
  • Production does not mock: a path that would fall into mock triggers the 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 the necessary 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 this happens in consecutive runs, open a support ticket informing 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 the observabilidade por conector (error rate, p50/p95, freshness).
  • A schema change at the source is signaled by schema drift (new column = info; removed column/type changed = attention).

Related#


Last review: 2026-10-04. Sheet automatically generated from the product connectors catalog.

Related links