This page is an interface inventory: what's written here is the text that appears on screen, literally. To learn the task, go to Connect your first source.
Where it is: menu ETL/ELT → Connections.
A connection is access to a system (for example, your ERP's database), registered once and reused in as many pipelines as you like. It only reads data — and registering doesn't bring anything in: the pipeline does that.
Find a connection in the list (/conexoes)#
The list is called Your connections. Columns: Name · System · Status · Used in · Actions.
| You want to | Click |
|---|---|
| Register new access | New connection (opens, at the top, the question Which system does your data come from?) |
| See if the access still works | Test (becomes Testing… while it runs) |
| Open the full detail page | Open connection |
| Use this connection in a pipeline you're building | Use connection |
In the More actions for connection {nome} menu: Edit configuration, Replace credential, Use in a new pipeline, See linked pipelines, Archive connection, and Delete connection.
Archive appears disabled, and that's on purpose
Archive connection is in the menu with the reason stated on the screen itself: archiving isn't available yet. The product prefers to say so rather than hide the action and leave you searching for it.
Status — a single answer
| Status | What it means |
|---|---|
| Working | The last test got into the system with the current data |
| Has a problem | The last test failed, or the password was rejected/expired |
| Never tested | We haven't tested yet whether we can get in |
| Test again | The access data changed after the last test |
Connections created inside a pipeline appear with the This pipeline only badge: they have no separate test, and their status comes from the pipeline's last run.
Filters
A single bar: Search by name · All systems · the status (All, Working, Has a problem, Never tested, Test again — only the ones present in your list appear, with the count) · Clear filters.
When the list is empty
- No connections yet: Connect your first system + the New connection button
- Filter with no results: No connection matches these filters + Clear filters
- Failed to load: Couldn't load your connections + Try again
On a phone, the list appears as cards.
Register a connection — the four-step wizard (/conexoes/nova)#
Title New connection (when editing: Edit connection — {nome}). Four steps:
System → Address and password → Test → Done
| Step | Heading on screen | What you do |
|---|---|---|
| 1 | Where is your data? | Choose the system (Postgres, MySQL, SQL Server, Oracle, BigQuery). If you came from a catalog card, this step is already done |
| 2 | {Sistema} address and password | Connection name (comes suggested), Server address, Port (default pre-filled), Database name, User, and Password. Each field has a help line with an example |
| 3 | Let's test whether we can get in | Click Test now |
| 4 | All set to save? | Review and save |
Advanced options (in step 2, collapsed) holds what usually only IT touches: Schema, Connection security (SSL), How we reach the database (Direct over the internet, SSH tunnel (bastion), Cloud SQL (IP/Proxy), VPN (private IP)), and the SSH tunnel fields. It comes with the secure default.
The test result is one sentence: Connection working or We couldn't get in, with the reason and what to do (e.g., "The server didn't respond in time… ask your IT to allow access"). The per-stage detail is under See test details (for IT).
Footer: Back · Continue (on the test step: Continue without testing or Continue anyway) · Cancel. The final button is Save connection — or Save and use in pipeline when you got here from inside the building of a pipeline.
When editing a saved connection, the password isn't shown: step 2 shows Change the password (and Keep the stored password to back out).
Changing the access calls for a new test
If you change any data, test again: the previous result doesn't apply to the new access.
You can save without testing — the connection stays as Never tested.
Configure, test, and revoke a saved connection (/conexoes/salva/[id])#
Top actions: Use in a new pipeline (or Use in pipeline, when you came from the builder) · Test connection · the More actions for connection {nome} menu, which has Edit configuration, Replace credential, See linked pipelines, Archive connection, Delete connection, and Revoke credential.
Replace and revoke are not the same thing
Replace credential swaps the secret and keeps the connection running. Revoke credential deletes the secret: the connection stays registered and stops working until you provide another one. Every pipeline that points to it fails on its next run.
Three tabs: Summary · Linked pipelines ({N}) · History.
The Summary has the Access configuration, Capabilities, Credential, Credential and vault, Last test, Test from the pipelines executor, and Ingestion panels. In Last test, the line that matters most is Valid for the current revision? — it tells you whether the test that passed applies to the access stored right now.
Right after creating it, the screen responds: "Connection registered. No load was started."
View the detail page of an already-ingested source (/conexoes/[id])#
A read-only view of an already-ingested source: Connection details ("This source's configuration (read-only). Credentials are never shown."), Ingested tables, Status (the Status, Last run, and Category lines), the Ingestion mode line, and the Encrypted credentials badge. The actions are Back and the Edit {nome} icon.
The four states behind the status (for IT)#
In the list you see ONE status. The connection's detail page shows the four states it comes from:
| Dimension | Possible values |
|---|---|
| Registration | Active · Draft · Archived |
| Validation | Validated ✓ · Failed the test · Testing… · Validation outdated · Not tested |
| Credential | Credential configured · Credential expired · Credential revoked · Credential inaccessible · No credential |
| Ingestion | Last ingestion OK · Last ingestion failed · Ingestion running · Never ingested · No pipeline |
As the screen itself says: a Validated ✓ connection doesn't mean data was loaded, and an Active registration doesn't mean the test passed.
Back to the app#
- Connections: ETL/ELT → Connections
- Register one: New connection
Next task#
- Connect your first source — the tutorial
- Pipelines screens — use the connection in a load
- Credentials and rotation