intercom-reference-architecture
Implement Intercom reference architecture with layered project structure. Use when designing new Intercom integrations, reviewing project structure, or establishing architecture standards for Intercom applications. Trigger with phrases like "intercom architecture", "intercom project structure", "how to organize intercom", "intercom layout", "intercom design patterns".
Best use case
intercom-reference-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement Intercom reference architecture with layered project structure. Use when designing new Intercom integrations, reviewing project structure, or establishing architecture standards for Intercom applications. Trigger with phrases like "intercom architecture", "intercom project structure", "how to organize intercom", "intercom layout", "intercom design patterns".
Teams using intercom-reference-architecture 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-reference-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How intercom-reference-architecture Compares
| Feature / Agent | intercom-reference-architecture | 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?
Implement Intercom reference architecture with layered project structure. Use when designing new Intercom integrations, reviewing project structure, or establishing architecture standards for Intercom applications. Trigger with phrases like "intercom architecture", "intercom project structure", "how to organize intercom", "intercom layout", "intercom design patterns".
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.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Intercom Reference Architecture
## Overview
Production-ready architecture for Intercom integrations with layered separation, type-safe SDK usage, webhook processing, contact sync, and Help Center management.
## Project Structure
```
my-intercom-app/
├── src/
│ ├── intercom/
│ │ ├── client.ts # Singleton IntercomClient wrapper
│ │ ├── types.ts # Extended Intercom types
│ │ └── errors.ts # Custom error classes
│ ├── services/
│ │ ├── contacts.service.ts # Contact CRUD + search + merge
│ │ ├── conversations.service.ts # Conversation lifecycle
│ │ ├── articles.service.ts # Help Center article management
│ │ └── events.service.ts # Data event tracking
│ ├── webhooks/
│ │ ├── router.ts # Topic-based event routing
│ │ ├── signature.ts # X-Hub-Signature verification
│ │ └── handlers/
│ │ ├── conversation.handler.ts
│ │ └── contact.handler.ts
│ ├── sync/
│ │ ├── contact-sync.ts # CRM <-> Intercom contact sync
│ │ └── company-sync.ts # Company data sync
│ ├── api/
│ │ ├── health.ts # Health check endpoint
│ │ └── webhooks.ts # Webhook endpoint
│ └── cache/
│ └── intercom-cache.ts # LRU + Redis caching layer
├── tests/
│ ├── unit/
│ │ ├── contacts.test.ts
│ │ └── webhooks.test.ts
│ └── integration/
│ └── intercom.integration.test.ts
├── config/
│ ├── development.json
│ ├── staging.json
│ └── production.json
└── package.json
```
## Layer Architecture
```
┌─────────────────────────────────────────────┐
│ API / Webhook Layer │
│ Express routes, webhook endpoints │
├─────────────────────────────────────────────┤
│ Service Layer │
│ contacts.service, conversations.service │
│ Business logic, orchestration │
├─────────────────────────────────────────────┤
│ Intercom Client Layer │
│ intercom-client SDK, error handling │
│ Caching, rate limit management │
├─────────────────────────────────────────────┤
│ Infrastructure │
│ Redis cache, job queue, monitoring │
└─────────────────────────────────────────────┘
```
## Instructions
### Step 1: Client Layer
```typescript
// src/intercom/client.ts
import { IntercomClient, IntercomError } from "intercom-client";
let instance: IntercomClient | null = null;
export function getClient(): IntercomClient {
if (!instance) {
const token = process.env.INTERCOM_ACCESS_TOKEN;
if (!token) throw new Error("INTERCOM_ACCESS_TOKEN required");
instance = new IntercomClient({ token });
}
return instance;
}
// Typed error wrapper
export class IntercomServiceError extends Error {
constructor(
message: string,
public readonly statusCode: number,
public readonly code: string,
public readonly retryable: boolean,
public readonly requestId?: string
) {
super(message);
this.name = "IntercomServiceError";
}
static from(err: unknown): IntercomServiceError {
if (err instanceof IntercomError) {
const retryable = err.statusCode === 429 || (err.statusCode ?? 0) >= 500;
return new IntercomServiceError(
err.message,
err.statusCode ?? 500,
err.body?.errors?.[0]?.code ?? "unknown",
retryable,
err.body?.request_id
);
}
return new IntercomServiceError(
(err as Error).message, 500, "internal", false
);
}
}
```
### Step 2: Contacts Service
```typescript
// src/services/contacts.service.ts
import { getClient, IntercomServiceError } from "../intercom/client";
import { Intercom } from "intercom-client";
export class ContactsService {
private client = getClient();
async findOrCreate(params: {
email: string;
externalId: string;
name?: string;
customAttributes?: Record<string, any>;
}): Promise<Intercom.Contact> {
// Search first to avoid 409 conflicts
const existing = await this.client.contacts.search({
query: { field: "external_id", operator: "=", value: params.externalId },
});
if (existing.data.length > 0) {
return existing.data[0];
}
return this.client.contacts.create({
role: "user",
externalId: params.externalId,
email: params.email,
name: params.name,
customAttributes: params.customAttributes,
});
}
async syncFromCRM(crmUser: {
id: string;
email: string;
name: string;
plan: string;
company: string;
}): Promise<Intercom.Contact> {
const contact = await this.findOrCreate({
email: crmUser.email,
externalId: crmUser.id,
name: crmUser.name,
customAttributes: {
plan: crmUser.plan,
company_name: crmUser.company,
last_synced_at: Math.floor(Date.now() / 1000),
},
});
return contact;
}
async mergeLead(leadId: string, userId: string): Promise<Intercom.Contact> {
return this.client.contacts.merge({ from: leadId, into: userId });
}
async *searchAll(
query: Intercom.SearchRequest["query"]
): AsyncGenerator<Intercom.Contact> {
let startingAfter: string | undefined;
do {
const page = await this.client.contacts.search({
query,
pagination: { per_page: 50, starting_after: startingAfter },
});
for (const contact of page.data) yield contact;
startingAfter = page.pages?.next?.startingAfter ?? undefined;
} while (startingAfter);
}
}
```
### Step 3: Conversations Service
```typescript
// src/services/conversations.service.ts
import { getClient } from "../intercom/client";
export class ConversationsService {
private client = getClient();
async replyAsAdmin(
conversationId: string,
adminId: string,
body: string
): Promise<void> {
await this.client.conversations.reply({
conversationId,
type: "admin",
adminId,
body,
});
}
async addNote(
conversationId: string,
adminId: string,
note: string
): Promise<void> {
await this.client.conversations.reply({
conversationId,
type: "note",
adminId,
body: note,
});
}
async closeWithMessage(
conversationId: string,
adminId: string,
message?: string
): Promise<void> {
await this.client.conversations.close({
conversationId,
adminId,
body: message,
});
}
async getOpenConversationsForAdmin(adminId: string) {
return this.client.conversations.search({
query: {
operator: "AND",
value: [
{ field: "state", operator: "=", value: "open" },
{ field: "admin_assignee_id", operator: "=", value: adminId },
],
},
sort: { field: "updated_at", order: "descending" },
});
}
}
```
### Step 4: Articles Service (Help Center)
```typescript
// src/services/articles.service.ts
import { getClient } from "../intercom/client";
export class ArticlesService {
private client = getClient();
async createArticle(params: {
title: string;
body: string;
authorId: string;
parentId?: string; // Collection ID
state?: "published" | "draft";
}) {
return this.client.articles.create({
title: params.title,
body: params.body,
authorId: params.authorId,
parentId: params.parentId,
state: params.state || "draft",
});
}
async *listAll() {
const response = await this.client.articles.list();
for await (const article of response) {
yield article;
}
}
async listCollections() {
return this.client.helpCenter.listCollections();
}
}
```
### Step 5: Data Flow
```
┌──────────────┐ Webhook POST ┌───────────────┐
│ Intercom │ ─────────────────▶ │ Webhook │
│ Platform │ │ Router │
│ │ ◀── API calls ──── │ │
└──────────────┘ └───────┬───────┘
│
┌────────▼────────┐
│ Service Layer │
│ - Contacts │
│ - Conversations │
│ - Articles │
└────────┬────────┘
│
┌────────▼────────┐
│ Your Database │
│ + Cache (Redis)│
└─────────────────┘
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Circular dependencies | Service A imports B imports A | Use dependency injection |
| Client initialization race | Async token fetch | Lazy singleton pattern |
| Cache inconsistency | Stale data after update | Webhook-driven invalidation |
| Test isolation | Shared SDK state | `resetClient()` in beforeEach |
## Resources
- [Intercom API Reference](https://developers.intercom.com/docs/references/rest-api/api.intercom.io)
- [Articles API](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/articles)
- [Help Center API](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/help-center)
- [intercom-client npm](https://www.npmjs.com/package/intercom-client)
## Next Steps
For multi-environment setup, see `intercom-multi-env-setup`.Related Skills
workhuman-reference-architecture
Workhuman reference architecture for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman reference architecture".
wispr-reference-architecture
Wispr Flow reference architecture for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr reference architecture".
windsurf-reference-architecture
Implement Windsurf reference architecture with optimal project structure and AI configuration. Use when designing workspace configuration for Windsurf, setting up team standards, or establishing architecture patterns that maximize Cascade effectiveness. Trigger with phrases like "windsurf architecture", "windsurf project structure", "windsurf best practices", "windsurf team setup", "optimize for cascade".
windsurf-architecture-variants
Choose workspace architectures for different project scales in Windsurf. Use when deciding how to structure Windsurf workspaces for monorepos, multi-service setups, or polyglot codebases. Trigger with phrases like "windsurf workspace strategy", "windsurf monorepo", "windsurf project layout", "windsurf multi-service", "windsurf workspace size".
webflow-reference-architecture
Implement Webflow reference architecture — layered project structure, client wrapper, CMS sync service, webhook handlers, and caching layer for production integrations. Trigger with phrases like "webflow architecture", "webflow project structure", "how to organize webflow", "webflow integration design", "webflow best practices".
vercel-reference-architecture
Implement a Vercel reference architecture with layered project structure and best practices. Use when designing new Vercel projects, reviewing project structure, or establishing architecture standards for Vercel applications. Trigger with phrases like "vercel architecture", "vercel project structure", "vercel best practices layout", "how to organize vercel project".
vercel-architecture-variants
Choose and implement Vercel architecture blueprints for different scales and use cases. Use when designing new Vercel projects, choosing between static, serverless, and edge architectures, or planning how to structure a multi-project Vercel deployment. Trigger with phrases like "vercel architecture", "vercel blueprint", "how to structure vercel", "vercel monorepo", "vercel multi-project".
veeva-reference-architecture
Veeva Vault reference architecture for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva reference architecture".
vastai-reference-architecture
Implement Vast.ai reference architecture for GPU compute workflows. Use when designing ML training pipelines, structuring GPU orchestration, or establishing architecture patterns for Vast.ai applications. Trigger with phrases like "vastai architecture", "vastai design pattern", "vastai project structure", "vastai ml pipeline".
twinmind-reference-architecture
Production architecture for meeting AI systems using TwinMind: transcription pipeline, memory vault, action item workflow, and calendar integration. Use when implementing reference architecture, or managing TwinMind meeting AI operations. Trigger with phrases like "twinmind reference architecture", "twinmind reference architecture".
together-reference-architecture
Together AI reference architecture for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together reference architecture".
techsmith-reference-architecture
TechSmith reference architecture for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith reference architecture".