Search

Purpose:

1. Search for resources in Intercom (conversations and contacts) using a unified query approach.
2. Note that only a subset of properties will be returned in search results.
3. For complete details, use the Fetch tool with the returned IDs.

Usage:

1. MUST specify object_type
   OR object_type
   to indicate which API to call.
2. Use specific field searches for precise filtering (e.g., email
   @example.com).
3. Use the starting_after parameter for pagination when more results exist.
4. Combine multiple search criteria with logical operators for complex queries.

Search Tool Response:

1. Returns results with id, title, text, and url for each match.
2. IDs are prefixed with 'conversation_' or 'contact_' to indicate type.
3. Use these IDs with the Fetch tool to get complete resource details.

Intercom Search Query DSL specification:

• Tokens separated by spaces • Each token: key[

] • op (optional; default "eq") ∈ { eq, neq, gt, lt, in, nin, contains } • value: unquoted (alphanumeric, no spaces) or quoted in single/double quotes (to include spaces)

Common Parameters: – object_type (mandatory) → "conversations" or "contacts" (specifies which API to call) – q/query → free-text search across key fields – created_at/updated_at → timestamp filters (YYYY-MM-DD or Unix timestamp) – limit → max results (default 10, max 150) – starting_after → pagination cursor

CONVERSATION SEARCH (object_type

): Supported fields: – id → conversation ID – state → conversation state ("open", "closed", "snoozed") – priority → conversation priority ("priority", "not_priority") – source_type → conversation source type ("conversation", "email", "facebook", "twitter", etc.) – source_author_name → name of the message author – source_author_email → email of the message author – source_subject → subject line of the conversation – source_body → body content of the conversation – contact_ids → contact IDs associated with the conversation – statistics_time_to_assignment → time to assignment in seconds – statistics_time_to_admin_reply → time to admin reply in seconds – statistics_time_to_first_close → time to first close in seconds

CONTACT SEARCH (object_type

): Supported fields: – id → contact ID – name → contact name – email → contact email address – email_domain → email domain – phone → contact phone number – role → contact role ("user", "lead") – custom_attributes.* → any custom attribute field (e.g., custom_attributes.company)

EXAMPLES:

user: show me recent conversations query: object_type

created_at:gt:1735689600

user: find open conversations from email query: object_type

state source_type

user: search for conversations from support emails
query: object_type

source_author_email:contains:"@support"

user: find conversations with slow response times query: object_type

statistics_time_to_admin_reply:gt:3600

user: find conversations about billing query: object_type

source_subject:contains:"billing"

user: find conversations mentioning refund query: object_type

source_body:contains:"refund"

user: find contacts named John query: object_type

name:"John"

user: find contacts from example.com domain query: object_type

email_domain:"example.com"

user: find contacts with specific custom attribute query: object_type

custom_attributes.plan_status:"active"

user: recent contact activity query: object_type

updated_at:gt:1735689600 limit:50

user: find conversations for a specific contact query: object_type

contact_ids:in

Unsupported features: • Complex boolean logic beyond simple AND/OR • Fuzzy matching or proximity searches
• Aggregations or analytics queries • Direct conversation content search (use source fields instead) • Real-time or streaming results