Gmail and Linkeddit in Claude: competitor price alerts and a weekly digest drafted for you

The Gmail connector is the mailbox side. Its listing shows 29 tools: 6 reads, 11 writes and 12 the listing does not classify. It can search threads, read a thread, create and update drafts, send a message, and manage labels and filters. It has no view of what competitors shipped this week or what the answer engines say about your category.

Linkeddit is the data side. Compete tracks competitor moves with a priority on each, and Answer Radar records which brands the five engines name and recommend. Both come with one plan at $60 a month. Linkeddit writes no advice and sends no email, so the customer's own assistant decides what belongs in the message.

The pain is clear in how sellers describe it. "It's incredibly manual and I often miss their flash sales," said an ecommerce store owner on Reddit. Linkeddit finds and dates the move, and Claude drafts the Gmail message about it for you to review.

Save a draft. The Gmail connector lists create_draft and send_message as separate tools, which lets you split writing from sending. A competitor email can carry a misread changelog or a wrong price, and a draft is where you catch it.

Agenta's competitor digest tutorial shows the risk the other way: with its permission policy left on Allow all, its agent sends the email without asking, and approving each send means changing the Gmail permission to Ask for write and delete. The prompts on these pages call only create_draft.

No. Claude works when you start it, so a weekly email happens in one of two ways: you run the same saved prompt each week, or a scheduler you already use starts a Claude session. Neither needs a new Linkeddit feature, and these pages do not pretend otherwise.

Linkeddit's side does run on its own clock. On Linkeddit's test project, all five competitor monitors are set to weekly, each with a next run of 2026-11-04. Trackers such as Kuse and TinyCommand run daily and email only when a price changes. If you need that, use one. If a weekly email is enough, this workflow works.

The first is a weekly competitor intelligence digest: one email with the headline change, where an engine named a competitor instead of you, and competitor moves by priority. It can also check whether a published change moved the answers, and it doubles as a one-off competitor brief by email. The second is price change alerts: the week's pricing moves and high priority signals, filtered so a quiet week stays quiet. Each guide has an exact prompt, the steps and a measured read-only run.

Claude reads Gmail through your own sign-in, and search_threads and get_thread can open any thread the account can see. Use a mailbox whose contents you are comfortable having Claude read, and tell it exactly which threads it may search, for example last week's digest only.

Then read the draft. Check each price and each source link, and look for a claim the data does not support. On the test project, the competitor brief returned empty and all three recent audit runs finished partial. A good email says that instead of covering it.