[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)

# Reply to conversation

> Sends a reply to the customer in the conversation's own channel. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/trengo/reply_to_conversation

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)

Sends a reply to the customer in the conversation's own channel.

Trengo API: https://cotlet.dev/docs/api/trengo.md

`POST https://cotlet.dev/api/v1/trengo/conversations/{conversation_id}/replies`

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

Sends the message as you, by email, WhatsApp or whichever channel the conversation is on. A reply sent cannot be recalled through Cotlet. On WhatsApp, Trengo asks you to keep to WhatsApp's 24-hour limitation, and a template is the only way to start a conversation; this tool answers existing conversations only. Set close_after_send for Send and close. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | Conversation ID from list_conversations or search_conversations. |
| `message` | string | yes | Text to send. |
| `close_after_send` | boolean | no | Send and close in one step. Default: false. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/trengo/conversations/5120391/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message":"Hi Lena, your refund was issued today and shows on your statement within a few days. Reply here if it has not arrived by Friday."}'
```

**Python**

```python
result = client.call("trengo", "reply_to_conversation", {"conversation_id":5120391,"message":"Hi Lena, your refund was issued today and shows on your statement within a few days. Reply here if it has not arrived by Friday."})
```

**Node.js**

```js
const result = await cotlet.call('trengo', 'reply_to_conversation', {"conversation_id":5120391,"message":"Hi Lena, your refund was issued today and shows on your statement within a few days. Reply here if it has not arrived by Friday."});
```

**CLI**

```bash
cotlet call trengo reply_to_conversation --data '{"conversation_id":5120391,"message":"Hi Lena, your refund was issued today and shows on your statement within a few days. Reply here if it has not arrived by Friday."}'
```

## Example response

```json
{
  "conversation_id": 5120391,
  "message_id": 93410022,
  "channel": "Email",
  "sent_at": "2026-10-20T08:14:00Z",
  "closed": false
}
```

Previous: [Assign conversation](https://cotlet.dev/docs/api/trengo/assign_conversation.md)
Next: [Close conversation](https://cotlet.dev/docs/api/trengo/close_conversation.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.