intercom-observability
Set up observability for Intercom integrations with metrics, traces, and alerts. Use when implementing monitoring for Intercom API operations, setting up dashboards, or configuring alerting for integration health. Trigger with phrases like "intercom monitoring", "intercom metrics", "intercom observability", "monitor intercom", "intercom alerts", "intercom tracing".
Best use case
intercom-observability is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Set up observability for Intercom integrations with metrics, traces, and alerts. Use when implementing monitoring for Intercom API operations, setting up dashboards, or configuring alerting for integration health. Trigger with phrases like "intercom monitoring", "intercom metrics", "intercom observability", "monitor intercom", "intercom alerts", "intercom tracing".
Teams using intercom-observability 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-observability/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How intercom-observability Compares
| Feature / Agent | intercom-observability | 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?
Set up observability for Intercom integrations with metrics, traces, and alerts. Use when implementing monitoring for Intercom API operations, setting up dashboards, or configuring alerting for integration health. Trigger with phrases like "intercom monitoring", "intercom metrics", "intercom observability", "monitor intercom", "intercom alerts", "intercom tracing".
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
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
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.
SKILL.md Source
# Intercom Observability
## Overview
Comprehensive observability for Intercom integrations covering Prometheus metrics, OpenTelemetry traces, structured logging, and alert rules for error rates, latency, and rate limit usage.
## Prerequisites
- Prometheus or compatible metrics backend
- OpenTelemetry SDK (optional, for tracing)
- Pino or similar structured logger
- Grafana or alerting system
## Instructions
### Step 1: Prometheus Metrics for Intercom API Calls
```typescript
import { Registry, Counter, Histogram, Gauge } from "prom-client";
const registry = new Registry();
// Total API requests by endpoint and status
const intercomRequests = new Counter({
name: "intercom_api_requests_total",
help: "Total Intercom API requests",
labelNames: ["endpoint", "method", "status"] as const,
registers: [registry],
});
// Request duration by endpoint
const intercomDuration = new Histogram({
name: "intercom_api_request_duration_seconds",
help: "Intercom API request duration in seconds",
labelNames: ["endpoint", "method"] as const,
buckets: [0.05, 0.1, 0.25, 0.5, 1, 2.5, 5, 10],
registers: [registry],
});
// Error counter by type
const intercomErrors = new Counter({
name: "intercom_api_errors_total",
help: "Intercom API errors by type",
labelNames: ["endpoint", "error_code", "status_code"] as const,
registers: [registry],
});
// Rate limit remaining gauge
const intercomRateLimit = new Gauge({
name: "intercom_rate_limit_remaining",
help: "Intercom API rate limit remaining requests",
registers: [registry],
});
// Webhook processing metrics
const webhookProcessed = new Counter({
name: "intercom_webhooks_processed_total",
help: "Intercom webhooks processed by topic",
labelNames: ["topic", "status"] as const,
registers: [registry],
});
```
### Step 2: Instrumented API Client Wrapper
```typescript
import { IntercomClient, IntercomError } from "intercom-client";
function instrumentedClient(client: IntercomClient): IntercomClient {
return new Proxy(client, {
get(target, prop) {
const value = (target as any)[prop];
if (typeof value === "object" && value !== null) {
// Wrap service objects (contacts, conversations, etc.)
return new Proxy(value, {
get(serviceTarget, methodName) {
const method = (serviceTarget as any)[methodName];
if (typeof method !== "function") return method;
return async (...args: any[]) => {
const endpoint = `${String(prop)}.${String(methodName)}`;
const timer = intercomDuration.startTimer({ endpoint, method: "API" });
try {
const result = await method.apply(serviceTarget, args);
intercomRequests.inc({ endpoint, method: "API", status: "success" });
return result;
} catch (err) {
if (err instanceof IntercomError) {
const statusCode = String(err.statusCode ?? "unknown");
const errorCode = err.body?.errors?.[0]?.code ?? "unknown";
intercomRequests.inc({ endpoint, method: "API", status: "error" });
intercomErrors.inc({ endpoint, error_code: errorCode, status_code: statusCode });
// Track rate limit from error response
if (err.statusCode === 429) {
intercomRateLimit.set(0);
}
}
throw err;
} finally {
timer();
}
};
},
});
}
return value;
},
});
}
// Usage
const rawClient = new IntercomClient({ token: process.env.INTERCOM_ACCESS_TOKEN! });
const client = instrumentedClient(rawClient);
```
### Step 3: Structured Logging
```typescript
import pino from "pino";
const logger = pino({
name: "intercom",
level: process.env.LOG_LEVEL || "info",
serializers: {
// Redact PII from logs
contact: (contact: any) => ({
id: contact.id,
role: contact.role,
// Never log email, name, phone
}),
err: pino.stdSerializers.err,
},
});
// Intercom operation logger
function logIntercomOp(
operation: string,
details: Record<string, any>,
durationMs: number
): void {
logger.info({
service: "intercom",
operation,
duration_ms: Math.round(durationMs),
...details,
});
}
// Webhook logger
function logWebhook(
topic: string,
notificationId: string,
status: "processed" | "failed" | "skipped",
durationMs?: number
): void {
logger.info({
service: "intercom",
type: "webhook",
topic,
notification_id: notificationId,
status,
duration_ms: durationMs ? Math.round(durationMs) : undefined,
});
}
```
### Step 4: OpenTelemetry Tracing
```typescript
import { trace, SpanStatusCode, Span } from "@opentelemetry/api";
const tracer = trace.getTracer("intercom-integration");
async function tracedIntercomCall<T>(
operationName: string,
attributes: Record<string, string>,
operation: () => Promise<T>
): Promise<T> {
return tracer.startActiveSpan(
`intercom.${operationName}`,
{ attributes },
async (span: Span) => {
try {
const result = await operation();
span.setStatus({ code: SpanStatusCode.OK });
return result;
} catch (err: any) {
span.setStatus({ code: SpanStatusCode.ERROR, message: err.message });
span.recordException(err);
if (err instanceof IntercomError) {
span.setAttribute("intercom.status_code", err.statusCode ?? 0);
span.setAttribute("intercom.error_code", err.body?.errors?.[0]?.code ?? "unknown");
span.setAttribute("intercom.request_id", err.body?.request_id ?? "");
}
throw err;
} finally {
span.end();
}
}
);
}
// Usage
const contact = await tracedIntercomCall(
"contacts.find",
{ "intercom.contact_id": contactId },
() => client.contacts.find({ contactId })
);
```
### Step 5: Alert Rules
```yaml
# prometheus/intercom-alerts.yml
groups:
- name: intercom_integration
rules:
- alert: IntercomHighErrorRate
expr: |
rate(intercom_api_errors_total[5m]) /
rate(intercom_api_requests_total[5m]) > 0.05
for: 5m
labels:
severity: warning
annotations:
summary: "Intercom error rate > 5%"
description: "{{ $value | humanizePercentage }} of requests failing"
- alert: IntercomHighLatency
expr: |
histogram_quantile(0.95,
rate(intercom_api_request_duration_seconds_bucket[5m])
) > 3
for: 5m
labels:
severity: warning
annotations:
summary: "Intercom P95 latency > 3s"
- alert: IntercomRateLimitLow
expr: intercom_rate_limit_remaining < 1000
for: 1m
labels:
severity: critical
annotations:
summary: "Intercom rate limit < 1000 remaining"
description: "Only {{ $value }} requests remaining before rate limit"
- alert: IntercomAuthFailures
expr: rate(intercom_api_errors_total{status_code="401"}[5m]) > 0
for: 1m
labels:
severity: critical
annotations:
summary: "Intercom authentication failures detected"
- alert: IntercomWebhookFailures
expr: |
rate(intercom_webhooks_processed_total{status="failed"}[5m]) > 0.1
for: 5m
labels:
severity: warning
annotations:
summary: "Intercom webhook processing failures"
```
### Step 6: Metrics Endpoint
```typescript
// Expose Prometheus metrics
app.get("/metrics", async (req, res) => {
res.set("Content-Type", registry.contentType);
res.send(await registry.metrics());
});
```
## Key Metrics Summary
| Metric | Type | Alert Threshold |
|--------|------|----------------|
| `intercom_api_requests_total` | Counter | N/A (baseline) |
| `intercom_api_request_duration_seconds` | Histogram | P95 > 3s |
| `intercom_api_errors_total` | Counter | > 5% error rate |
| `intercom_rate_limit_remaining` | Gauge | < 1000 |
| `intercom_webhooks_processed_total` | Counter | Failed > 10% |
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| High cardinality | Too many unique labels | Use endpoint groups, not IDs |
| Missing metrics | Uninstrumented calls | Wrap client with proxy |
| Alert storms | Wrong thresholds | Tune based on baseline data |
| Log volume too high | Debug logging in prod | Set LOG_LEVEL=info |
## Resources
- [Prometheus Best Practices](https://prometheus.io/docs/practices/naming/)
- [OpenTelemetry Node.js](https://opentelemetry.io/docs/languages/js/)
- [Pino Logger](https://getpino.io/)
## Next Steps
For incident response, see `intercom-incident-runbook`.Related Skills
windsurf-observability
Monitor Windsurf AI adoption, feature usage, and team productivity metrics. Use when tracking AI feature usage, measuring ROI, setting up dashboards, or analyzing Cascade effectiveness across your team. Trigger with phrases like "windsurf monitoring", "windsurf metrics", "windsurf analytics", "windsurf usage", "windsurf adoption".
webflow-observability
Set up observability for Webflow integrations — Prometheus metrics for API calls, OpenTelemetry tracing, structured logging with pino, Grafana dashboards, and alerting for rate limits, errors, and latency. Trigger with phrases like "webflow monitoring", "webflow metrics", "webflow observability", "monitor webflow", "webflow alerts", "webflow tracing".
vercel-observability
Set up Vercel observability with runtime logs, analytics, log drains, and OpenTelemetry tracing. Use when implementing monitoring for Vercel deployments, setting up log drains, or configuring alerting for function errors and performance. Trigger with phrases like "vercel monitoring", "vercel metrics", "vercel observability", "vercel logs", "vercel alerts", "vercel tracing".
veeva-observability
Veeva Vault observability for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva observability".
vastai-observability
Monitor Vast.ai GPU instance health, utilization, and costs. Use when setting up monitoring dashboards, configuring alerts, or tracking GPU utilization and spending. Trigger with phrases like "vastai monitoring", "vastai metrics", "vastai observability", "monitor vastai", "vastai alerts".
twinmind-observability
Monitor TwinMind transcription quality, meeting coverage, action item extraction rates, and memory vault health. Use when implementing observability, or managing TwinMind meeting AI operations. Trigger with phrases like "twinmind observability", "twinmind observability".
speak-observability
Monitor Speak API health, assessment latency, session metrics, and pronunciation score distributions. Use when implementing observability, or managing Speak language learning platform operations. Trigger with phrases like "speak observability", "speak observability".
snowflake-observability
Set up Snowflake observability using ACCOUNT_USAGE views, alerts, and external monitoring. Use when implementing Snowflake monitoring dashboards, setting up query performance tracking, or configuring alerting for warehouse and pipeline health. Trigger with phrases like "snowflake monitoring", "snowflake metrics", "snowflake observability", "snowflake dashboard", "snowflake alerts".
shopify-observability
Set up observability for Shopify app integrations with query cost tracking, rate limit monitoring, webhook delivery metrics, and structured logging. Trigger with phrases like "shopify monitoring", "shopify metrics", "shopify observability", "monitor shopify API", "shopify alerts", "shopify dashboard".
salesforce-observability
Set up observability for Salesforce integrations with API limit monitoring, error tracking, and alerting. Use when implementing monitoring for Salesforce operations, tracking API consumption, or configuring alerting for Salesforce integration health. Trigger with phrases like "salesforce monitoring", "salesforce metrics", "salesforce observability", "monitor salesforce", "salesforce alerts", "salesforce API usage dashboard".
retellai-observability
Retell AI observability — AI voice agent and phone call automation. Use when working with Retell AI for voice agents, phone calls, or telephony. Trigger with phrases like "retell observability", "retellai-observability", "voice agent".
replit-observability
Monitor Replit deployments with health checks, uptime tracking, resource usage, and alerting. Use when setting up monitoring for Replit apps, building health dashboards, or configuring alerting for deployment health and performance. Trigger with phrases like "replit monitoring", "replit metrics", "replit observability", "monitor replit", "replit alerts", "replit uptime".