[Integrations](https://spiral.ai/integrations) › [Notion](https://spiral.ai/integrations/notion) › [LinkedIn comment reactions](https://spiral.ai/integrations/notion/linkedin-comment-reactions)

# How to Use LinkedIn comment reactions in Notion

Returns reaction records for one LinkedIn comment, including reaction types and actor details. Use it to measure the response to a specific answer or objection within a discussion.

|  |  |
| --- | --- |
| Model | LinkedIn comment reactions |
| Available through | Alexandria |
| Category | Social Media |
| Price | Up to $0.0034918 per run. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with LinkedIn comment reactions in Notion

- Every Monday at 9am: use LinkedIn comment reactions to look this up and give me the result as a table.
- Pull the latest numbers from LinkedIn comment reactions and tell me what changed since last week.
- Check LinkedIn comment reactions and summarize what you find in three bullet points.
- Pull the newest data from LinkedIn comment reactions and give me the result as a table.
- Check LinkedIn comment reactions every morning and tell me only when something changed.

## How to set up LinkedIn comment reactions in Notion

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send Notion this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Allow custom MCP servers**: A workspace owner opens Settings › Connections, then the Manage tab, and turns on Enable custom MCP servers. Where members may install only approved connections, also add Spiral under Approved connections › Add approved connection › Custom MCP server with the URL below.

2. **Add Spiral to a custom agent**: Open the custom agent (or create one), then Settings › Tools & Access › Add connection › Custom MCP server. Paste this URL, name it Spiral, keep OAuth and click Connect.

```text
https://api.spiral.ai/mcp
```

3. **Sign in to Spiral and approve**: Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Notion never sees it, and you can remove it under Settings › Connected apps in the console.

4. **Run LinkedIn comment reactions in a workflow step**: Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds LinkedIn comment reactions, prices it and runs it each time the step fires.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run LinkedIn comment reactions**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "harvestapi/linkedin/comment-reactions",
    "input": {
      "url": "<url>"
    }
  }'
