Connector operations and data access in chat

When you work on a connector with the AI assistant beside it, the assistant can install the connector, run a sync, read and edit its files, check its recipe and connection, and ask you for the secrets and data access it needs. Each step appears as a card under the reply, and this page explains what those cards say. For the panel itself, see The AI assistant; for the shared card shell, its statuses and the other card families, see The assistant's step cards.

Install and sync a connector

• Install connector follows the connector's installation. Its subtitle names the current step, for example Step 2 / 5, over a progress bar that shows the percentage; when the step is done, the subtitle reads Installed.
• Sync data source runs the connector end to end. The card stays open until the run finishes, so one that reads Running the pipeline - this can take a while is a run in progress; while it runs, it carries the note The landing database is rebuilt from scratch on every run. A finished run shows the message the run returned, or Pipeline completed; a failed run reads Pipeline failed with the error.

Check the connector's data

• Connector tables lists the tables the last sync landed, one per stream, with the row count for each. While it runs, the card reads Checking the landing database; a finished card gives the count, for example 12 tables in the landing database. With nothing to show it reads No tables - the tap produced no streams, and on a failure Could not list tables.
• The row counts are a sample, not the stream's full size: the card notes Row counts are a sample - each stream is capped during sync.
• Sample stream previews real rows from one stream. While it runs, its subtitle reads Sampling with the stream's name; a failure reads Sample failed. A finished card gives the stream, the row count and the time it took, and a table of the first 20 rows and 12 columns. Empty cells read NULL, and when the stream has more rows the card notes The sample hit the limit - the stream has more rows. The footer counts what is shown against the sample, as in Showing 20 of 148 rows, and adds the hidden columns, as in +3 more columns. Copy JSON copies the full sampled row set, not only the visible rows.

Read, write and validate the connector's files

• Get meltano.yml and Set meltano.yml show the connector's configuration file, read or updated, with the datasource and the line count in the subtitle. A long file starts collapsed behind Show all; Show less collapses it again, and Copy meltano.yml copies the file text and reads Copied. The file itself is covered in Configure a custom connector.
• Get recipe and Set recipe show the API recipe in the same kind of card, under the file label manifest.yaml. For the recipe itself, see Connect any API.
• Test meltano.yml runs a schema check on the configuration file. A pass reads Schema check passed · Valid config; a failure reads Validation failed · Invalid config with the error.
• Validate recipe checks the recipe and lists what it found, grouped by severity: fatal, error, warning and info. The subtitle counts only the fatal and error issues, for example 2 issues, and a clean recipe reads Recipe is valid. When the recipe calls hosts that are not approved yet, the card adds an Unapproved hosts: line naming them; each issue line gives its code, where it sits in the recipe and the message.
• Check connection runs the recipe's live check. It reads Connected with the time it took in milliseconds, or Connection failed with the error.
• Approved hosts reports a whitelist change. It reads how many hosts were approved, as in 2 host(s) approved, or Approval failed, and warns while any host still waits: 1 host(s) still pending approval. Host approval itself sits in Hosts, streams and data access; when a change waited for your decision first, see Approve or reject connector changes.

Troubleshoot a page or a load

• Bisect page isolates the part of a page that breaks a stream by splitting it in halves. While it searches, it reads Bisecting with the stream and the range; a skipped search reads Skipped. The verdict reads Offset n breaks the page when the break is found, Intermittent - neither half reproduced when the result is not stable, or Bisect failed. The steps table shows each tried half with ok or fails cells, and a broken record is labelled invalid UTF-8 or invalid JSON.
• Probe page reads one page the way the loader would see it. While it runs, it reads Probing with the stream; a failure reads Probe failed, and a finished card gives the stream, the parameters, the record count, the size and the time. When the recipe's record path is missing, it warns The record path is not present in this page - the loader would read 0 records from it. The card can list the sequences it replaced, name the First and Last record keys (a placeholder stands in for them when you may not read the data), and settle the page body: a clean body reads Body is valid UTF-8 and valid JSON, and a failure names the byte or the character where the scan stopped.
• Load diagnostics opens the connector's Sync Log. While it reads, it shows Reading the Sync Log…; a finished card lists the failed or warned runs it found, with the count, and the first run opens by itself. Each run shows its status, the rows it loaded, its window from start to finish and any error. When the card cannot read diagnostics, it reads No diagnostics with the error under the subtitle; a run without diagnostics reads No runner diagnostics were collected for this run.
• Sample and probe cards can carry an amber warning line for the reader's warnings, such as invalid UTF-8 sequences that were replaced; nothing appears when there are none.

