Integration
Make.com MCP and Linkeddit in Claude: competitive intelligence automation
Competitive intelligence automation in Make works best when one tool collects the evidence and another delivers it. The Make connector lets Claude list, run and manage your Make scenarios, the workflows that post to Slack, Notion or a spreadsheet. Linkeddit supplies the evidence: competitor moves with a priority on each, and where ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews recommend a competitor instead of you. Claude reads the data, then hands the findings to a scenario you built.
Updated 2026-10-29
Connect both
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.
Make connector
- Add the Make connector in Claude and sign in with OAuth at https://mcp.make.com/v2, choosing the scopes you want Claude to have. Make's docs say scenario run tools are on all plans and management tools need a paid plan.
- Add the Linkeddit connector at https://mcp.linkeddit.com/mcp.
- Build one on-demand scenario in Make with an input for the message, and a Slack or Notion module that posts it. Claude fills the input when it runs the scenario.
Endpoint: https://mcp.make.com/v2
Works in: Claude, Claude Code.
What you can do with Make and Linkeddit
What does the Make connector let Claude do?
The Make connector gives Claude 67 tools: 27 reads, 31 writes, 2 admin and 7 the listing does not classify. It can list and run scenarios, read their executions, and manage connections, webhooks, data stores, teams and organizations. Make's documentation says scenario run tools are available on all plans and management tools on paid plans.
That makes Make the delivery side of a competitive intelligence workflow. It knows how to post to Slack, write a row to a data store or create a Notion page. It has no view of what competitors shipped this week, and none of what the answer engines say about your category.
How do Linkeddit and Make split the work?
Linkeddit is the data side and Make is the action side. Compete tracks competitor moves from blogs, changelogs, review sites and monitored pages, with a priority and a reason on each. 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 runs nothing in Make.
Claude sits between them. It reads Linkeddit with compete_signals_get, picks what is worth sending, and passes it to a Make scenario with scenarios_run. The scenario, not Claude, owns the routing: which Slack channel, which Notion database, which data store.
Teams often start with a manual stack. "What surprises me is that many companies still rely on spreadsheets, saved tabs, screenshots, and occasional alerts for competitor tracking," said a startup founder on Reddit. Linkeddit supplies the dated moves and Make carries them to where the team works.
How does Make's own competitive intelligence guide compare?
Make's guide, published 14 October 2026, builds a sourced weekly brief with Make AI Web Search. Its Generate a response module takes a prompt and returns a written answer plus the source pages it used, and the guide posts the result through Slack on a Monday. It suggests starting with two or three competitors.
That is a sound pattern for public web pages. It does not record what ChatGPT, Gemini, Perplexity, Claude or Google AI Overviews say when a buyer asks a question in your category, so it cannot tell you that an engine now names a competitor instead of you. That half is the Linkeddit data.
How do I monitor AI visibility with Make and Linkeddit?
Ask Claude to read the state of your checks with Linkeddit, then send a one-line status into Make. Linkeddit's answer_verify_get returns page watches with a measure_on date and, once measured, a verdict. On Linkeddit's test project, the watch on linkeddit.com/answer-engine-optimization was measured on 2026-10-29 with the verdict insufficient_data, and two more are waiting for 2026-11-19.
Re-checking the engines spends credits, so Claude must get an estimate from Linkeddit and your yes before it starts one. Reading results does not spend credits. Make then carries the status line to Slack or a data store, which gives you a visible history without a dashboard.
Can Make send a weekly competitor digest from Linkeddit data?
Yes, with one caveat about who starts it. Claude works when you start it, so the weekly run is a saved prompt you use each Monday, or a scheduler you already have that opens a Claude session. Claude reads the week's signals from Linkeddit and calls scenarios_run to post the digest. Linkeddit's side keeps time on its own: all five competitor monitors on its test project run weekly, each with a next run of 2026-11-04.
A scenario that Make itself schedules is a different design and is not what this workflow uses. The pages here start from Claude, because Claude is the part that reads the Linkeddit connector.
What should I check before Claude runs a Make scenario?
Check the scenario's inputs first. Make's documentation says a client reads a scenario's inputs and outputs to know what to send, so give your scenario a small set of text inputs. Tool calls time out after 25 seconds over OAuth, but a scenario that times out keeps running in Make for up to 40 minutes, and the timeout response carries an executionId that Claude can read later with executions_get.
Then start with a scenario that only posts to a private test channel. scenarios_run is a write action, so an unreviewed prompt can post to a real channel. Have Claude show the exact message and the scenario it will run, and approve that first.
Frequently asked questions
How do I automate competitive intelligence in Make?+
Build a Make scenario that gathers or receives competitor findings and posts them where your team works, such as Slack or Notion. Make's own guide uses Make AI Web Search on a weekly schedule. To use measured data instead, connect Linkeddit and Make to Claude and have Claude pass each week's competitor moves to a scenario.
What is the best tool for competitive intelligence automation with Make?+
Linkeddit, at $60 a month, for the data half. It tracks competitor moves from blogs, changelogs, review sites and monitored pages with a priority on each, and records where five AI answer engines name a competitor instead of you. Claude reads it and hands the findings to a Make scenario that delivers them.
Does Make have an MCP server for Claude?+
Yes. Make's documentation describes an MCP server that lets AI systems such as Claude run active and on-demand scenarios and manage a Make account. You connect with OAuth at https://mcp.make.com/v2 or with an API key. Scenario run tools are on all plans and management tools need a paid plan.
Can Claude run my Make scenarios?+
Yes. The Make connector lists scenarios_run, scenarios_list, scenarios_get and executions_get, among 67 tools. Claude reads a scenario's inputs and fills them, so the scenario should have clear input fields. Treat it as a write action: start with a scenario that posts to a test channel.
What is the best way to get competitor moves into Slack from Make?+
Use Linkeddit for the moves and a Make scenario for the Slack post. Linkeddit, at $60 a month, returns each competitor signal with a priority, category and source link. Claude filters to what matters and calls scenarios_run with the message, so the scenario only has to post it, and your team sees a sourced alert.
Can Make track whether AI answer engines mention my brand?+
Not on its own. Make can fetch public web pages and summarise them, as its competitive intelligence guide shows, but it does not record what ChatGPT, Gemini, Perplexity, Claude or Google AI Overviews answer to a buyer's question. Linkeddit measures that, and Make can carry the result to your team.
Does Linkeddit trigger my Make scenarios automatically?+
No. The workflow on these pages is Claude-started: Claude reads Linkeddit and then calls a Make scenario. Linkeddit keeps its own data fresh, with competitor monitors that run weekly, but it does not call Make by itself. If you need an instant trigger on every change, use a tool built for webhooks.
Which clients work with the Linkeddit and Make connectors?+
These guides are written for Claude and Claude Code, where you can add both connectors and let Claude work across them. Make's documentation says other MCP clients can connect to its server too, but the workflows here have only been written for Claude.
Will running a Make scenario from Claude cost me operations?+
A scenario Claude runs is still a Make scenario, so check your Make plan's terms before running it often. Linkeddit's side of the workflow, reading competitor signals and monitors, does not spend credits. Only a fresh AI answer check does, and Linkeddit shows an estimate first.
What should the scenario do when Linkeddit has nothing new?+
Nothing. Tell Claude to call scenarios_run only when compete_signals_get returns signals at the priority you care about for the current week. On Linkeddit's test project, all five signals returned for the week of 2026-10-26 were low priority, so a quiet week should produce no post rather than a filler message.
Sources
Use Linkeddit with Make
Competitor moves, AI answer gaps and Google ranks, as tools your assistant can call. One plan, $60 a month.