> ## 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 Push Replyand Lead Toreply Followup Campaign:

> This endpoint lets you push a reply to a "reply followup campaign" The goal is to followup with interested leads in a templated, automated manner.

## 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_push_replyand_lead_toreply_followup_campaign:{"reply_id":"{{reply_id}}","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.reply_id`        | `integer` | Yes      |         | The ID of the reply                                                                       |
| `payload.campaign_id`     | `integer` | Yes      |         | The ID of the followup campaign                                                           |
| `payload.force_add_reply` | `boolean` | No       |         | optional Set this to true if you want to ignore the lead's unsubscribed or bounced status |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "This endpoint lets you push a reply to a \"reply followup campaign\" The goal is to followup with interested leads in a templated, automated manner. Followups are done in the same conversation thread, and we take the last message from the conversation to continue the process. Caveats: the reply must have a sender email attached. If you deleted a sender email, then you will need to add this lead into a separate outbound campaign since we cannot send an email in the same thread.",
    "properties": {
      "reply_id": {
        "type": "integer",
        "description": "The ID of the reply"
      },
      "campaign_id": {
        "type": "integer",
        "description": "The ID of the followup campaign"
      },
      "force_add_reply": {
        "type": "boolean",
        "description": "optional Set this to true if you want to ignore the lead's unsubscribed or bounced status"
      }
    },
    "required": [
      "reply_id",
      "campaign_id"
    ],
    "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": {
          "data": {
            "type": "object",
            "properties": {
              "success": {
                "type": "boolean"
              },
              "message": {
                "type": "string"
              }
            },
            "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 emailbison_push_replyand_lead_toreply_followup_campaign --payload '{
  "reply_id": "integer",
  "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`.