Skip to content

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

Connectors — catalog by REAL state

On this page (11)

The table below states, connector by connector, which can be registered and used today and which the product refuses to configure.

Sheets per connector: conectores/fichas.md — one page per connector, with fields, credentials, limits and common errors.

Read first: README.md (vocabulary of states + template of the 9 fields). This page is the public state map of connectors — the detailed operational step-by-step lives in the internal operational runbook and is not duplicated here.


Two vocabularies, and why both exist#

Confusing the two produced the contradiction between the homepage and this page: the former showed Available and the latter said Preview for the same connector. They are different axes, and both remain valid.

AxisValuesWhat it answers
Public state (the site badge and the connections screen)Available · Limited access · PlannedCan I use this today?
Maturity (internal engineering vocabulary)GA-candidate · Preview · RoadmapHow much evidence is behind it?

Rules that apply on both surfaces, without exception:

  • "Available" = usable today, in the product's normal flow, with the credential from your source. The platform's availability commitment is the plan SLA (99.5% per month from Growth — see /legal/sla); the connector state says whether it accepts registration today.
  • "Limited access" always comes with the concrete condition written on the connector's page — "limited access" without condition would be an empty promise.
  • "Planned" is what does not exist yet. No surface offers a "use today" button for these.

Catalog state (the product truth)#

The public state of each connector is derived from the catalog, not retyped. disponivel → Available; estrutura → Limited access; roadmap → Planned. The "Configuration" column says whether the product refuses to register the source today — and that refusal is the only case where use depends on contacting support.