See the requests to your API

• HTTP request is one request the assistant ran while it worked on your API. While it runs, the subtitle shows the method and the address, or Running request; a failure reads Request failed.
• A finished card carries a status pill for the response code: green for a 2xx code, red for a 4xx or 5xx code, and neutral otherwise. A code that is not a success is still not a failed step; the pill takes its colour from the code.
• Open Request body, Response body and Response headers to read the exchange. Request headers never appear on the card, and a request body that is JSON is shown formatted.
• A response body larger than 32 KB is cut: the card adds Response truncated - showing the first 32 KB and the body's full size.

Handle secrets

• List secrets lists the connector's stored secrets by name, with how many are stored and how many are bound, for example 4 stored · 3 binding(s). Values never appear; the card shows names only.
• Rename secret shows a rename as the old name and the new name around an arrow; an unknown side reads ?, and a failure replaces the subtitle with the error.
• A secrets request card asks you to store the values the connector needs. While it waits it reads Waiting for secret(s), with Open Secrets Vault opening the vault for the requested names. The vault also opens by itself once while the request waits; close it, and it stays closed until you open it again. The card settles as Secrets provided when every requested value is stored, Secrets not provided while at least one is still missing, or Could not request secrets when the request fails.
• Store the values in the vault, not in the chat: the chat does not take the value itself. The vault, its actions and its permissions are covered in Connector secrets.

Check and request data access

• Data access grants lists the connector's grants and their state, active, broken or revoked. Each grant shows its columns, with a token badge on personal-data columns, the hosts it is pinned to, and a summary such as its row count, date column and cap. For admins the card also carries a Sample values payload with up to three values per column, personal data as tokens; other users read the grant's details without the samples. With no grants yet, the card reads No data access grants yet. An admin adds one in the recipe editor.
• Data access request is a request the assistant raises when its work needs rows from a Lake or Warehouse object. It shows the purpose and any suggested object, columns, date column or row cap. While it waits, it reads Waiting for an admin…; it settles as Grant name created, No grant created, Request failed or Decided. An admin sees Open Data access on the request, which opens the prefilled Add data access form in the connector; other users do not.
• Preview data access shows the rows a grant sends, exactly as the stream receives them, with personal data as tokens. It reads Reading grant…, then the row count and per-column statistics under column, distinct, nulls, min and max; a missing figure reads -. A failure reads Preview failed. The preview is for the admin role.
• The grant's lifecycle, its limits and what it sends are covered in Data access grants.

Questions, answered

Why did the Secrets Vault open by itself?

A secrets request that is waiting opens the vault once, with the requested names ready to fill in. Close it and it stays closed; you can open it again with Open Secrets Vault on the card.

What does "Secrets not provided" mean?

At least one of the values the assistant asked for is still missing, so the step did not get everything it needed. Store the missing values in the vault; the card lists the names that were requested. The vault is covered in Connector secrets.

What does "The landing database is rebuilt from scratch on every run." mean?

It is the note a running sync card carries: the run rebuilds the connector's loaded data from scratch, and the card stays open until the run finishes.

Are the row counts on a "Connector tables" card exact?

No. They are a sample, not the stream's full size: each stream is capped during sync, and the card says so.

Does "Copy JSON" copy only the rows I can see?

No. The table shows the first 20 rows and 12 columns, and Copy JSON copies the full sampled row set, not only the visible rows.

What does "No diagnostics" mean on a "Load diagnostics" card?

The card could not read anything from the connector's Sync Log, so it shows no runs; the error under the subtitle says why. When the log reads, the card lists the runs it found instead.

What does "Unapproved hosts" mean on a validation card?

The recipe calls hosts that are not approved yet, and a connector can call only approved hosts. Approve them under Hosts; see Hosts, streams and data access.

Why does a probe say "The record path is not present in this page"?

The page does not contain the record path the recipe points at, so the loader would read 0 records from it. Check that path in the recipe, then probe again.

Where are the request headers of an "HTTP request" card?

They are not shown: the card leaves request headers out, so only the request and response bodies and the response headers appear.

What does "Intermittent - neither half reproduced" mean?

The page break did not reproduce when the page was split in halves, so it is not stable. The steps table shows what each half returned.