intercom-core-workflow-a

v2026.09.24

Manage Intercom contacts: create, search, update, merge leads into users. Use when building contact management features, syncing user data, or implementing contact search and segmentation against the Intercom REST API. Trigger with phrases like "intercom contacts", "intercom users", "intercom leads", "create intercom contact", "search intercom contacts", "merge intercom lead".

GitHub
Install command
npx skhub add jeremylongshore/intercom-core-workflow-a
Markdown
SKILL.md

Intercom Contacts & Contact Management

Overview

Primary workflow for managing Intercom contacts. Covers creating users and leads, searching with filters, updating custom attributes, merging leads into users, and listing segments. This SKILL.md gives you the high-level workflow and the first example; drill into references/implementation.md for the full step-by-step code and references/examples.md for end-to-end flows.

Prerequisites

  • Completed intercom-install-auth setup
  • Understanding of Intercom contact model (users vs leads)
  • Valid API credentials with contacts read/write scope

Instructions

The contact workflow is six operations against the intercom-client SDK. Instantiate the client once, then call the operation you need:

import { IntercomClient } from "intercom-client";

const client = new IntercomClient({
  token: process.env.INTERCOM_ACCESS_TOKEN!,
});

// Create an identified user (has external_id)
const user = await client.contacts.create({
  role: "user",
  externalId: "customer-9001",
  email: "alice@acme.com",
  name: "Alice Johnson",
  customAttributes: { plan: "enterprise" },
});

The six operations, in the order you typically reach for them:

  1. Create contacts — contacts.create with role: "user" (identified, needs externalId) or role: "lead" (anonymous).
  2. Search contacts — contacts.search with a single filter or a compound AND/OR query, plus pagination and sort.
  3. Update a contact — contacts.update by contactId to change name or custom attributes.
  4. Merge a lead into a user — contacts.merge({ from: leadId, into: userId }); the lead's conversations, events, and tags transfer to the user.
  5. List segments — contacts.listSegments({ contactId }) to see which segments a contact belongs to.
  6. Paginate all contacts — contacts.list with startingAfter cursor to stream the full contact base.

Full code for every step, including compound-search filters and the async-generator pagination helper, is in references/implementation.md.

Output

Each operation returns a typed response from the SDK:

  • create / update — a single contact object: { type: "contact", id, role, email, name, customAttributes, created_at, ... }. The id is the Intercom-generated handle you pass to later calls.
  • search — { data: Contact[], totalCount, pages }. Iterate data; read totalCount for the match count; use pages.next.startingAfter to page.
  • merge — the surviving user contact (the into target); the from lead is deleted.
  • listSegments — { data: Segment[] }, each { id, name }.
  • list — one page { data: Contact[], pages }; follow pages.next.startingAfter until it is absent.

Contact Data Model

FieldTypeDescription
idstringIntercom-generated unique ID
external_idstringYour system's user ID
role"user" or "lead"Contact type
emailstringEmail address
namestringFull name
phonestringPhone number
custom_attributesobjectCustom key-value data
created_atnumberUnix timestamp
last_seen_atnumberLast activity timestamp
signed_up_atnumberSignup timestamp
tagsobjectApplied tags list
companiesobjectAssociated companies
locationobjectGeoIP location data

Error Handling

ErrorHTTP CodeCauseSolution
not_found404Contact ID doesn't existVerify with search first
conflict409Duplicate external_id or emailSearch before creating
parameter_invalid422Bad field value or missing required fieldCheck field types and names
rate_limit_exceeded429Over 10,000 req/min (private apps)Add backoff, batch operations
merge_not_possible400Merging user into lead (reversed)from must be lead, into must be user

Examples

Quick create-then-search flow:

const user = await client.contacts.create({
  role: "user",
  externalId: "customer-9001",
  email: "alice@acme.com",
  name: "Alice Johnson",
});

const found = await client.contacts.search({
  query: { field: "email", operator: "=", value: "alice@acme.com" },
});
console.log(`Found ${found.totalCount} match(es)`);

Three fuller worked flows — lead-to-user lifecycle, segmenting recent enterprise signups, and streaming every contact for an export — are in references/examples.md.

Resources

Next Steps

For conversation management (creating, replying to, and searching conversations), see the companion skill intercom-core-workflow-b, which builds on the contact IDs produced by this workflow.

Discovery
Tags

No tags published for this skill.

Version
Latest version metadata

Version

v2026.09.24

Published

Sep 24, 2026

Category

Uncategorized

License

MIT

Source path

skills/.curated/intercom-core-workflow-a

Default branch

main

Latest commit

e5a6c3b

Tree SHA

c2dc8e8