# Note Magazine Posts Scraper (`scrapingmonkey/note-magazine-posts-scraper`) Actor

Extract articles from Note magazines with public previews, author profiles, publication dates, prices, likes, and magazine metadata.

- **URL**: https://apify.com/scrapingmonkey/note-magazine-posts-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 Magazine Posts Scraper** — Extract articles from Note magazines with public previews, author profiles, publication dates, prices, likes, and magazine metadata. Add supported inputs and start a run to get structured public data without providing a note.com account.

Collect public article listings from a note.com product improvement magazine. Keep titles, previews, dates and magazine context for a release reference index.

| At a glance | Details |
|---|---|
| 📥 Input | Enter public Note magazine URLs or m-prefixed magazine keys, one per item. The source controls page size; the verified magazine returned 14 articles per page. |
| 📤 Output | One post per success row, with source input retained |
| 📄 Pagination | `pagesPerMagazine` 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 magazine posts scraper collects 📊

Extract articles from Note magazines with public previews, author profiles, publication dates, prices, likes, and magazine metadata.

Data can include:

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

### How to collect posts 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 **Posts** dataset view and review the individual records.
5. Export the dataset or retrieve it from your application.

```json
{
  "inputList": [
    "https://note.com/info/m/m9d9015b8e27a"
  ],
  "pagesPerMagazine": 1
}
```

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

