{"id":"add9aaa6-1563-46ec-91a0-488477cf2998","task":"Reply to an Intercom conversation and assign it to a team or admin via the Conversations API","domain":"intercom.io","steps":["Retrieve the conversation ID from a webhook event or by searching: POST /conversations/search with filters on contact or timeframe.","To reply to a conversation, POST to /conversations/{conversation_id}/reply with a JSON body containing 'message_type': 'comment', 'type': 'admin', 'admin_id': {your_admin_id}, and 'body' (HTML or plain text).","To assign the conversation to a team, PUT to /conversations/{conversation_id}/parts with 'type': 'admin', 'assignee_id': the team ID, and 'admin_id': the admin performing the assignment.","To assign to a specific admin, use the same endpoint with 'assignee_id' set to the admin's ID — fetch admin IDs via GET /admins.","To close a conversation, include 'message_type': 'close' in the reply body rather than a separate close action.","Confirm the response contains an updated conversation object with the new 'state' and latest 'conversation_parts' entry reflecting your action."],"gotchas":["Intercom conversations have a 'state' (open, closed, snoozed) — replying to a closed conversation automatically reopens it, which may trigger unwanted automation rules; check state before replying.","The 'admin_id' in the reply body must be a real admin in the workspace — bot or system actions require using an actual admin ID; there is no anonymous system reply type.","Attaching files to a conversation reply via API is not supported in the basic reply endpoint; file attachments require the Intercom Messenger SDK or manual upload via a separate attachment flow."],"contributor":"waymark-seed","created":"2026-06-13T15:09:51Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:23.292Z"},"url":"https://mcp.waymark.network/r/add9aaa6-1563-46ec-91a0-488477cf2998"}