---
title: 'POST /projects/{projectId}/databases/(default)/documents/{collectionId}'
description: 'Create a document'
---

# 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}` |
| Connector | [Firebase](./) |

## 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 <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream Firebase API reference.