Skip to content

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

Updated on 2026-10-04

Senior — connector

Planned connector: reading data from Senior's ERP and HR by the Senior X platform does not yet exist — today the data arrives via scheduled exports to the receiving area.

On this page (16)

Read before: ../conectores.md (state map) and fichas.md (index of cards).


⚠️ Warning — Roadmap (not available)#

This connector is not implemented: configuration and execution are rejected by the product (nothing pretends to succeed).

The Senior X platform requires a gateway and a certified partner credential; there is no public access for a generic connector.

The rest of this page describes the planned specification (fields and connection form), not an active feature.


What it is#

Planned connector: reading data from Senior's ERP and HR by the Senior X platform does not yet exist — today the data arrives via scheduled exports to the receiving area of your environment.

Supported ingestion modes:

  • Nós buscamos — Nós buscamos os dados na sua fonte.

Purpose#

Bring Senior 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 in the datalake on a scheduled basis, with isolation per workspace.

Do not use for production today: the connector is on the Roadmap. Meanwhile, for files, use the "Você deposita" mode (upload the files to the landing).

Plan and permissions#

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

Prerequisites#

  • A Senior account with access to the data you want to ingest.
  • When the connector exists, the connection will use Senior X platform APIs with an application credential issued by the gateway. Today the data arrives via scheduled exports to the receiving area of your environment.

Credentials#

Authentication method: Application credentials (client id/secret) exchanged for an access token.

This connector does not require its own secrets (upload mode / no credential in the platform).

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
tenantSeniorTenant na Senior X (informativo)textonãoSó para registro de interesse — a configuração é recusada enquanto o conector não existir.

Step by step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose Senior in the catalog.
  3. Fill in 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 running anything. Then, Ativar agenda and Executar agora are separate actions.

In the current state (Roadmap), steps 4–5 are rejected by the product.

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)
tenantSenior = <tenantSenior>

Expected result#

The product rejects the configuration with a clear message that the connector is on the Roadmap.

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: ~1 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.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being persisted. The external credential vault is optional and enabled per connection; without it, the encrypted value is stored in the database. Changing the value here DOES NOT revoke the credential at the origin.
  • Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
  • Production does not fake: 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 missing the 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 terminates when the API cursor does not advance (anti-loop guard). If it happens in consecutive runs, open a support ticket informing the connector and the resource.
  • Empty records path — 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 por conector (error rate, p50/p95, freshness).
  • A schema change at the source is flagged by schema drift (new column = info; removed column/type changed = attention).

Related#


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

Related links