Skip to main content
Search threads by meaning or text. Vector search understands intent (“angry customer about shipping”), while regex search matches exact terms. Both return thread summaries your agent can act on.
Semantic vector search requires Business or higher. Regex search is available on all plans as a fallback.

Search threads

Search email threads by semantic meaning

Open in Cursor

Parameters

At least one of inbox_id or domain_id is required.

Response (regex fallback)

When vector search is not available, results come from regex-based text matching on subjects and content:

Search modes

Vector search (semantic)

When configured with Qdrant and Azure OpenAI embeddings, search understands meaning:
  • "angry customer about shipping" matches emails about delivery complaints
  • "pricing questions" matches emails about costs, quotes, and packages
  • "technical integration help" matches API questions, SDK issues, etc.
Vector search returns a score (0–1) indicating semantic similarity.

Regex search (fallback)

When vector search is unavailable, Commune falls back to regex-based matching:
  • Searches subject lines and message content
  • Case-insensitive text matching
  • Works without any additional infrastructure
The search_type field in the response tells you which mode was used.

After searching

Once you have search results, use the thread API to read full conversations:
Semantic vector search is available on Business plans and above and requires additional infrastructure (Qdrant + embedding model).

What’s next?

Threads

Read thread messages and manage triage after searching.

Structured Extraction

Extract structured data from emails to improve search relevance.

Messages

Full message object reference for processing search results.

Capability Matrix

See which features are available across API, SDKs, and MCP.
Last modified on March 19, 2026