leoworks/naver-blog-brand-monitor
leoworks--naver-blog-brand-monitorDestructive
This tool calls the Actor "leoworks/naver-blog-brand-monitor" and retrieves its output results. Actor description: Naver Blog scraper (네이버 블로그): posts by keyword, sponsored post detection (체험단/협찬), sentiment, brand mentions — Korean social listening. Use for blog posts; for shop ranks use leoworks/naver-shopping-rank-tracker. queries = Korean keywords. No login, ~6 min/1,000 posts, pay per post.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Most recent posts first (good for monitoring) or Naver relevance order. Example values: "recent" | recent |
| judge | No | Which judgments to add (charged as post-judged per post when any is on): sponsored (체험단/협찬 vs 내돈내산), sentiment, brandMention. Example values: {"sponsored":true,"sentiment":true,"brandMention":true} | |
| queries | Yes | **REQUIRED** Naver Blog search queries — usually your brand or product name in Korean (e.g. 라운드랩 선크림, 다이슨 에어랩 후기). Example values: ["라운드랩 선크림"] | |
| dateFrom | No | Only posts published on or after this date (YYYY-MM-DD). | |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| ncpApiKey | No | Optional secret key paired with the key ID above. | |
| brandNames | No | Brands whose mention you want checked in every post (Korean or English, e.g. 라운드랩, Round Lab). Up to 10. Example values: ["라운드랩"] | |
| healthCheck | No | Internal: fail the run when results look degraded (used by the developer's scheduled checks). | |
| ncpApiKeyId | No | Optional. Use your own NAVER Cloud (NCP) NAVER API Hub key for post discovery instead of web search — steadier for large daily volumes. See README. | |
| maxConcurrency | No | Posts processed in parallel. Example values: 10 | |
| includeFullText | No | Add the full post text to each row (larger output). | |
| maxPostsPerQuery | No | Up to 1,000 posts per query. The form starts at 8 for a quick, low-cost first run (default when omitted via API: 50). Example values: 8 | |
| proxyConfiguration | No | Default Apify datacenter proxy works for most users. Example values: {"useApifyProxy":true} | |
| residentialFallback | No | Retry failing requests through Korean residential proxy. Example values: true |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key | |
| runId | Yes | Actor run ID | |
| stats | No | Run statistics | |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED | |
| actorId | Yes | Stable Apify Actor ID from the run record | |
| summary | Yes | Past-tense summary of the run state | |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) | |
| nextStep | Yes | One primary follow-up action with identifiers interpolated | |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. | |
| actorName | No | "username/actor-name" | |
| startedAt | No | ISO timestamp when the run started | |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) | |
| statusMessage | No | Pass-through from Apify run.statusMessage | |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |