Linq
Bots that text over iMessage and SMS through Linq, in DMs and group chats, with media in both directions and native tapback reactions. Maps Linq chats to the Chat SDK thread, message, and reaction model.
Create a new bot
Scaffold a Next.js bot with the Linq adapter using create-chat-sdk:
pnpm create chat-sdk@latest my-bot --adapter linq memory -yThe generated app uses the Memory state adapter for local development. To add the adapter to an existing app, start at Install.
Install
pnpm add @linqapp/chat-sdk-adapterQuick start
The adapter maps a Linq chat to a Chat SDK thread, a text to a message, and an iMessage tapback to a reaction, so subscriptions, handlers, posts, and reactions work as they do with any other adapter.
Platform setup
- Create a Linq account and copy your API key. For testing, the Linq CLI provisions a sandbox number:
linq signup --phone <your cell>. - Create a webhook subscription that points at the route forwarding to
bot.webhooks.linq(see Webhooks), and subscribe to:message.receivedreaction.addedreaction.removed
- Copy the signing secret returned by the subscription into
signingSecret.
Configuration
| Prop | Type | Description |
|---|---|---|
apiKey? | string | Linq API key for outbound API calls. |
signingSecret? | string | Webhook signing secret. Inbound requests are verified with HMAC-SHA256 over `{timestamp}.{body}` with replay protection. |
baseURL? | string | Override the Linq API base URL (e.g. a sandbox host). |
Webhooks
The adapter handles these Linq webhook events:
| Event | Role |
|---|---|
message.received | Drives Chat SDK message processing |
reaction.added | Drives reaction handlers |
reaction.removed | Drives reaction handlers |
The adapter acknowledges other event types with a 200 and ignores them. Forward webhook requests to bot.webhooks.linq:
The adapter verifies each request's HMAC-SHA256 signature and timestamp before dispatch, and returns 401 for an invalid or stale signature. Passing waitUntil lets work continue after the response is sent in serverless environments such as Vercel.
Message format
iMessage has no markdown, and Linq delivers message text as-is, so the adapter renders outbound markdown to plain text. Inbound text is parsed to the Chat SDK AST, with URLs surfaced as link previews.
Reactions
Standard iMessage tapbacks map to normalized Chat SDK emoji in both directions:
| Linq tapback | Chat SDK emoji |
|---|---|
like | thumbs_up |
dislike | thumbs_down |
love | heart |
laugh | laugh |
emphasize | exclamation |
question | question |
Custom emoji reactions go through the default emoji resolver, so 👍 becomes thumbs_up, and anything the resolver can't map is passed through as the raw emoji. Sticker reactions have no Chat SDK equivalent and are skipped.
Attachments
Inbound media (images, audio, files) arrives as Chat SDK attachments with downloadable data. Outbound attachments and files are sent as Linq media parts: a public HTTPS URL under 10 MB is sent by reference, while raw bytes, non-HTTPS URLs, and files up to 100 MB are pre-uploaded. Messages can be media-only.
Thread IDs
Thread IDs are stable and always take the form linq:{chatId}, so a conversation maps to the same Chat SDK thread whether it first arrives via webhook or API.
encodeThreadId
decodeThreadId
The adapter tracks whether a chat is a group or a DM from webhook payloads, so the thread ID doesn't carry it. Legacy linq:{chatId}:group and linq:{chatId}:dm IDs still decode.
Feature support
Messaging
| Feature | Supported |
|---|---|
| Post message | |
| Message replies | |
| Edit message | Text, first part |
| Delete message | |
| File uploads | Images, audio, files |
| Streaming | Buffered |
| Scheduled messages |
Rich content
| Feature | Supported |
|---|---|
| Card format | |
| Buttons | |
| Link buttons | |
| Select menus | |
| Tables | |
| Charts | |
| Fields | |
| Images in cards | |
| Modals |
Conversations
| Feature | Supported |
|---|---|
| Slash commands | |
| Mentions | |
| Add reactions | Tapbacks |
| Remove reactions | Tapbacks |
| Typing indicator | DMs only |
| Mark as read | |
| Message edit events | |
| Message delete events | |
| DMs | |
| Ephemeral messages | |
| User lookup | |
| Parent subject | |
| Native client | |
| Custom API endpoint |
Message history
| Feature | Supported |
|---|---|
| Fetch messages | |
| Fetch single message | |
| Fetch thread info | |
| Fetch channel messages | |
| List threads | |
| Fetch channel info | |
| Post channel message |
Resources
- Adapter source and README
- Example app: one AI bot running across Linq, Telegram, and WhatsApp from a single set of handlers.