```

Then paste one of the prompts above: Notion finds LinkedIn comment reactions on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/notion

## LinkedIn comment reactions tools and prices

- [HarvestAPI · LinkedIn get reactions of linkedin post comment](https://spiral.ai/tools/alexandria/harvestapi/linkedin/comment-reactions) (Alexandria): Up to $0.0034918 per run.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| page |  | — | Page number for pagination. Default is 1. |

## What can you do with LinkedIn comment reactions in Notion?

Produce a recurring brief on LinkedIn product announcements and the public discussion around them. A scheduled agent can compare newly returned posts, comments, or reaction records with previous results and report changes.

### Review a product launch

Combine company announcements, public creator posts, and topic searches into a launch brief. Examine post details, comments, replies, and reaction mixes; use creators' published comments and reacted-to post IDs to find additional discussions.

### Plan an editorial calendar

Research company publishing feeds and public creators' posts, comments, and reacted-to posts for topic ideas. Read the underlying posts and discussions, then compare post and comment reactions to select questions worth answering.

### Prepare a conference debrief

Find event posts through organizer feeds, public speakers' publishing activity, and keyword searches. Follow comments, replies, and reacted-to post IDs to collect discussion points, then summarize reaction types at both post and comment level.

### Build an industry discussion brief

Collect company posts and public creators' published contributions around a defined industry topic. Use reaction records to identify associated posts and calculate response mixes, then read post details and comment threads for the substance behind those responses.

### Compare campaign responses

Compare the content and reported engagement of selected company and public creator posts. Calculate reaction mixes for the posts and for specific comments addressing campaign messages.

### Prioritize public questions for a response

Review comments and reply threads beneath a company's announcements. Compare reactions on individual questions with reactions on the post to choose which issues deserve a public explanation.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Notion guides](https://spiral.ai/integrations/notion)

## LinkedIn comment reactions in other agents

- [Amp](https://spiral.ai/integrations/amp/linkedin-comment-reactions)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/linkedin-comment-reactions)
- [Claude](https://spiral.ai/integrations/claude-desktop/linkedin-comment-reactions)
- [Claude Code](https://spiral.ai/integrations/claude-code/linkedin-comment-reactions)
- [Cline](https://spiral.ai/integrations/cline/linkedin-comment-reactions)
- [Codex](https://spiral.ai/integrations/codex/linkedin-comment-reactions)
- [Cursor](https://spiral.ai/integrations/cursor/linkedin-comment-reactions)
- [Devin](https://spiral.ai/integrations/devin/linkedin-comment-reactions)
- [dots](https://spiral.ai/integrations/dots/linkedin-comment-reactions)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/linkedin-comment-reactions)
- [Gemini](https://spiral.ai/integrations/gemini/linkedin-comment-reactions)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/linkedin-comment-reactions)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/linkedin-comment-reactions)
- [goose](https://spiral.ai/integrations/goose/linkedin-comment-reactions)
- [Grok](https://spiral.ai/integrations/grok/linkedin-comment-reactions)
- [Grok Build](https://spiral.ai/integrations/grok-build/linkedin-comment-reactions)
- [Hermes](https://spiral.ai/integrations/hermes/linkedin-comment-reactions)
- [Instinct](https://spiral.ai/integrations/instinct/linkedin-comment-reactions)
- [Manus](https://spiral.ai/integrations/manus/linkedin-comment-reactions)
- [Muse](https://spiral.ai/integrations/muse/linkedin-comment-reactions)
- [Muse Code](https://spiral.ai/integrations/muse-code/linkedin-comment-reactions)
- [n8n](https://spiral.ai/integrations/n8n/linkedin-comment-reactions)
- [OpenClaw](https://spiral.ai/integrations/openclaw/linkedin-comment-reactions)
- [opencode](https://spiral.ai/integrations/opencode/linkedin-comment-reactions)
- [Perplexity](https://spiral.ai/integrations/perplexity/linkedin-comment-reactions)
- [Raycast](https://spiral.ai/integrations/raycast/linkedin-comment-reactions)
- [VS Code](https://spiral.ai/integrations/vscode/linkedin-comment-reactions)
- [Windsurf](https://spiral.ai/integrations/windsurf/linkedin-comment-reactions)
- [Zapier](https://spiral.ai/integrations/zapier/linkedin-comment-reactions)

## More Notion guides

- [LinkedIn ad search](https://spiral.ai/integrations/notion/linkedin-ad-search)
- [LinkedIn comment replies](https://spiral.ai/integrations/notion/linkedin-comment-replies)
- [LinkedIn ad details](https://spiral.ai/integrations/notion/linkedin-ad-details)
- [LinkedIn company posts](https://spiral.ai/integrations/notion/linkedin-company-posts)
- [LinkedIn Web Get post comments](https://spiral.ai/integrations/notion/linkedin-web-get-post-comments)
- [LinkedIn company profile](https://spiral.ai/integrations/notion/linkedin-company-profile)

## Questions about LinkedIn comment reactions in Notion

**Can Notion use LinkedIn comment reactions?**

Yes. Add Spiral to Notion as an MCP server, and Notion can find and run LinkedIn comment reactions like any built-in tool.

**How much does LinkedIn comment reactions cost in Notion?**

Up to $0.0034918 per run. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Notion plan is separate.

**Do I need an Alexandria account to use LinkedIn comment reactions in Notion?**

No. Spiral runs LinkedIn comment reactions on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up LinkedIn comment reactions in Notion?**

About two minutes: allow custom MCP servers, then add Spiral to a custom agent, then sign in to Spiral and approve.

**Does Notion wait while LinkedIn comment reactions runs?**

LinkedIn comment reactions runs in the background. Notion starts the run, checks on it and gives you the json when it's ready.

**What information does HarvestAPI cover?**

HarvestAPI describes its data as publicly available web information. That scope does not establish coverage of private LinkedIn messages or restricted discussions.

**How fresh is the LinkedIn data?**

HarvestAPI advertises real-time access to the latest source data. Its website does not state a fixed refresh interval in minutes or hours.

**Is the returned data guaranteed to be complete?**

HarvestAPI's terms exclude warranties of absolute data accuracy, reliability, and completeness. A response therefore carries no guarantee that it represents every LinkedIn post or interaction.

**Can returned data be kept indefinitely?**

HarvestAPI's terms limit storage and caching to the period reasonably necessary for the specific legitimate use. They do not grant an unrestricted retention period.

**What does public mean on LinkedIn?**

LinkedIn says posts shared with Anyone can be visible on or off LinkedIn. Posts shared with Connections only are restricted to the author's first-degree connections.

