> ## 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.

# Emailbison Get Campaign Replies: Inputs, Cost & CLI

> This endpoint retrieves all replies associated with a campaign. 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=emailbison_get_campaign_replies:{"campaign_id":"{{campaign_id}}"}' --json
```

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

## Input Schema

| Name                      | Type      | Required | Default | Description                                                                      |
| ------------------------- | --------- | -------- | ------- | -------------------------------------------------------------------------------- |
| `payload.campaign_id`     | `integer` | Yes      |         | The ID of the campaign.                                                          |
| `payload.search`          | `string`  | No       |         | Search term for filtering replies.                                               |
| `payload.status`          | `string`  | No       |         | Filter by status. One of `interested`, `automated_reply`, `not_automated_reply`. |
| `payload.folder`          | `string`  | No       |         | Filter by folder. One of `inbox`, `sent`, `spam`, `bounced`, `all`.              |
| `payload.read`            | `boolean` | No       |         | Filter by read status.                                                           |
| `payload.sender_email_id` | `integer` | No       |         | The ID of the sender email address.                                              |
| `payload.lead_id`         | `integer` | No       |         | The id of an existing record in the leads table.                                 |
| `payload.tag_ids`         | `array`   | No       |         | Array of tag IDs to filter by.                                                   |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "This endpoint retrieves all replies associated with a campaign.",
    "properties": {
      "campaign_id": {
        "type": "integer",
        "description": "The ID of the campaign."
      },
      "search": {
        "type": [
          "string",
          "null"
        ],
        "description": "Search term for filtering replies."
      },
      "status": {
        "type": "string",
        "description": "Filter by status. One of `interested`, `automated_reply`, `not_automated_reply`."
      },
      "folder": {
        "type": "string",
        "description": "Filter by folder. One of `inbox`, `sent`, `spam`, `bounced`, `all`."
      },
      "read": {
        "type": [
          "boolean",
          "null"
        ],
        "description": "Filter by read status."
      },
      "sender_email_id": {
        "type": "integer",
        "description": "The ID of the sender email address."
      },
      "lead_id": {
        "type": "integer",
        "description": "The id of an existing record in the leads table."
      },
      "tag_ids": {
        "type": "array",
        "description": "Array of tag IDs to filter by.",
        "items": {
          "type": "integer"
        }
      }
    },
    "required": [
      "campaign_id"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

| Name          | Type     | Required | Default | Description                                    |
| ------------- | -------- | -------- | ------- | ---------------------------------------------- |
| `result.data` | `string` | 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": "string",
        "description": "Provider response payload."
      },
      "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 emailbison_get_campaign_replies --payload '{
  "campaign_id": "integer"
}' --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`.