<!-- gen:conectores-tabela:inicio --> <!-- Bloco gerado por scripts/docs/gen-connectors.mjs a partir do catálogo — não edite à mão; rode `pnpm gen:conectores`. -->
ConnectoridCategoryPublic stateMaturityConfigurationAuth
Google Sheetsgoogle_sheetsSpreadsheets and collaborationAvailableGA-candidateacceptedservice account
CSVcsvFilesAvailableGA-candidateacceptedupload to the landing area
JSONjsonFilesAvailableGA-candidateacceptedupload to the landing area
ParquetparquetFilesAvailableGA-candidateacceptedupload to the landing area
PostgreSQLpostgresqlDatabasesAvailableGA-candidateaccepteduser/password (network: IP, SSH, Cloud SQL, VPN)
SQL ServersqlserverDatabasesAvailableGA-candidateaccepteduser/password
OracleoracleDatabasesAvailableGA-candidateaccepteduser/password
MySQLmysqlDatabasesAvailableGA-candidateaccepteduser/password
MariaDBmariadbDatabasesLimited accessPreviewaccepteduser/password
Amazon Redshiftamazon_redshiftDatabasesLimited accessPreviewaccepteduser/password
CockroachDBcockroachdbDatabasesLimited accessPreviewaccepteduser/password
SupabasesupabaseDatabasesLimited accessPreviewaccepteduser/password
NeonneonDatabasesLimited accessPreviewaccepteduser/password
TimescaleDBtimescaledbDatabasesLimited accessPreviewaccepteduser/password
AlloyDBalloydbDatabasesLimited accessPreviewaccepteduser/password
Azure SQLazure_sqlDatabasesLimited accessPreviewaccepteduser/password
bigquerybigqueryDatabasesAvailableGA-candidateacceptedservice account
ClickHouseclickhouseData warehousesLimited accessPreviewacceptedusername and password (Basic)
Databricks SQLdatabricks_sqlData warehousesLimited accessPreviewacceptedaccess token
ElasticsearchelasticsearchData warehousesLimited accessPreviewacceptedusername and password (Basic)
Cloud FirestorefirestoreData warehousesLimited accessPreviewacceptedservice account
SnowflakesnowflakeData warehousesLimited accessPreviewacceptedkey pair (private key)
TrinotrinoData warehousesLimited accessPreviewacceptedusername and password (Basic)
Omie ERPomieERP and managementLimited accessPreviewacceptedApp Key / App Secret
Bling ERPblingERP and managementLimited accessPreviewacceptedOAuth 2.0 (refresh token)
Conta Azulconta_azulERP and managementLimited accessPreviewacceptedOAuth 2.0 (refresh token)
Tiny ERPtinyERP and managementLimited accessPreviewacceptedaccess token
NF-e (SEFAZ)nfeERP and managementLimited accessPreviewacceptedA1 certificate (.pfx)
Dynamics 365dynamics_365ERP and managementLimited accessPreviewacceptedclient id/secret (OAuth 2.0)
NetSuitenetsuiteERP and managementLimited accessPreviewacceptedOAuth 1.0a
NiboniboERP and managementLimited accessPreviewacceptedAPI key
OdooodooERP and managementLimited accessPreviewacceptedsession login
QuickBooks OnlinequickbooksERP and managementLimited accessPreviewacceptedOAuth 2.0 (refresh token)
SankhyasankhyaERP and managementLimited accessPreviewacceptedsession login
SAP Business Onesap_business_oneERP and managementLimited accessPreviewacceptedsession login
SAP S/4HANAsap_s4hanaERP and managementLimited accessPreviewacceptedusername and password (Basic)
SeniorseniorERP and managementPlannedRoadmaprefusedclient id/secret (OAuth 2.0)
TOTVS Protheustotvs_protheusERP and managementPlannedRoadmaprefusedAPI key
iFoodifoodE-commerce and marketplacesLimited accessPreviewacceptedclient id/secret (OAuth 2.0)
Loja Integradaloja_integradaE-commerce and marketplacesLimited accessPreviewacceptedAPI key
Magento 2 (Adobe Commerce)magento2E-commerce and marketplacesLimited accessPreviewacceptedaccess token
Mercado Livremercado_livreE-commerce and marketplacesLimited accessPreviewacceptedOAuth 2.0 (refresh token)
NuvemshopnuvemshopE-commerce and marketplacesLimited accessPreviewacceptedaccess token
ShopifyshopifyE-commerce and marketplacesLimited accessPreviewacceptedaccess token
Tray CommercetrayE-commerce and marketplacesLimited accessPreviewacceptedaccess token
VTEXvtexE-commerce and marketplacesLimited accessPreviewacceptedAPI key
WooCommercewoocommerceE-commerce and marketplacesLimited accessPreviewacceptedusername and password (Basic)
AsaasasaasPayments and financeLimited accessPreviewacceptedAPI key
GranatumgranatumPayments and financeLimited accessPreviewacceptedAPI key
Mercado Pagomercado_pagoPayments and financeLimited accessPreviewacceptedaccess token
Pagar.mepagarmePayments and financeLimited accessPreviewacceptedusername and password (Basic)
PagBankpagbankPayments and financePlannedRoadmaprefusedaccess token
StripestripePayments and financeLimited accessPreviewacceptedaccess token
VindivindiPayments and financeLimited accessPreviewacceptedusername and password (Basic)
SalesforcesalesforceCRM and supportLimited accessPreviewacceptedOAuth 2.0 (refresh token)
HubSpothubspotCRM and supportLimited accessPreviewacceptedOAuth 2.0 (refresh token)
AgendoragendorCRM and supportLimited accessPreviewacceptedAPI key
FreshdeskfreshdeskCRM and supportLimited accessPreviewacceptedusername and password (Basic)
IntercomintercomCRM and supportLimited accessPreviewacceptedaccess token
Moskit CRMmoskitCRM and supportLimited accessPreviewacceptedAPI key
MovideskmovideskCRM and supportLimited accessPreviewacceptedAPI key
PipedrivepipedriveCRM and supportLimited accessPreviewacceptedAPI key
PloomesploomesCRM and supportLimited accessPreviewacceptedAPI key
RD Station CRMrd_station_crmCRM and supportLimited accessPreviewacceptedAPI key
RD Station Marketingrd_station_marketingCRM and supportLimited accessPreviewacceptedOAuth 2.0 (refresh token)
ZendeskzendeskCRM and supportLimited accessPreviewacceptedusername and password (Basic)
Zoho CRMzoho_crmCRM and supportLimited accessPreviewacceptedOAuth 2.0 (refresh token)
Meta Ads (Facebook and Instagram)meta_adsMarketing and analyticsAvailableGA-candidateacceptedaccess token
Google Adsgoogle_adsMarketing and analyticsAvailableGA-candidateacceptedOAuth 2.0 (refresh token)
ActiveCampaignactivecampaignMarketing and analyticsLimited accessPreviewacceptedAPI key
BrevobrevoMarketing and analyticsLimited accessPreviewacceptedAPI key
EduzzeduzzMarketing and analyticsLimited accessPreviewacceptedaccess token
Google Analytics 4google_analytics_4Marketing and analyticsLimited accessPreviewacceptedservice account
Google Search Consolegoogle_search_consoleMarketing and analyticsLimited accessPreviewacceptedservice account
HotmarthotmartMarketing and analyticsLimited accessPreviewacceptedclient id/secret (OAuth 2.0)
KiwifykiwifyMarketing and analyticsLimited accessPreviewacceptedclient id/secret (OAuth 2.0)
KlaviyoklaviyoMarketing and analyticsLimited accessPreviewacceptedAPI key
LinkedIn Adslinkedin_adsMarketing and analyticsLimited accessPreviewacceptedaccess token
MailchimpmailchimpMarketing and analyticsLimited accessPreviewacceptedusername and password (Basic)
Pinterest Adspinterest_adsMarketing and analyticsLimited accessPreviewacceptedOAuth 2.0 (refresh token)
TikTok Adstiktok_adsMarketing and analyticsLimited accessPreviewacceptedAPI key
TypeformtypeformMarketing and analyticsLimited accessPreviewacceptedaccess token
AirtableairtableProductivity and HRLimited accessPreviewacceptedaccess token
AsanaasanaProductivity and HRLimited accessPreviewacceptedaccess token
ClickUpclickupProductivity and HRLimited accessPreviewacceptedAPI key
GupygupyProductivity and HRLimited accessPreviewacceptedaccess token
JirajiraProductivity and HRLimited accessPreviewacceptedusername and password (Basic)
monday.commondayProductivity and HRLimited accessPreviewacceptedAPI key
NotionnotionProductivity and HRLimited accessPreviewacceptedaccess token
SlackslackProductivity and HRLimited accessPreviewacceptedaccess token
TrellotrelloProductivity and HRLimited accessPreviewacceptedAPI key
TwiliotwilioProductivity and HRLimited accessPreviewacceptedusername and password (Basic)
Banco Central (SGS)bcb_sgsPublic dataLimited accessPreviewacceptedno credential (public data)
BrasilAPIbrasilapiPublic dataLimited accessPreviewacceptedno credential (public data)
IBGE (SIDRA)ibgePublic dataLimited accessPreviewacceptedno credential (public data)
Backblaze B2backblaze_b2Object storageLimited accessPreviewacceptedAPI key
Cloudflare R2cloudflare_r2Object storageLimited accessPreviewacceptedAPI key
DigitalOcean Spacesdigitalocean_spacesObject storageLimited accessPreviewacceptedAPI key
MinIOminioObject storageLimited accessPreviewacceptedAPI key
WasabiwasabiObject storageLimited accessPreviewacceptedAPI key
Amazon S3s3Object storageLimited accessPreviewacceptedaccess key / service account
gcsgcsObject storageLimited accessPreviewacceptedaccess key / service account
Azure Blob Storageazure_blobObject storageLimited accessPreviewacceptedSAS token or OAuth (Microsoft Entra ID)
DropboxdropboxRemote filesLimited accessPreviewacceptedOAuth 2.0 (refresh token)
Google Drivegoogle_driveRemote filesLimited accessPreviewacceptedservice account
HTTP Filehttp_fileRemote filesLimited accessPreviewacceptedaccess token
OneDrive / SharePointonedrive_sharepointRemote filesLimited accessPreviewacceptedclient id/secret (OAuth 2.0)
SFTPsftpRemote filesLimited accessPreviewacceptedusername and password (Basic)
Generic ODataodata_genericaGeneric APIsLimited accessPreviewacceptedusername and password (Basic)
Generic REST APIrest_api_genericaGeneric APIsLimited accessPreviewacceptedaccess token

