Bridge KitA workbench for message tools
Menu

Client-specific bridge / SOURCE-BASED REVIEW

Linq Claude Code channel : receive and answer business messages inside Claude Code

Linq’s official channel plugin brings iMessage events into Claude Code and supplies messaging actions. It is a documented path for that client, with pairing and polling behavior that deserve their own evaluation.

By Bridge Kit editorial · Published · Updated

This update revises the setup and decision guidance below. It is based on public documents, not a connected-account test.

Repository files retrieved November 9, 2026; its head was unchanged November 10. API pricing was retrieved November 10. Original publication and earlier source records are retained.

Linq’s official channel has a documented client host, pairing and runtime setup.
Linq’s official channel has a documented client host, pairing and runtime setup.

OUR TAKE

Receive and answer business messages inside Claude Code

Linq’s official channel plugin brings iMessage events into Claude Code and supplies messaging actions. It is a documented path for that client, with pairing and polling behavior that deserve their own evaluation.

A channel has a particular host

The repository specifies Claude Code version 2.1.80 or later and a plugin-oriented setup. This entry belongs in a messaging bridge shortlist because it delivers incoming context and actions to that host.

A team using another assistant should evaluate Linq’s API or a separately documented connector. A similar tool protocol does not make this channel universally interchangeable.

This channel handles arrivals while running, not archive search. That limitation describes the plugin, not the whole Linq API.

Sources: Pinned README

Pairing is an operational decision

The guide describes a pairing policy for unknown senders and an allowlist. That helps distinguish a recognized participant from a new message arriving at the line, but the team must still decide who can authorize access.

The published polling interval defaults to three seconds, with configuration and a webhook listener path also documented. Those are implementation settings, not our measured response latency.

Protect the surrounding workspace

Messages and downloaded photos enter the client’s working context. Review how that client handles files, model requests and approval for tools before giving it customer content.

Use the plugin for a client-centered workflow only if the host, credentials and ongoing process ownership suit the team. Request the production API terms separately from general Linq app pricing.

The published API starting rate does not establish per-line billing or included production usage; confirm both separately.

Decide what happens between sessions

For a channel-centered workflow, the important question is what the assistant knows at the moment it is asked to answer. State which conversation details must be supplied by a person and which are expected to arrive during the session. If earlier context is needed, make its absence explicit rather than allowing a plausible reconstruction.

Assign responsibility for the running client and the handoff when that session is unavailable. A small personal workflow and a shared support queue can have very different expectations about continuity. Write those expectations down before deciding whether this client-specific approach is the right fit.

Keep the plugin setup decision separate from the commercial API purchase. Ask for a quote that explains the quantity being billed and the usage the intended workload needs. A published starting amount is useful for opening that discussion, but it does not answer the scope of a particular order.

The decision in one sentence

Choose Linq Claude Code channel when receive and answer business messages inside claude code matches the task and its documented limits fit your client.

Read the primary sources

These are the provider’s own descriptions. Prices and product claims are dated snapshots, and performance claims are not our test results.