[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Add follow-up

> Add a follow-up email at the end of a campaign's sequence, with a delay after the previous email. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/mailshake/add_follow_up

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Add a follow-up email at the end of a campaign's sequence, with a delay after the previous email.

Mailshake MCP tools: https://cotlet.dev/docs/mcp/mailshake.md

MCP tool: `mailshake_write → add_follow_up`

Access: write. Confirm: waits for the user's OK before it runs.

Appends a follow-up to the sequence of a campaign. With reply_to_previous true it goes out as a reply in the same thread and has no subject of its own; with false it is a new email and needs subject. Follow-ups stop for a recipient who replies or becomes a lead, and bounced or unsubscribed recipients get none. On a campaign that already ran, the delay counts from each recipient's last send, so recipients who waited longer get the email at once. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | integer | yes | Campaign ID from list_campaigns. |
| `body` | string | yes | Body of the follow-up. Text replacements such as {{first}} work. |
| `delay_days` | integer | yes | Days to wait after the previous email in the sequence. |
| `reply_to_previous` | boolean | no | true to send as a reply in the same thread. Default: true. |
| `subject` | string | no | Subject line. Needed only when reply_to_previous is false. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "mailshake_write",
    "arguments": {
      "operation": "add_follow_up",
      "arguments": {
        "campaign_id": 4821,
        "body": "Hi {{first}}, one last note. Is client reporting still on your list this quarter?",
        "delay_days": 5,
        "reply_to_previous": true
      }
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "campaign_id": 4821,
    "message_id": 90314,
    "type": "follow-up",
    "position": 4,
    "reply_to_id": 90311,
    "delay_days": 5,
    "subject": null
  },
  "isError": false
}
```

Previous: [Move leads to campaign](https://cotlet.dev/docs/mcp/mailshake/move_leads_to_campaign.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.