Conditions of use — connectors whose configuration the product refuses today (the text is the same as the public connector page):

  • Senior (senior) — It is not yet possible to connect Senior by yourself: API access depends on a credential from an approved partner. Today the data enters via scheduled exports to the landing area of your environment.
  • TOTVS Protheus (totvs_protheus) — It is not yet possible to connect TOTVS Protheus by yourself: the REST API varies by version and environment customization. Today the data enters via scheduled exports (CSV/JSON) to the landing area of your environment.
  • PagBank (pagbank) — It is not yet possible to connect PagBank by yourself: the API queries one charge at a time, by its number, and does not return the account's list of charges. Today the path is to export the statement and upload it to the landing area of your environment.

Today the catalog has 110 connectors: 11 Available, 96 Limited access and 3 Planned.

<!-- gen:conectores-tabela:fim -->

Connectors that do not appear in "Conditions of use" do not depend on any case-by-case approval: they depend on the credential from your source and on the cloud environment of your workspace being configured (without it the run fails, with a message, rather than pretending success).

The R/Python script runner remains unavailable due to unverified isolation. It is not a connector: it is isolated script execution.


Sheet per family (template of the 9 fields)#

BR ERP/Fiscal connectors — Omie, Bling, Conta Azul, Tiny, NF-e

  1. State — Limited access for all five. All five accept registration today: since Onda 15 the automatic renewal of access (rotation of Bling and Conta Azul refresh tokens) is persisted by the platform, and the refusal to configure no longer exists. None of them is announced as generally available.
  2. What it does — extracts business tables (orders, products, finance, NF-e) from the ERP API and loads into the Bronze layer of the workspace.
  3. How it works — each connector is just an adapter over the common connectors SDK: normalized auth, pagination with hard cap, resume checkpoint, retry with Retry-After, redaction and metrics come for free. The same contract suite runs against all five.
  4. Plan · Permission — product core · access verification (active workspace) · execução de ingestão by capacity. Real extraction requires the source's encrypted credential.
  5. Cost — extraction itself is an ERP API call (R$0 on the platform); the Bronze load consumes datalake load processing (billable) — see custo-limites-seguranca.md.
  6. Limits — pagination with hard cap (default 10,000 pages / 5,000,000 rows); SaaS load default batchSize 5,000, maxRows 200,000.
  7. Security — secret (App Secret, refresh token, certificate password) enters secret redaction; no error leaks a token. Scope by workspace at load.
  8. How to validate — in the console, under ETL/ELT → Connections, use "Testar conexão" with the source credential and confirm that discovery lists the expected tables; after a load, check the Bronze layer of your workspace for the ingested rows. The catalog shows the state ("Preview until certification with real credential").
  9. In short — "<Connector> in Limited access — the condition of use is written on the connector's page."