### note.com posts 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. |
| `id` | string or null | Numeric source identifier exported as a string. |
| `key` | string or null | Stable Note entity key. |
| `url` | string or null | Public URL of the collected object. |
| `title` | string or null | Public title supplied by the source. |
| `post_type` | string or null | Post type when exposed by the public response. |
| `published_at` | string or null | Publication time as supplied by the source. |
| `description` | string or null | Available public description. |
| `preview_text` | string or null | Plain-text preview returned by the public listing endpoint. |
| `price_jpy` | integer or null | Article price in Japanese yen when provided. |
| `is_paid` | boolean or null | Is paid when exposed by the public response. |
| `can_read` | boolean or null | Whether the current anonymous visitor can read the article. False does not mean its public metadata is unavailable. |
| `likes_count` | integer or null | Likes count supplied by the source; absent values remain null. |
| `anonymous_likes_count` | integer or null | Like total from visitors with no identified account record. |
| `comments_count` | integer or null | Comments count supplied by the source; absent values remain null. |
| `image_count` | integer or null | Image count supplied by the source; absent values remain null. |
| `thumbnail_url` | string or null | Available thumbnail URL. |
| `is_pinned` | boolean or null | Is pinned when exposed by the public response. |
| `hashtags` | array or null | Available hashtag labels. |
| `author` | object or null | Author when exposed by the public response. |
| `author.id` | string or null | Source identifier of this entity, retained as a string. |
| `author.key` | string or null | Source key identifying this entity. |
| `author.username` | string or null | Username when exposed by the public response. |
| `author.name` | string or null | Public name supplied by the source. |
| `author.url` | string or null | Public source URL. |
| `author.description` | string or null | Available public description. |
| `author.profile_image_url` | string or null | Available profile image URL. |
| `author.header_image_url` | string or null | Available header image URL. |
| `author.followers_count` | integer or null | Followers count supplied by the source; absent values remain null. |
| `author.following_count` | integer or null | Following count supplied by the source; absent values remain null. |
| `author.follow_counts_visible` | boolean or null | Follow counts visible when exposed by the public response. |
| `author.is_official` | boolean or null | Is official when exposed by the public response. |
| `is_pinned_in_magazine` | boolean or null | Is pinned in magazine when exposed by the public response. |
| `magazine` | object or null | Metadata of the input magazine attached to each article row. |
| `magazine.key` | string or null | Source key identifying this entity. |
| `magazine.name` | string or null | Public name supplied by the source. |
| `magazine.url` | string or null | Public source URL. |
| `magazine.description` | string or null | Available public description. |
| `magazine.posts_count` | integer or null | Posts count supplied by the source; absent values remain null. |
| `magazine.price_jpy` | integer or null | Price jpy 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/info/m/m9d9015b8e27a",
  "status": "success",
  "type": "post",
  "id": "144331179",
  "key": "nb50a11d765b8",
  "url": "https://note.com/info/n/nb50a11d765b8",
  "title": "【2026年】note新機能（カイゼン）のお知らせまとめ",
  "post_type": "TextNote",
  "published_at": "2026-02-03T11:00:00.000+09:00",
  "description": null,
  "preview_text": "クリエイターのみなさんからの貴重な声をもとに、noteでは日々、新機能（カイゼン）の開発に励んでいます。この記事では、2026年1月以降にリリースした新機能やカイゼン情報をまとめていきます。記事の更新は月1回です。気になる機能があれば、ぜひお試しください！\n\n8月：自動翻訳がひろがる。有料記事と韓国語に対応しました8月3日\nメンバーシップの請求タイミングが変わりました。\n\n8月5日\nnote質問箱で質問を受け付ける相手を、メンバーシップのプランごとに設定できるようになりました",
  "price_jpy": 0,
  "is_paid": false,
  "can_read": true,
  "likes_count": 1952,
  "anonymous_likes_count": 8,
  "comments_count": null,
  "image_count": 1,
  "thumbnail_url": "https://assets.st-note.com/production/uploads/images/247278566/rectangle_large_type_2_9e4169e546f371a58777847904532900.png",
  "is_pinned": null,
  "hashtags": null,
  "author": {
    "id": null,
    "key": null,
    "username": "info",
    "name": "note公式",
    "url": "https://note.com/info",
    "description": null,
    "profile_image_url": "https://assets.st-note.com/production/uploads/images/93752369/profile_ae0f62081ec839762d6e066ef222a3d6.png?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
  },
  "is_pinned_in_magazine": true,
  "magazine": {
    "key": "m9d9015b8e27a",
    "name": "noteカイゼン報告",
    "url": "https://note.com/info/m/m9d9015b8e27a",
    "description": "noteでは、クリエイターのみなさんからの声をもとに、新機能（カイゼン）の開発を日々続けています。表現の幅が広がる新機能から、要望・フィードバックを元に対応したものまで。",
    "posts_count": 392,
    "price_jpy": 0
  }
}
```

Complete failed result:

```json
{
  "input": "invalid input",
  "status": "failed",
  "type": null,
  "id": null,
  "key": null,
  "url": null,
  "title": null,
  "post_type": null,
  "published_at": null,
  "description": null,
  "preview_text": null,
  "price_jpy": null,
  "is_paid": null,
  "can_read": null,
  "likes_count": null,
  "anonymous_likes_count": null,
  "comments_count": null,
  "image_count": null,
  "thumbnail_url": null,
  "is_pinned": null,
  "hashtags": null,
  "author": null,
  "is_pinned_in_magazine": null,
  "magazine": 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 **Posts** 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 magazine URLs or m-prefixed magazine keys, one per item. The source controls page size; the verified magazine returned 14 articles per page. At least `1` item. |
| `pagesPerMagazine` | 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 magazine URLs or m-prefixed magazine keys, one per item. The source controls page size; the verified magazine returned 14 articles per page.

Examples of supported inputs: `https://note.com/info/m/m9d9015b8e27a`.

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 posts use cases 🎯

#### Catalog note.com product improvement articles

Collect public article listings from a note.com product improvement magazine. Keep titles, previews, dates and magazine context for a release reference index.

#### Export a note.com press room article index

Collect the public article listings in a note.com press room magazine. Export titles, author links, dates and previews to organize source material.

#### Research a curated note.com article magazine

Export the public articles listed in a curated note.com magazine. Keep article metadata, previews and collection context to review its editorial selection.

### 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 post 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 posts 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/info/m/m9d9015b8e27a"],"pagesPerMagazine":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.

Only publicly listed article previews and magazine metadata are exported. Paid article bodies are not unlocked. Actual page size follows the source. Magazine layout story settings can differ from the number of returned rows.

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 Magazine Posts Scraper result represent?

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

#### Which source limits apply?

Only publicly listed article previews and magazine metadata are exported. Paid article bodies are not unlocked. Actual page size follows the source. Magazine layout story settings can differ from the number of returned rows.

#### 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 magazine URLs or m-prefixed magazine keys, one per item. The source controls page size; the verified magazine returned 14 articles per page.

## `pagesPerMagazine` (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/info/m/m9d9015b8e27a"
  ],
  "pagesPerMagazine": 1
}
```

# Actor output Schema

## `posts` (type: `string`):

One dataset row per public Note article. 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/info/m/m9d9015b8e27a"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapingmonkey/note-magazine-posts-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/info/m/m9d9015b8e27a"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapingmonkey/note-magazine-posts-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/info/m/m9d9015b8e27a"
  ]
}' |
apify call scrapingmonkey/note-magazine-posts-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapingmonkey/note-magazine-posts-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/ve8bR1VaQLMeaGTHe/builds/yDBIWPSS370OQI470/openapi.json