intercom-core-workflow-b
Manage Intercom conversations: create, reply, close, snooze, assign, and tag. Use when building conversation management features, automating replies, or implementing support workflow automation. Trigger with phrases like "intercom conversations", "intercom reply", "intercom assign conversation", "intercom close conversation", "intercom snooze", "manage intercom conversations".
Best use case
intercom-core-workflow-b is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manage Intercom conversations: create, reply, close, snooze, assign, and tag. Use when building conversation management features, automating replies, or implementing support workflow automation. Trigger with phrases like "intercom conversations", "intercom reply", "intercom assign conversation", "intercom close conversation", "intercom snooze", "manage intercom conversations".
Teams using intercom-core-workflow-b should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/intercom-core-workflow-b/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How intercom-core-workflow-b Compares
| Feature / Agent | intercom-core-workflow-b | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage Intercom conversations: create, reply, close, snooze, assign, and tag. Use when building conversation management features, automating replies, or implementing support workflow automation. Trigger with phrases like "intercom conversations", "intercom reply", "intercom assign conversation", "intercom close conversation", "intercom snooze", "manage intercom conversations".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Intercom Conversations & Messaging
## Overview
Manage the full conversation lifecycle: create, reply (as admin or contact), assign to teams, close, snooze, and tag. Conversations contain threaded "parts" including messages, notes, and assignments.
## Prerequisites
- Completed `intercom-install-auth` setup
- Admin ID (from `client.admins.list()`)
- Contact IDs for conversation participants
## Instructions
### Step 1: Create a Conversation
Conversations are created when a contact sends a message.
```typescript
import { IntercomClient } from "intercom-client";
const client = new IntercomClient({
token: process.env.INTERCOM_ACCESS_TOKEN!,
});
// Create conversation from a contact
const conversation = await client.conversations.create({
from: {
type: "user",
id: "6657add46abd0167d9419c3a", // Contact ID
},
body: "Hi, I'm having trouble with my billing. Can you help?",
});
console.log(`Conversation ID: ${conversation.conversationId}`);
```
### Step 2: Reply to a Conversation
```typescript
// Admin reply (visible to customer)
await client.conversations.reply({
conversationId: conversation.conversationId,
body: "Hi there! I'd be happy to help with billing. What's the issue?",
type: "admin",
adminId: "12345", // Your admin ID
});
// Admin note (internal, not visible to customer)
await client.conversations.reply({
conversationId: conversation.conversationId,
body: "Customer is on Enterprise plan, checking billing system...",
type: "note",
adminId: "12345",
});
// Contact reply
await client.conversations.reply({
conversationId: conversation.conversationId,
body: "I was charged twice for this month.",
type: "user",
intercomUserId: "6657add46abd0167d9419c3a",
});
```
### Step 3: Assign a Conversation
```typescript
// Assign to a specific admin
await client.conversations.assign({
conversationId: conversation.conversationId,
type: "admin",
adminId: "12345",
assigneeId: "67890", // Target admin ID
body: "Assigning to billing specialist",
});
// Assign to a team
await client.conversations.assign({
conversationId: conversation.conversationId,
type: "team",
adminId: "12345",
assigneeId: "team-billing-123",
body: "Routing to billing team",
});
// Auto-assign using assignment rules
// POST /conversations/{id}/run_assignment_rules
await fetch(`https://api.intercom.io/conversations/${conversation.conversationId}/run_assignment_rules`, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.INTERCOM_ACCESS_TOKEN}`,
"Content-Type": "application/json",
},
});
```
### Step 4: Close and Snooze Conversations
```typescript
// Close a conversation (with optional closing message)
await client.conversations.close({
conversationId: conversation.conversationId,
adminId: "12345",
body: "Issue resolved! Let us know if you need anything else.",
});
// Snooze until a specific time
await client.conversations.snooze({
conversationId: conversation.conversationId,
adminId: "12345",
snoozedUntil: Math.floor(Date.now() / 1000) + 86400, // 24 hours from now
});
// Reopen a closed conversation
await client.conversations.open({
conversationId: conversation.conversationId,
adminId: "12345",
});
```
### Step 5: Tag Conversations
```typescript
// Tag a conversation
await client.conversations.attachTag({
conversationId: conversation.conversationId,
tagId: "tag-billing-issue",
adminId: "12345",
});
// Remove a tag
await client.conversations.detachTag({
conversationId: conversation.conversationId,
tagId: "tag-billing-issue",
adminId: "12345",
});
```
### Step 6: Retrieve Conversation with Parts
```typescript
const full = await client.conversations.find({
conversationId: conversation.conversationId,
});
console.log(`State: ${full.state}`); // "open", "closed", "snoozed"
console.log(`Assignee: ${full.adminAssigneeId}`);
console.log(`Parts: ${full.conversationParts.totalCount}`);
// Iterate conversation parts (messages, notes, assignments)
for (const part of full.conversationParts.conversationParts) {
console.log(` [${part.partType}] ${part.author.type}: ${part.body?.substring(0, 50)}`);
}
// Conversation parts include:
// - comment (admin/user messages)
// - note (internal notes)
// - assignment (team/admin assignments)
// - close/open (state changes)
```
### Step 7: List and Filter Conversations
```typescript
// List all conversations
const conversations = await client.conversations.list();
// Search conversations
const searched = await client.conversations.search({
query: {
operator: "AND",
value: [
{ field: "state", operator: "=", value: "open" },
{ field: "admin_assignee_id", operator: "=", value: "12345" },
],
},
pagination: { per_page: 20 },
sort: { field: "updated_at", order: "descending" },
});
```
## Conversation States
| State | Description | Transitions |
|-------|-------------|-------------|
| `open` | Active, awaiting action | close, snooze |
| `closed` | Resolved | open |
| `snoozed` | Deferred until timestamp | open (auto or manual) |
## Conversation Part Types
| Part Type | Description | Who Creates |
|-----------|-------------|------------|
| `comment` | Visible message | Admin or contact |
| `note` | Internal-only note | Admin |
| `assignment` | Reassignment record | System or admin |
| `close` | Conversation closed | Admin |
| `open` | Conversation reopened | Admin or contact |
## Error Handling
| Error | HTTP Code | Cause | Solution |
|-------|-----------|-------|----------|
| `not_found` | 404 | Invalid conversation or admin ID | Verify IDs exist |
| `conversation_not_found` | 404 | Conversation deleted | Handle gracefully |
| `admin_not_found` | 404 | Admin ID invalid | Use `client.admins.list()` |
| `parameter_invalid` | 422 | Missing body or type | Include required fields |
| `conversation_closed` | 400 | Action on closed conversation | Reopen first |
## Resources
- [Conversations API](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations)
- [Reply to Conversation](https://developers.intercom.com/docs/references/2.2/rest-api/conversations/reply-to-a-conversation)
- [Manage Conversation](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations/manageconversation)
## Next Steps
For common errors and debugging, see `intercom-common-errors`.Related Skills
calendar-to-workflow
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
workhuman-core-workflow-b
Workhuman core workflow b for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow b".
workhuman-core-workflow-a
Workhuman core workflow a for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow a".
wispr-core-workflow-b
Wispr Flow core workflow b for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow b".
wispr-core-workflow-a
Wispr Flow core workflow a for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow a".
windsurf-core-workflow-b
Execute Windsurf's secondary workflow: Workflows, Memories, and reusable automation. Use when creating reusable Cascade workflows, managing persistent memories, or automating repetitive development tasks. Trigger with phrases like "windsurf workflow", "windsurf automation", "windsurf memories", "cascade workflow", "windsurf slash command".
windsurf-core-workflow-a
Execute Windsurf's primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature".
webflow-core-workflow-b
Execute Webflow secondary workflows — Sites management, Pages API, Forms submissions, Ecommerce (products/orders/inventory), and Custom Code via the Data API v2. Use when managing sites, reading pages, handling form data, or working with Webflow Ecommerce products and orders. Trigger with phrases like "webflow sites", "webflow pages", "webflow forms", "webflow ecommerce", "webflow products", "webflow orders".
webflow-core-workflow-a
Execute the primary Webflow workflow — CMS content management: list collections, CRUD items, publish items, and manage content lifecycle via the Data API v2. Use when working with Webflow CMS collections and items, managing blog posts, team members, or any dynamic content. Trigger with phrases like "webflow CMS", "webflow collections", "webflow items", "create webflow content", "manage webflow CMS", "webflow content management".
veeva-core-workflow-b
Veeva Vault core workflow b for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow b".
veeva-core-workflow-a
Veeva Vault core workflow a for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow a".
vastai-core-workflow-b
Execute Vast.ai secondary workflow: multi-instance orchestration, spot recovery, and cost optimization. Use when running distributed training, handling spot preemption, or optimizing GPU spend across multiple instances. Trigger with phrases like "vastai distributed training", "vastai spot recovery", "vastai multi-gpu", "vastai cost optimization".