Ads connectors — Meta Ads and Google Ads

  1. State — Limited access; both accept registration. Meta Ads depends on Meta App Review (ads_read) for broad use; Google Ads depends on the developer token basic→standard.
  2. What it does — Meta Ads reads the Insights endpoint (one row per day, time_increment=1) into 3 Bronze tables (meta_ads_campanhas/_conjuntos/_anuncios). Google Ads reads performance reports (campaign/group/keyword).
  3. How it works — adapters on the common SDK, with transport retry (429/5xx + Retry-After) and checkpoint. Google Ads refuses ingestion in production while the developer token is not approved (it never pretends success).
  4. Plan · Permission — core · access verification · execução de ingestão.
  5. Cost — calls to Ads APIs (R$0 platform) + Bronze load billable.
  6. Limits — configurable date windows (7/14/30/90 days, current/previous month); same SDK pagination caps.
  7. Security — access token / client secret / developer token / refresh token redacted in every error.
  8. How to validate — in the console, connect the ad account and run "Testar conexão"; confirm that the Insights/report tables appear in discovery and, after a load, in your workspace Bronze. While the app is not approved, production ingestion is refused with a clear warning.
  9. In short — Limited access, the same label used by the landing and the product: there is no "coming soon" badge anywhere. Moving up a state depends on App Review (Meta) and an approved developer token (Google).

Google Sheets

  1. State — Available: can be registered and used today, without case-by-case approval.
  2. What it does — reads sheets of a spreadsheet (actual columns, configurable header) and loads into Bronze.
  3. How it works — adapter with pagination by window of rows and checkpoint ({row, columns}); "Test connection" indicates the service account email to authorize.
  4. Plan · Permission — core · access verification · execução de ingestão.
  5. Cost — spreadsheet read R$0; Bronze load billable.
  6. Limits — SDK caps; a renamed sheet does not bring down the others (error is in the table, the loop continues).
  7. Security — service account JSON (and its private_key) redacted; scope by workspace.
  8. How to validate — in the console, authorize the service account email on the spreadsheet, run "Testar conexão" and confirm that sheets/columns appear; after the load, see the rows in Bronze.
  9. In short — "Google Sheets Available — registration and extraction in the normal flow."

