# note Creator Feed Monitor - Posts & Mentions — workflow

## Choose this tool

Follow known creators on Japan’s note.com community without maintaining your own RSS collector. Bring publisher headlines, opening excerpts and source links into a creator watchlist or campaign report.

Useful output columns: `noteId`, `title`, `sourceHandle`, `creatorName`, `publishedAt`, `comparisonStatus`.

## Practical workflow

Copy this exact input into the Actor’s JSON input editor, then run it.

```json
{
  "creators": [
    "info",
    "note_ir"
  ],
  "maxItemsPerFeed": 10,
  "maxResults": 20
}
```

This example selects up to ten entries each from the official `info` and `note_ir` feeds. `{}` uses the same demonstration creators. Supply exact handles in `creators` to replace them with your own watchlist. Review the dataset and `SUMMARY` after the run.

## Check the fit

note’s documented creator RSS contains the latest 25 entries in publication-date order. This version accepts `note.com` creator handles only, not magazine feeds or custom-domain note pro feeds.

An edit is detected only while the post is visible in the selected feed window. A publication date is the source’s publication date, not an edit timestamp. This Actor does not expose engagement counts, follower counts, comments, ranking scores or historical backfill. Feeds can lag or change between requests.

Overlapping feeds are deduplicated by post identity and their `feedUrls` are retained. If the same post has conflicting fields in two responses, the first observation is retained and the conflict is recorded in SUMMARY. Treat that run as partial.

SUMMARY records actual saved and observed counts, per-feed available/selected entries, filter and unchanged skips, failed sources, sources not reached and deadline or spending stops. A selected result/window cap is scope, not an operational failure. Partial runs can contain useful paid observations. All-source failures with no usable output fail rather than producing fake error rows.

Requests respect robots.txt, validate public network destinations, reject redirects and bound response size and retry delays. Robots restrictions or upstream errors are reported. There is no fallback through private APIs or alternate anti-bot routes.

## Real output sample

One selected row from a 2026-10-14 run. One saved row, selected scalar columns only. Contact details, patient demographics and long text are omitted. Original values and nulls are preserved.

Run: 4q2V1r1gqCky6WkPb. Summary status: ok. Incomplete: false.

Historical output from this run; the current example input is a separate starting configuration and may produce different records.

```json
{
  "noteId": "n7ce9240358d7",
  "title": "仲間と力を合わせて、乗り越えたことは？「#チームだからできたこと」で投稿を募集します。",
  "sourceHandle": "info",
  "creatorName": "note公式",
  "publishedAt": "2026-10-09T02:00:00.000Z",
  "comparisonStatus": "unchanged",
  "sourceUrl": "https://note.com/info/n/n7ce9240358d7",
  "observedAt": "2026-10-14T14:12:05.442Z",
  "thumbnailUrl": "https://assets.st-note.com/production/uploads/images/321737900/rectangle_large_type_2_2f9a661d240a7a31bdda6cb0096fc7cc.png?width=800"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [Discourse Community Topic Monitor](https://mayd-it.com/data-tools/actors/discourse-community-topic-monitor/)

Track recent public Discourse topics by community and keyword. Compare topic activity and saved changes with source links. Bounded latest-topic coverage; no private forums. Keep this Discourse Community Topic Monitor evidence alongside the original source in a reviewed public community review workflow.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Public preview/RSS/relay coverage differs by platform. Engagement values are not directly comparable, and a missing post is not proof of deletion or account inactivity.

### [Telegram Public Channel Posts & Change Monitor](https://mayd-it.com/data-tools/actors/telegram-public-channel-monitor/)

Export public Telegram channel posts, text, dates, view estimates and links. Compare saved observations and filter keywords without a login, API key or proxy. Keep this Telegram Public Channel Posts & Change Monitor evidence alongside the original source in a reviewed public community review workflow.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Public preview/RSS/relay coverage differs by platform. Engagement values are not directly comparable, and a missing post is not proof of deletion or account inactivity.
