# Note Post Comments Scraper (`scrapingmonkey/note-post-comments-scraper`) Actor

Extract public Note article comments with text, authors, dates, likes, reply counts, and available creator reply previews.

- **URL**: https://apify.com/scrapingmonkey/note-post-comments-scraper.md
- **Developed by:** [ScrapingMonkey](https://apify.com/scrapingmonkey) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

**Note Post Comments Scraper** — Extract public Note article comments with text, authors, dates, likes, reply counts, and available creator reply previews. Add supported inputs and start a run to get structured public data without providing a note.com account.

Export root comments on a note.com photography article. Keep comment text, dates, author details and available creator replies for qualitative review.

| At a glance | Details |
|---|---|
| 📥 Input | Enter public Note article URLs or article keys, one per item. Returns root comments, not complete reply trees. Disabled or unavailable comments are skipped without repeated requests. |
| 📤 Output | One comment per success row, with source input retained |
| 📄 Pagination | `pagesPerPost` limits result pages per input, with a default of 1. The source may end sooner. |
| 🔐 Login required | No |
| ⚡ Processing | Up to 5 HTTP requests concurrently with automatic retries |
| 💾 Delivery | One Apify dataset view, useful flat columns and complete nested JSON |

### What the note post comments scraper collects 📊

Extract public Note article comments with text, authors, dates, likes, reply counts, and available creator reply previews.

Data can include:

- Source identity and public links
- Available key, id, post key, post url, post title, text, created at, updated at
- Original input retained with every result
- One consistent success or failed record format

### How to collect comments from note.com 🚀

1. Enter one or more supported inputs in `inputList`.
2. Set the result-page budget for each input.
3. Start the Actor.
4. Open the **Comments** dataset view and review the individual records.
5. Export the dataset or retrieve it from your application.

```json
{
  "inputList": [
    "https://note.com/fuwafuwa_man/n/n8336606d36cd"
  ],
  "pagesPerPost": 1
}
```

`pagesPerPost` limits result pages per input, with a default of 1. The source may end sooner.

### note.com comments data and complete output 📦

| Field | Type | Meaning |
|---|---|---|
| `input` | string | Original submitted input. |
| `status` | string | Result status: success or failed. |
| `type` | string or null | Result entity type. |
| `key` | string or null | Stable Note entity key. |
| `id` | string or null | Numeric source identifier exported as a string. |
| `post_key` | string or null | Post key when exposed by the public response. |
| `post_url` | string or null | Available post URL. |
| `post_title` | string or null | Post title when exposed by the public response. |
| `text` | string or null | Comment text extracted from the public comment body. |
| `created_at` | string or null | Creation time as supplied by the source. |
| `updated_at` | string or null | Update time as supplied by the source. |
| `likes_count` | integer or null | Likes count supplied by the source; absent values remain null. |
| `replies_count` | integer or null | Replies count supplied by the source; absent values remain null. |
| `is_edited` | boolean or null | Is edited when exposed by the public response. |
| `is_root` | boolean or null | Is root when exposed by the public response. |
| `is_creator_liked` | boolean or null | Is creator liked when exposed by the public response. |
| `is_creator_replied` | boolean or null | Is creator replied when exposed by the public response. |
| `user` | object or null | User when exposed by the public response. |
| `user.id` | string or null | Source identifier of this entity, retained as a string. |
| `user.key` | string or null | Source key identifying this entity. |
| `user.username` | string or null | Username when exposed by the public response. |
| `user.name` | string or null | Public name supplied by the source. |
| `user.url` | string or null | Public source URL. |
| `user.description` | string or null | Available public description. |
| `user.profile_image_url` | string or null | Available profile image URL. |
| `user.header_image_url` | string or null | Available header image URL. |
| `user.followers_count` | integer or null | Followers count supplied by the source; absent values remain null. |
| `user.following_count` | integer or null | Following count supplied by the source; absent values remain null. |
| `user.follow_counts_visible` | boolean or null | Follow counts visible when exposed by the public response. |
| `user.is_official` | boolean or null | Is official when exposed by the public response. |
| `to_user` | object or null | To user when exposed by the public response. |
| `to_user.id` | string or null | Source identifier of this entity, retained as a string. |
| `to_user.key` | string or null | Source key identifying this entity. |
| `to_user.username` | string or null | Username when exposed by the public response. |
| `to_user.name` | string or null | Public name supplied by the source. |
| `to_user.url` | string or null | Public source URL. |
| `to_user.description` | string or null | Available public description. |
| `to_user.profile_image_url` | string or null | Available profile image URL. |
| `to_user.header_image_url` | string or null | Available header image URL. |
| `to_user.followers_count` | integer or null | Followers count supplied by the source; absent values remain null. |
| `to_user.following_count` | integer or null | Following count supplied by the source; absent values remain null. |
| `to_user.follow_counts_visible` | boolean or null | Follow counts visible when exposed by the public response. |
| `to_user.is_official` | boolean or null | Is official when exposed by the public response. |
| `latest_creator_reply` | object or null | Latest creator reply preview, when supplied; this is not the full reply thread. |
| `latest_creator_reply.key` | string or null | Source key identifying this entity. |
| `latest_creator_reply.text` | string or null | Public text of this result. |
| `latest_creator_reply.created_at` | string or null | Creation time as supplied by the source. |
| `latest_creator_reply.user` | object or null | User when exposed by the public response. |
| `latest_creator_reply.user.id` | string or null | Source identifier of this entity, retained as a string. |
| `latest_creator_reply.user.key` | string or null | Source key identifying this entity. |
| `latest_creator_reply.user.username` | string or null | Username when exposed by the public response. |
| `latest_creator_reply.user.name` | string or null | Public name supplied by the source. |
| `latest_creator_reply.user.url` | string or null | Public source URL. |
| `latest_creator_reply.user.description` | string or null | Available public description. |
| `latest_creator_reply.user.profile_image_url` | string or null | Available profile image URL. |
| `latest_creator_reply.user.header_image_url` | string or null | Available header image URL. |
| `latest_creator_reply.user.followers_count` | integer or null | Followers count supplied by the source; absent values remain null. |
| `latest_creator_reply.user.following_count` | integer or null | Following count supplied by the source; absent values remain null. |
| `latest_creator_reply.user.follow_counts_visible` | boolean or null | Follow counts visible when exposed by the public response. |
| `latest_creator_reply.user.is_official` | boolean or null | Is official when exposed by the public response. |

Nested arrays and media references stay in their parent record. Downloading source media files is not part of this Actor.

Every top-level output field appears in these complete examples. The success example is normalized from a public response. Long strings and arrays are shortened here; the Actor keeps the complete available values. Values are a snapshot and can change. Nested arrays remain inside their parent result.

Representative success result with every output field (long text and arrays shortened for readability):

```json
{
  "input": "https://note.com/fuwafuwa_man/n/n8336606d36cd",
  "status": "success",
  "type": "comment",
  "key": "ncef2b2668c305",
  "id": null,
  "post_key": "n8336606d36cd",
  "post_url": "https://note.com/fuwafuwa_man/n/n8336606d36cd",
  "post_title": "写真をバババッ",
  "text": "スタイルエグすぎるっす\n脚なげええええ",
  "created_at": "2026-09-04T23:19:21.730+09:00",
  "updated_at": "2026-09-04T23:19:21.730+09:00",
  "likes_count": 0,
  "replies_count": 0,
  "is_edited": false,
  "is_root": true,
  "is_creator_liked": false,
  "is_creator_replied": false,
  "user": {
    "id": null,
    "key": "35ace8425c95c2d54064b60796907c4b",
    "username": "koshirosuper",
    "name": "こうしろう",
    "url": "https://note.com/koshirosuper",
    "description": null,
    "profile_image_url": "https://assets.st-note.com/production/uploads/images/170346878/profile_1eea387a11c08c1787e2a6410d37095d.jpeg?fit=bounds&format=jpeg&quality=85&width=330",
    "header_image_url": null,
    "followers_count": null,
    "following_count": null,
    "follow_counts_visible": null,
    "is_official": null
  },
  "to_user": null,
  "latest_creator_reply": null
}
```

Complete failed result:

```json
{
  "input": "invalid input",
  "status": "failed",
  "type": null,
  "key": null,
  "id": null,
  "post_key": null,
  "post_url": null,
  "post_title": null,
  "text": null,
  "created_at": null,
  "updated_at": null,
  "likes_count": null,
  "replies_count": null,
  "is_edited": null,
  "is_root": null,
  "is_creator_liked": null,
  "is_creator_replied": null,
  "user": null,
  "to_user": null,
  "latest_creator_reply": null
}
```

A failed row preserves `input`, sets `status` to `failed`, and sets every other top-level field to `null`. The run log records the reason. Optional successful fields can be null or empty when note.com does not supply them. Object fields are exposed through useful columns in the single **Comments** view; arrays are not expanded into extra result rows.

### Input requirements and pagination settings ⚙️

| Parameter | Type | Required | Default | Rules |
|---|---|---|---|---|
| `inputList` | array of strings | Yes | None | Enter public Note article URLs or article keys, one per item. Returns root comments, not complete reply trees. Disabled or unavailable comments are skipped without repeated requests. At least `1` item. |
| `pagesPerPost` | integer | No | `1` | Maximum result pages per input. Metadata requests do not count as pages. Stops at the source end marker or a repeated continuation. Minimum `1`. |

Enter public Note article URLs or article keys, one per item. Returns root comments, not complete reply trees. Disabled or unavailable comments are skipped without repeated requests.

Examples of supported inputs: `https://note.com/fuwafuwa_man/n/n8336606d36cd`.

Duplicate normalized inputs are processed once. Within the collection for one source input, repeated records are removed while distinct interactions or objects remain separate. The same object returned for different source inputs retains its source relationship.

The first result page counts as page 1. Public-page preparation and metadata lookups do not consume result pages. Collection stops at your page budget or the end of the available list. A short page alone does not mean that the list has ended.

### note.com comments use cases 🎯

#### Review discussion of a note.com photo article

Export root comments on a note.com photography article. Keep comment text, dates, author details and available creator replies for qualitative review.

#### Collect feedback on a note.com photo essay

Collect public root comments on a note.com photo essay. Review reader feedback, edited flags and creator responses in your own analysis of the export.

#### Review creator interaction on a note.com essay

Export public root comments on a note.com essay with creator-liked and creator-replied flags. Available latest creator replies stay in the comment row.

### Pricing and saved-result behavior 💰

Check the Actor’s **Pricing** tab for the active pricing model and current rate. Store settings can change, so this README does not claim a fixed price or runtime.

Under dataset-item pricing:

- Each successful result represents one comment for its source input.
- An invalid or unavailable input, an input with no accessible results, or an exhausted request can produce a `failed` row.
- Retry attempts and supporting requests do not create extra dataset rows by themselves.
- Nested media, profile information and other arrays remain part of their parent row.
- A normal empty continuation after earlier successes creates no additional row.
- Saved failed rows are not assumed to be free; check their treatment in the active pricing configuration.

More inputs and larger page budgets can produce more saved rows. Start with a small run and check actual usage before increasing the workload.

### note.com comments API 🔌

Replace `$ACTOR_ID` with the identifier shown in this Actor’s **API** tab and `$APIFY_TOKEN` with your Apify token.

```bash
curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["https://note.com/fuwafuwa_man/n/n8336606d36cd"],"pagesPerPost":1}'
```

Download the dataset in JSON, CSV, Excel or other formats available in the Console, or retrieve it through the Apify API. Use schedules, webhooks and Apify integrations to connect results to Google Sheets, Make, Zapier, cloud storage or your own application. These connections are configured separately by the user.

### Reliability, retries, and public-data limits ⚠️

Collection uses pure HTTP with up to five concurrent requests. Invalid syntax and confirmed missing, removed or unavailable targets stop without unnecessary retries. Temporary network or proxy failures, timeouts, blocking responses, malformed data, throttling and server errors allow up to five total attempts per request.

Successful earlier pages remain saved if a later request fails. A normal end after saved results is not retried. An input with no accessible results can receive a failed row; that alone does not prove that its underlying source does not exist. An exhausted later request can add a failed row while preserving previous output.

Returns root comments plus the latest creator reply when provided, not full nested reply trees. Article metadata determines the current or legacy comment endpoint. The current endpoint was verified for three pages; the legacy parser has fixture coverage. Disabled comments can have a historical nonzero comment count; they are skipped based on the explicit availability response.

note.com controls public availability, ranking and optional fields. Result counts can be affected by duplicates, removed content and changes during a run. A page budget is a collection limit, not a promise of exhaustive coverage.

An invalid string within a valid input list does not stop other inputs. Invalid overall configuration, such as a non-string list item or a wrong page-count type, exits before source requests. Startup failures, unavailable dataset storage or an unrecoverable result-save error can still stop the whole run. A failed save is not retried as a new scraping request.

### Frequently asked questions ❓

#### What does one Note Post Comments Scraper result represent?

Each successful row represents one comment. The source input is retained, and nested fields stay in the same row.

#### Which source limits apply?

Returns root comments plus the latest creator reply when provided, not full nested reply trees. Article metadata determines the current or legacy comment endpoint. The current endpoint was verified for three pages; the legacy parser has fixture coverage. Disabled comments can have a historical nonzero comment count; they are skipped based on the explicit availability response.

#### Does it download media files?

No. Where available, the Actor returns media URLs and metadata within the result row.

#### Does it require a note.com account or personal cookies?

No. You do not need to provide a note.com account, password or personal session cookie. Collection uses HTTP without opening a browser.

#### What happens to invalid or unavailable inputs?

Invalid individual inputs are recorded as failed without a source request. Confirmed missing or unavailable targets stop without unnecessary retries. Temporary failures allow up to five total attempts per request; other inputs and earlier saved results remain available.

#### Can I export results or run the same input again?

Yes. Export the default dataset or retrieve it through the Apify API. You can create an Apify schedule and connect completed runs to your own workflow.

### Support, responsible use, and related actors 🛟

For a reproducible issue, use the Actor’s **Issues** tab and provide the run ID, approximate time, a safe public input, expected behavior and actual result. Include the mode or page budget when relevant. Never share access tokens, personal cookies or proxy credentials.

Use public data responsibly and follow applicable privacy, copyright, contractual and platform requirements before storing, analyzing or redistributing collected information.

# Actor input Schema

## `inputList` (type: `array`):

Enter public Note article URLs or article keys, one per item. Returns root comments, not complete reply trees. Disabled or unavailable comments are skipped without repeated requests.

## `pagesPerPost` (type: `integer`):

Maximum result pages per input. Metadata requests do not count as pages. Stops at the source end marker or a repeated continuation.

## Actor input object example

```json
{
  "inputList": [
    "https://note.com/fuwafuwa_man/n/n8336606d36cd"
  ],
  "pagesPerPost": 1
}
```

# Actor output Schema

## `comments` (type: `string`):

One dataset row per public root comment. Check success or failed status.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "inputList": [
        "https://note.com/fuwafuwa_man/n/n8336606d36cd"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapingmonkey/note-post-comments-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "inputList": ["https://note.com/fuwafuwa_man/n/n8336606d36cd"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapingmonkey/note-post-comments-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "inputList": [
    "https://note.com/fuwafuwa_man/n/n8336606d36cd"
  ]
}' |
apify call scrapingmonkey/note-post-comments-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapingmonkey/note-post-comments-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/M0SZzVrxlOAbh1AQ5/builds/5A4OUzUXQOTmuVhCl/openapi.json