Salesforce · HubSpot · Azure Blob

  1. State — Limited access. All three accept registration since Onda 15: HubSpot automatic access renewal is persisted by the platform and reading the Azure Blob container began being called by the same flow as other source connectors.
  2. What it does — Salesforce/HubSpot read CRM objects/entities; Azure Blob reads files from a container.
  3. How it works — adapters on the common SDK (Azure Blob has resume by blob name: blob ≤ last processed is skipped, not reprocessed).
  4. Plan · Permission — core · access verification · execução de ingestão.
  5. Cost — API/read R$0; Bronze load billable.
  6. Limits — SDK caps.
  7. Security — credentials redacted; scope by workspace.
  8. How to validate — in the console, connect the source, run "Testar conexão" and confirm discovery of entities/files; after the load, see the rows in your workspace Bronze.
  9. In short — "<Connector> in Limited access — the condition of use is written on the connector's page."

Declarative connectors from Onda 15 — ERPs, e-commerce, payments, CRM, marketing, productivity, public data, warehouses, remote files, generic APIs and compatible databases

  1. State — Limited access for all new connectors; Planned for TOTVS Protheus, Senior and PagBank (configuration refused with the reason). The list with each one's state is the generated table above — no counts are retyped here.
  2. What it does — each connector reads the resources listed in its sheet (orders, customers, charges, deals, campaigns, tasks, public series, warehouse tables, files from a folder or bucket…) and loads into the Bronze layer, one table per resource.
  3. How it works — the connector is a declarative specification (auth, pagination, resources and columns) executed by ONE engine per family: REST, HTTP SQL (ClickHouse, Trino, Databricks, Snowflake) and remote files (S3 and compatibles, gcs, SFTP, Drive, Dropbox, OneDrive/SharePoint, HTTP). Compatible databases (MariaDB, Redshift, CockroachDB, Supabase, Neon, TimescaleDB, AlloyDB, Azure SQL) run via the base engine driver. The same contract suite used for hand-written connectors runs against each one, with a simulator derived from the specification itself.
  4. Plan · Permission — core · access verification · execução de ingestão.
  5. Cost — calls to API/read of the source R$0 on the platform; Bronze load billable.
  6. Limits — SDK caps (pages/rows); complete extraction on each run (no incremental windowing by the scheduler); execution time limited to the function. The provider's thread format came from public documentation, without real credential — the condition is in the ownerBlocker of each connector.
  7. Security — every sensitive field is encrypted (AES-256-GCM) and enters secret redaction; renewed tokens enter the live list; no error leaks credential.
  8. How to validate — in the console, choose the connector, fill your account credential, run "Testar conexão" (a small call to the cheapest resource) and confirm discovery of resources; after the load, check the rows in Bronze. Format divergence is expected on first contact with the real API: it becomes a spec correction before the 30-day gate.
  9. In short — "<Connector> in Limited access — the condition of use is written on the connector's page." For Planned: "Not yet possible to use today — the condition is on the page."

The common SDK (why "new connector = adapter + contract suite")#

The common connectors SDK is pure (no I/O of its own; network transport is injected). A new connector only writes test/discover/extract; the rest comes from the adapter factory:

PieceGuarantee
Authnormalized credential; the SDK knows how to extract sensitive material for redaction
Paginationgenerator with hard cap and anti-loop guard (cursor that does not advance terminates)
Checkpointinjectable contract; reads before extracting, writes each batch, cleans on completion (next run starts from zero)
Retryexponential backoff + deterministic jitter, respects Retry-After; retries only 429/5xx and network errors
Redactionevery error/log passes through secret redaction (raw, URL-encoded, JSON)
Metricsone telemetry line per operation (rows/bytes/ms/ok) — telemetry never breaks the extraction

Contract suite: the same battery proves, for each adapter, that thrown errors are always redacted, metrics are always emitted and checkpoint resumes without duplicating or losing rows.

Schema drift and observability#

  • Schema drift: compares saved baseline × discovered schema. New column/table → info; removed column / type changed / removed table → attention (breaks the mart). It's pure logic; where the baseline is persisted is the caller's decision.
  • Observability: aggregates events into runs, error rate, p50/p95, freshness. Thresholds: error ≥ 20% → degraded; p95 > 30 s → degraded; not run > 26 h → degraded, > 72 h → stopped.

Connector certification (never automatic)#

Certification runs live probes (transport injected, without network) against the real adapter: honest status in the catalog · conformant adapter · discover with ≥1 table · active redaction (plants a sentinel-secret and requires it not to leak) · checkpoint supported. The human items (30 days with real credential, reconciliation against provider reports, token rotation, quotas with real traffic) are done by our team, connector by connector — so the automatic probe never promotes a connector on its own.

Related links