Create conversation reply with the Intercom API

Replies to a conversation as a teammate. A comment goes to the contact through the channel of the conversation, such as the Messenger or email; a note stays internal, visible only to teammates. Closing, snoozing, reopening and assigning are done by Manage conversation.

Identifier
intercom_create_conversation_reply

The request

POST https://connect.reportei.com/api/tools/intercom_create_conversation_reply/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "conversation_id": "<conversation_id>",
    "message_type": "comment",
    "type": "admin",
    "admin_id": "<admin_id>",
    "body": "<body>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
conversation_idstringYesId of the conversation, from List conversations or Search conversations.
message_typestringYescomment is a reply the contact sees; note is internal.Values: comment, note
typestringYesAlways admin: the reply comes from a teammate.Values: admin
admin_idstringYesId of the teammate who writes the reply, from List admins.
bodystringYesText of the reply. Notes accept some HTML formatting.
attachment_urlsarrayNoURLs of images to attach, up to 10.
skip_notificationsbooleanNotrue sends the reply without notifications.

Supported connections

Your customer connects their Intercom account once, with one of the modes below. The same connection serves every tool of the toolkit.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/intercom, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/intercom_create_conversation_reply. It becomes your agent's tool definition with no conversion.

Other Intercom tools

See all 13 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.