Get Connector

firebase_data_connect.get_connector
ActionDatabases & warehousesconnection required

Calls firebasedataconnect v1 GET /v1/projects/{projectsId}/locations/{locationsId}/services/{servicesId}/connectors/{connectorsId}.

Gets details of a single Connector.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Firebase SQL Connect
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
service
Service name or id.
stringYes———
connector
Connector name or id.
stringYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
annotations
object—
clientCache
object—
createTime
string—
displayName
string—
etag
string—
labels
object—
name
string—
reconciling
boolean—
source
object—
uid
string—
updateTime
string—
{
  "annotations": {},
  "clientCache": {},
  "createTime": "",
  "displayName": "",
  "etag": "",
  "labels": {},
  "name": "",
  "reconciling": false,
  "source": {},
  "uid": "",
  "updateTime": ""
}

See Get Connector run in a workflow.

In a technical demo we add the Firebase SQL Connect connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.