leoworks/naver-ai-briefing-monitor
leoworks--naver-ai-briefing-monitorDestructive
This tool calls the Actor "leoworks/naver-ai-briefing-monitor" and retrieves its output results. Actor description: Track your brand in the Naver AI briefing (네이버 AI 브리핑): answer, cited sources, AI ads — AI search visibility and GEO. Use for AI answers; for shop ranks use leoworks/naver-shopping-rank-tracker. queries in Korean; brandNames flag mentions. No login, ~10 s/2 queries, pay per query.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| queries | Yes | **REQUIRED** Korean search queries to check. Informational, how-to, review and comparison queries trigger AI briefings most often (see README). Example values: ["콜라겐 효과","전기포트 세척 방법"] | |
| surface | No | PC search shows AI briefings slightly more often in our tests. Example values: "pc" | pc |
| 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. | |
| brandNames | No | Brands to check in each AI briefing (Korean or English). | |
| includeAds | No | Also request the ads Naver attaches to the AI briefing. Example values: true | |
| healthCheck | No | Internal: fail the run when results look degraded (used by the developer's scheduled checks). | |
| maxConcurrency | No | Queries checked in parallel. Example values: 5 | |
| competitorNames | No | Competitors to check the same way. Brands + competitors: up to 10 in total. | |
| 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 |