Normalized message format with text, AST, author, and metadata.
Incoming messages are normalized across all platforms into a consistent Message object.
import { Message } from "chat";How isMe works
Each adapter detects whether a message came from the bot itself. The detection logic varies by platform:
| Platform | Detection method |
|---|---|
| Slack | Checks event.user === botUserId (primary), then event.bot_id === botId (for bot_message subtypes). Both IDs are fetched during initialization via auth.test. |
| Teams | Checks activity.from.id === appId (exact match), then checks if activity.from.id ends with :{appId} (handles 28:{appId} format). |
| Google Chat | Checks message.sender.name === botUserId. The bot user ID is learned dynamically from message annotations when the bot is first @-mentioned. |
All adapters return false if the bot ID isn't known yet. This is a safe default that prevents the bot from ignoring messages it should process.
Links found in incoming messages are extracted and exposed as LinkPreview objects. On platforms that support it (currently Slack), links pointing to other chat messages include a fetchMessage() callback to retrieve the full linked message.
When using toAiMessages(), link metadata is automatically appended to the message content. Embedded message links are labeled as [Embedded message: ...] so the AI model understands the context.
Platform support
| Platform | Link extraction | fetchMessage() |
|---|---|---|
| Slack | URLs from rich_text blocks or <url> text patterns | Slack message links (*.slack.com/archives/...) |
| Others | Not yet — links is always [] | — |
Returned by message.subject on platforms with parent resources. See Message Subject for usage.
Messages can be serialized for workflow engines and external systems.
// Serialize
const json = message.toJSON();
// Deserialize
const restored = Message.fromJSON(json);The serialized format converts Date fields to ISO strings and omits non-serializable fields like data buffers and fetchData functions. The fetchMetadata field is preserved so that adapters can reconstruct fetchData when the message is rehydrated from a queue.