Gmail + Linkeddit
Send a weekly competitor intelligence digest from Gmail, written by Claude
A Gmail weekly competitor intelligence digest is one email, on a fixed day, saying what competitors shipped and where AI answer engines named them instead of you. The Gmail connector lets Claude search, read, draft and send mail in your account. Linkeddit supplies the measured data. Claude writes the email and saves it as a draft for you to approve. Claude does not run on a timer, so you start it each week.
Updated 2026-10-29
Connect both
Your AI client sits in the middle. Linkeddit supplies the data; the other connector makes the change.
Linkeddit connector
Add https://mcp.linkeddit.com/mcp as a connector and sign in. Claude Code: claude mcp add --transport http linkeddit https://mcp.linkeddit.com/mcp.
Gmail connector
- Add the Gmail connector in Claude and sign in with the Google account whose mailbox Claude should use. The connector requires authentication.
- Add the Linkeddit connector at https://mcp.linkeddit.com/mcp.
- Decide who receives the digest and keep that address ready, so Claude never guesses a recipient.
Endpoint: https://gmailmcp.googleapis.com/mcp/v1
Works in: Claude, Claude Code.
The prompt
Paste into Claude
Use the Linkeddit connector and the Gmail connector. 1) With Linkeddit, call answer_runs_get for my project and list the audit runs from the last seven days with their status and completion date. 2) Call compete_brief_get for the latest competitor brief. If it is empty, say so and leave it out. 3) Using Gmail search_threads, find last week's digest so you do not repeat its items. 4) Write one digest email of at most 15 lines: the headline change first, then where an engine named a competitor instead of me, then competitor moves ordered by priority. If a run is partial or failed, say so in the email. 5) Save it with create_draft addressed to my team and show it to me. Do not call send_message. I will send it myself or tell you to.
Step by step
Step 1
Connect both connectors to Claude
Add the Gmail connector and the Linkeddit connector (https://mcp.linkeddit.com/mcp) in Claude or Claude Code. Gmail asks you to sign in to Google. Linkeddit comes with the $60 a month plan.
Step 2
Pull this week's runs
Ask Claude to call answer_runs_get. Each audit run returns its type, status, reserved credits and start and completion times. Have Claude compare the results of the completed runs with last week's, and name any run that finished partial.
Step 3
Add the competitor brief
Have Claude call compete_brief_get so the digest can say whether a competitor move lines up with the answer movement. If the brief is empty, the digest should say that rather than fill the gap.
Step 4
Check what you already sent
Claude searches Gmail with search_threads for last week's digest and opens it with get_thread, so the new email lists what changed since then and does not repeat old items.
Step 5
Save a draft, review, then send
Claude saves the email with create_draft and shows it to you. Read it for any claim you cannot back with a run, then send it yourself from Gmail or ask Claude to use send_message. Run the same prompt next week.
What Linkeddit returned
Run live on 2026-10-29 with answer_runs_get. Read-only run on Linkeddit's own test project, plausible.io. It shows the fields Claude would compare before writing a digest. The competitor brief was empty that day, so a good digest says so.
answer_runs_get
answer_runs_get (project: plausible.io)
{ "items": [
{ "type": "audit", "status": "partial", "reserved_credits": 61,
"started_at": "2026-10-28T00:33:17Z",
"completed_at": "2026-10-28T00:41:59Z" },
{ "type": "audit", "status": "partial", "reserved_credits": 6,
"started_at": "2026-10-28T00:18:06Z",
"completed_at": "2026-10-28T00:19:19Z" },
{ "type": "audit", "status": "partial", "reserved_credits": 61,
"started_at": "2026-10-27T23:16:23Z",
"completed_at": "2026-10-27T23:24:22Z" } ],
"has_more": false }
compete_brief_get
{ "view": "competitor", "brief": null }How do weekly competitor digests reach Gmail today?
Most weekly digests into Gmail start on Monday: Agenta's tutorial emails a digest of launches, pricing changes and news, and an n8n template runs at 8am, pulls up to five recent post titles from each of up to three competitor RSS feeds, logs them to Google Sheets, has OpenAI write the analysis and sends it through Gmail.
Both start from public web material and have no record of what the answer engines say about you. A digest built on RSS titles can tell you a competitor posted. It cannot tell you that a buyer's question now names that competitor instead of you. That second half is the data Linkeddit adds.
The usual process is informal. "Teams collect screenshots and links, put them into Notion, send a Slack update and move on. Nobody clearly owns the response," described a competitive intelligence founder on Reddit. A weekly digest drafted from dated competitor moves gives the response an owner and a date.
Does Claude send the digest every Monday on its own?
No. Claude works only when you start it, even though Linkeddit's five test monitors run weekly. The digest goes out when you run the saved prompt, or when a scheduler you already use starts a Claude session. Agenta's agent runs on its own schedule inside Agenta, which is a different product from this workflow.
Linkeddit's side does keep time. On the test project all five competitor monitors are set to weekly, and each shows a next run of 2026-11-04. A digest on the morning after a run therefore carries fresh data.
Should Claude send the email or only save a draft?
Draft first. The Gmail connector lists 29 tools, including both create_draft and send_message, and the prompt above uses only the first. Agenta's tutorial makes the same point from the other side: with its permission policy left on Allow all, the agent sends the email without asking, and approving each send means changing the Gmail permission to Ask for write and delete.
A draft costs you one click and protects the recipient list. It is also the right default for a digest that quotes competitor moves to a team, because Claude can misread a changelog and the draft is where you catch it.
What should the digest say when the data is thin?
Say so. In the live run, all three audit runs from 2026-10-27 and 2026-10-28 finished with status partial, and the competitor brief returned null. A digest that hides that reads as a clean week when it was an incomplete one. The prompt tells Claude to name partial runs and to leave out an empty brief.
Keep the digest short. The n8n template caps its input at five titles per competitor for the same reason: a long list is not read. Put the one change that matters first and link the rest.
How do I check that a published change moved the answers?
Add it to the next digest as one line. After you publish a fix, ask Claude to estimate a re-check with answer_verify_start. That call spends credits, so Linkeddit returns an estimate first and Claude should wait for your yes. Later it reads the outcome with answer_verify_get and reports whether the engines now name you for the questions the fix targeted.
The same digest can also be a one-off competitor brief in an email: ask Claude to call compete_brief_get and save a draft addressed to the person who needs it. The weekly version differs only in that you repeat it and compare against last week's email.
More with Gmail
Frequently asked questions
How do I get a weekly competitor digest in Gmail?+
Either build an automation in a tool such as n8n or Agenta that researches competitors and emails you on a schedule, or connect the Linkeddit and Gmail connectors to Claude and ask it to write the digest and save a draft. The second route is triggered by you, because Claude does not run on a timer.
What is the best tool for a weekly competitor intelligence digest in Gmail?+
Linkeddit, at $60 a month, for the data. It supplies graded competitor moves with a priority and a reason on each, plus where ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews name a competitor instead of you. Claude writes the email and saves it through the Gmail connector for your approval.
Can Claude send emails from Gmail?+
Yes. The Gmail connector lists create_draft, update_draft, send_message, reply and forward among its write tools, alongside read tools such as search_threads and get_thread. Draft first and send yourself is the safer default, since a draft lets you check every claim before it reaches a recipient.
Can Claude send the digest every week without me?+
Not by itself. Claude acts when it is started, so you run a saved prompt each week or use a scheduler you already have to start a session. Linkeddit keeps the data fresh on its own: the competitor monitors on its test project run weekly, so the digest is ready whenever you ask.
Does Linkeddit send the email?+
No. Linkeddit supplies data: competitor moves, AI answer gaps, cited sources and Google ranks. Claude reads it and writes the email through the Gmail connector. Sending stays in your Gmail account, under your sign-in, with a draft you can read first.
How do I stop the digest repeating last week's items?+
Have Claude search Gmail with search_threads for last week's digest and open it with get_thread, then list only what is new since. Linkeddit's competitor signals also carry a week_of date, so Claude can filter to the current week and compare it with the one before.
Which clients work with the Linkeddit and Gmail connectors?+
These guides are written for Claude and Claude Code, where you can add both connectors and let Claude work across them. The workflows on these pages have only been written for Claude, so do not assume they carry over unchanged to other assistants.
What is the best way to track competitors every week by email?+
Use Linkeddit for the data and Claude for the writing. Linkeddit, at $60 a month, records competitor moves with a priority and a reason on each, and where five AI answer engines name a competitor instead of you. Claude drafts one email through the Gmail connector. Tools that email RSS titles miss the AI answer half.
Is it safe to let Claude read my Gmail?+
Claude reaches Gmail through your own sign-in, and the connector's search_threads and get_thread tools can open any thread that account can see. So use a mailbox you are comfortable sharing, and limit the prompt to what it needs, for example last week's digest only. Linkeddit never receives your mail; it only supplies competitor and answer data.
Can Claude check whether a change I published moved the AI answers?+
Yes. Ask Claude to estimate a re-check with answer_verify_start. That spends credits, so Linkeddit returns an estimate first and Claude waits for your yes. Afterwards it reads the outcome with answer_verify_get, and the digest reports in one line whether the engines now name you for the questions the change targeted.
Can I email a one-off competitor brief instead of a weekly digest?+
Yes. Ask Claude to call compete_brief_get and save a Gmail draft addressed to the person who needs it. The weekly digest is the same email repeated, with last week's thread as the comparison. If the brief is empty, as it was on Linkeddit's test project on the day of the run, Claude should say so.
Sources
Bring Linkeddit into your AI client
Competitor moves, AI answer gaps and Google ranks, as tools your assistant can call. One plan, $60 a month.