> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Clickhouse Click Pipe Cdc Scaling Update: Inputs, Cost &

> Update CDC ClickPipes scaling. Includes inputs, outputs, pricing notes, Deepline CLI examples, and GTM automation guidance.

## Run in Enrichment Spreadsheet

<Info>
  Use this function as a column step in `deepline enrich`.
</Info>

```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=clickhouse_click_pipe_cdc_scaling_update:{"organizationId":"{{organizationId}}","serviceId":"{{serviceId}}"}' --json
```

<Tip>
  Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
</Tip>

## Input Schema

| Name                           | Type      | Required | Default | Description                                                     |
| ------------------------------ | --------- | -------- | ------- | --------------------------------------------------------------- |
| `payload.organizationId`       | `string`  | Yes      |         | ID of the organization that owns the service.                   |
| `payload.serviceId`            | `string`  | Yes      |         | ID of the service that owns the ClickPipe.                      |
| `payload.replicaCpuMillicores` | `integer` | No       |         | CPU in millicores for DB ClickPipes.                            |
| `payload.replicaMemoryGb`      | `number`  | No       |         | Memory in GiB for DB ClickPipes. Must be 4× the CPU core count. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Update scaling settings for database ClickPipes (PostgreSQL, MySQL, MongoDB, BigQuery). The infrastructure is shared between all database ClickPipes in the service, both for initial load and CDC. Scaling settings may take a few minutes to fully propagate. For billing purposes, 2 CPU cores and 8 GB of RAM [correspond](https://clickhouse.com/docs/cloud/manage/billing/overview#clickpipes-for-postgres-cdc) to one compute unit. If your organization tier changes, database ClickPipes will be [rescaled](https://clickhouse.com/docs/cloud/manage/billing/overview#compute) appropriately. **Note:** For Kafka, Kinesis, and object storage pipes (S3, GCS, Azure Blob), see [Get ClickPipe](#tag/ClickPipes/operation/clickPipeGet). **This endpoint becomes available once at least one database ClickPipe was provisioned.**",
    "properties": {
      "organizationId": {
        "type": "string",
        "description": "ID of the organization that owns the service.",
        "format": "uuid"
      },
      "serviceId": {
        "type": "string",
        "description": "ID of the service that owns the ClickPipe.",
        "format": "uuid"
      },
      "replicaCpuMillicores": {
        "type": "integer",
        "description": "CPU in millicores for DB ClickPipes.",
        "multipleOf": 1000,
        "minimum": 1000,
        "maximum": 32000
      },
      "replicaMemoryGb": {
        "type": "number",
        "description": "Memory in GiB for DB ClickPipes. Must be 4× the CPU core count.",
        "multipleOf": 4,
        "minimum": 4,
        "maximum": 128
      }
    },
    "required": [
      "organizationId",
      "serviceId"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

| Name          | Type     | Required | Default | Description                                    |
| ------------- | -------- | -------- | ------- | ---------------------------------------------- |
| `result.data` | `object` | Yes      |         | Provider response payload.                     |
| `result.meta` | `object` | No       |         | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "status": {
            "type": "number",
            "description": "HTTP status code."
          },
          "requestId": {
            "type": "string",
            "description": "Unique id assigned to every request. UUIDv4",
            "format": "uuid"
          },
          "result": {
            "properties": {
              "replicaCpuMillicores": {
                "type": "integer",
                "description": "CPU in millicores for DB ClickPipes.",
                "multipleOf": 1000,
                "minimum": 1000,
                "maximum": 32000
              },
              "replicaMemoryGb": {
                "type": "number",
                "description": "Memory in GiB for DB ClickPipes. Must be 4× the CPU core count.",
                "multipleOf": 4,
                "minimum": 4,
                "maximum": 128
              }
            },
            "additionalProperties": false
          }
        },
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Advanced: Direct CLI

<Info>
  Use direct execution for single payload debugging.
</Info>

```bash theme={null}
deepline tools execute clickhouse_click_pipe_cdc_scaling_update --payload '{
  "organizationId": "string",
  "serviceId": "string"
}' --json
```

### CLI flags

| Flag                        | Description                                         |
| --------------------------- | --------------------------------------------------- |
| `--json`                    | Print machine-readable output.                      |
| `--wait`                    | Wait for terminal provider status when supported.   |
| `--debug`                   | Enable wait mode with additional status/log output. |
| `--wait-timeout SECONDS`    | Max seconds to wait in wait mode.                   |
| `--poll-interval SECONDS`   | Polling interval in seconds during wait mode.       |
| `--timeout SECONDS`         | Request timeout in seconds.                         |
| `--connect-timeout SECONDS` | Connection timeout in seconds.                      |

## Cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.
* Billing mode: `no_bill`.