---
title: 'POST /conversations/{id}/reply'
description: 'Reply to a conversation'
---

# POST /conversations/{id}/reply

Reply to a conversation

| Detail | Value |
|---|---|
| Operation ID | `support.replyToConversation` |
| Method | `POST` |
| Path | `/conversations/{id}/reply` |
| Connector | [Intercom](./) |

## Parameters

| Name | Location | Type | Required |
|---|---|---|---|
| `id` | path | string | **Yes** |

## Request Body

| Field | Type |
|---|---|
| `message_type` | string |
| `type` | string |
| `body` | string |


## Using this endpoint in a workflow

1. Add an **API Call** node to your workflow.
2. Pick your Intercom connection from the Connection dropdown.
3. In the Operation dropdown, select `support.replyToConversation`.
4. Fill in the parameter fields that appear. Use `{{...}}` to reference upstream values.

**Required fields are marked — fill them or the call will fail at runtime.**

## What it returns

The `API Call` node writes the response to the workflow context:

```
{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}
```

Reference response fields downstream as <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream Intercom API reference.