Note Post Search Scraper

Note Post Search Scraper — Search Note articles by keyword and export titles, creators, publication dates, prices, and engagement counts. Add supported inputs and start a run to get structured public data without providing a note.com account.

Find popular note.com articles about photography. Export titles, author profiles, dates, prices and like counts to shortlist articles for editorial research.

At a glance	Details
📥 Input	Enter one search keyword or phrase per item. Search URLs are not accepted. Choose new or popular order. Each result page returns up to 20 articles.
📤 Output	One post per success row, with source input retained
📄 Pagination	pagesPerSearch 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 search scraper collects 📊

Search Note articles by keyword and export titles, creators, publication dates, prices, and engagement counts.

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.

{
  "inputList": [
    "写真"
  ],
  "mode": "new",
  "pagesPerSearch": 1
}

pagesPerSearch 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.

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):

{
  "input": "写真",
  "status": "success",
  "type": "post",
  "id": "179811730",
  "key": "n54bf8e512eae",
  "url": "https://note.com/light_honest114/n/n54bf8e512eae",
  "title": "デジタル依存・SNS比較の脱却",
  "post_type": "TextNote",
  "published_at": "2026-09-12T10:54:34.000+09:00",
  "description": null,
  "preview_text": "",
  "price_jpy": 300,
  "is_paid": true,
  "can_read": false,
  "likes_count": 2,
  "anonymous_likes_count": null,
  "comments_count": 0,
  "image_count": 1,
  "thumbnail_url": "https://assets.st-note.com/production/uploads/images/312818688/rectangle_large_type_2_51c883bb1287670223f1777f7ca11543.jpeg?fit=bounds&quality=85&width=1280",
  "is_pinned": null,
  "hashtags": null,
  "author": {
    "id": "15269439",
    "key": "15dea4ccc3859f9ece9007e23a831ab5",
    "username": "light_honest114",
    "name": "みなもと",
    "url": "https://note.com/light_honest114",
    "description": null,
    "profile_image_url": "https://assets.st-note.com/production/uploads/images/309972104/profile_28b726612836e3f7d9e351916ef617b6.jpg?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
  }
}

Complete failed result:

{
  "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
}

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 one search keyword or phrase per item. Search URLs are not accepted. Choose new or popular order. Each result page returns up to 20 articles. At least 1 item.
mode	string	No	"new"	Choose newly published or popular articles. Both orders use the same output fields. Allowed values: new, popular.
pagesPerSearch	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 one search keyword or phrase per item. Search URLs are not accepted. Choose new or popular order. Each result page returns up to 20 articles.

Examples of supported inputs: 写真.

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 🎯

Find popular photography articles on note.com

Find popular note.com articles about photography. Export titles, author profiles, dates, prices and like counts to shortlist articles for editorial research.

Find recent illustration articles on note.com

Collect recent note.com articles about illustration. Keep author links, publication dates and hashtags to review new topics and potential contributors.

Research generative AI publishing on note.com

Search recent note.com articles about generative AI. Export titles, dates, prices and authors for your own comparison of free and paid publishing topics.

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.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["写真"],"mode":"new","pagesPerSearch":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.

Search exports article metadata and available preview fields. The validated anonymous search pages had no preview body, so preview_text is null. Use Note Post Scraper for available article text. New and popular search orders were verified separately for three consecutive pages. Live search results can change while pages are requested.

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 Search 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?

Search exports article metadata and available preview fields. The validated anonymous search pages had no preview body, so preview_text is null. Use Note Post Scraper for available article text. New and popular search orders were verified separately for three consecutive pages. Live search results can change while pages are requested.

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.