Firebase

Manage Firestore documents, authentication, and cloud messaging.

Detail	Value
Category	Cloud & Infra
Base URL	https://firebase.googleapis.com/v1beta1
Authentication	Bearer Token
Endpoints	5
Connector key	firebase

Using Firebase in a workflow

1. Go to Connections and click New Connection.
2. Pick Firebase from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /projects/{projectId}/databases/(default)/documents/{collectionId}	List documents in a collection
POST /projects/{projectId}/databases/(default)/documents/{collectionId}	Create a document
GET /projects/{projectId}/databases/(default)/documents/{documentPath}	Get a document
PATCH /projects/{projectId}/databases/(default)/documents/{documentPath}	Update a document
POST /projects/{projectId}/databases/(default)/documents:runQuery	Run a structured query

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /projects/{projectId}/databases/(default)/documents/{collectionId}

List documents in a collection

Detail	Value
Operation ID	cloud.listDocuments
Method	GET
Path	/projects/{projectId}/databases/(default)/documents/{collectionId}

Parameters

Name	Location	Type	Required
projectId	path	string	Yes
collectionId	path	string	Yes
pageSize	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Firebase connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listDocuments.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Firebase API reference.

POST /projects/{projectId}/databases/(default)/documents/{collectionId}

Create a document

Detail	Value
Operation ID	cloud.createDocument
Method	POST
Path	/projects/{projectId}/databases/(default)/documents/{collectionId}

Parameters

Name	Location	Type	Required
projectId	path	string	Yes
collectionId	path	string	Yes

Request Body

Field	Type
fields	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Firebase connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.createDocument.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Firebase API reference.

GET /projects/{projectId}/databases/(default)/documents/{documentPath}

Get a document

Detail	Value
Operation ID	cloud.getDocument
Method	GET
Path	/projects/{projectId}/databases/(default)/documents/{documentPath}

Parameters

Name	Location	Type	Required
projectId	path	string	Yes
documentPath	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Firebase connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.getDocument.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Firebase API reference.

PATCH /projects/{projectId}/databases/(default)/documents/{documentPath}

Update a document

Detail	Value
Operation ID	cloud.updateDocument
Method	PATCH
Path	/projects/{projectId}/databases/(default)/documents/{documentPath}

Parameters

Name	Location	Type	Required
projectId	path	string	Yes
documentPath	path	string	Yes

Request Body

Field	Type
fields	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Firebase connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.updateDocument.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Firebase API reference.

POST /projects/{projectId}/databases/(default)/documents:runQuery

Run a structured query

Detail	Value
Operation ID	cloud.runQuery
Method	POST
Path	/projects/{projectId}/databases/(default)/documents:runQuery

Parameters

Name	Location	Type	Required
projectId	path	string	Yes

Request Body

Field	Type
structuredQuery	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Firebase connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.runQuery.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Firebase API reference.