Read first:
../conectores.md(state map) andfichas.md(index of sheets).
What it is#
Reads message history (SMS/WhatsApp, with status, cost and errors) and voice call history from Twilio's REST API and loads into the Bronze layer.
Supported ingestion modes:
- Nós buscamos — Nós buscamos os dados na sua fonte.
What it's for#
Bring Twilio 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 of the plan).
- Access: requires an active workspace — with the subscription overdue, suspended or canceled, the execution is blocked.
- Shutdown: the ingestion run can be temporarily disabled (maintenance or incident). When that happens, the screen indicates the feature is unavailable at the moment.
Prerequisites#
- A Twilio account with access to the data you want to ingest.
- In the Twilio console (console.twilio.com), in Account Info, copy the Account SID (starts with AC) and the Auth Token. Paste both — the Auth Token is encrypted (AES-256-GCM) and never shown again. To avoid exposing the main token, prefer an API Key: use the key SID as the user and the Secret as the password.
Credentials#
Authentication method: Username and password (or key and secret) using Basic authentication.
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.
- Auth Token (
authToken) — Account Auth Token (or the Secret of an API Key).
Secrets are never re-displayed and go through redaction on every error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
accountSid | Account SID | text | yes | In Account Info in the Twilio console (34 characters, starts with AC). |
authToken 🔒 | Auth Token | password/secret | yes | secret (encrypted; external vault optional); Account Auth Token (or the Secret of an API Key). |
Step by step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose Twilio in the catalog.
- Fill in the form fields (see the table above).
- 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.
- Use Salvar conexão. Saving DOES NOT start any ingestion.
- 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.
- In the review, Publicar (agenda desligada) creates version 1 without running anything. Then, Ativar agenda and Executar agora are separate actions.
Example — connection test#
Sample configuration (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
accountSid = <accountSid>
authToken = •••••• (cifrado — nunca exibido)Expected result#
Testar conexão returns the list of discovered tables/resources. After the first load, the 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
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~0.3 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 is stored 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 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 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-Afterand retries; if it repeats, wait and reduce the schedule frequency. - Resource not found — check the resource identifier (account, object, report) and the permissions granted.
- 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 with the connector and resource information.
- Empty record path — the response arrived without records in the expected place. Check the selected resource and filters (period, account, status) before assuming there is no data.
Troubleshooting#
- Use Testar conexão to isolate credential/network issues before scheduling.
- Monitor runs in the observability by connector (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#
../conectores.md— connector catalog by state../ingestao-incremental-backfill.md— full, incremental by watermark, backfill and checkpoint../pipeline-medalhao.md— Bronze/Silver/Gold layers and quality../agendamento-retry-dlq.md— scheduling, retry/backoff and DLQ../custo-limites-seguranca.md— cost, limits and workspace security
Last review: 2026-10-04. Sheet automatically generated from the product's connector catalog.