community-radar
Instructions
Setup state. Not yet configured for this org. Load the Setup sub-page and walk the user through wiring the community-radar trigger (SCHEDULE + Apify search actors across LinkedIn / X / Reddit / Hacker News, or WEBHOOK from a social listening tool the user already pays for) with the org's brand-and-pain-language keyword list, the platforms to monitor, and the follow-up sequence before running this play. (After setup is performed, rewrite this paragraph via swan-update-skill to describe the current state — trigger type chosen, keywords / brand terms / pain-language phrases monitored, platforms covered, sequence wired, success metric, and last-refreshed date — so future runs see the current configuration without re-checking.)
When this fires
A SCHEDULE trigger running an Apify search actor (LinkedIn search, X / Twitter search, Reddit search, Hacker News scrape) surfaces new mentions of the configured keywords. Or a WEBHOOK from a social listening service the user already pays for (Brand24, Mention, Hootsuite, Triggify, custom Reddit / X monitoring) pushes mentions in. Payload includes: platform, author, mention text, post URL, engagement metrics on the parent post.
Note: LINKEDIN_ENGAGEMENT is not the right trigger here — that one follows specific LinkedIn profiles. For keyword-driven brand-mention sweeps across LinkedIn, use SCHEDULE + an Apify LinkedIn-search actor.
The window is short on public social — 24-48 hours feels reasonable; > 1 week and the reply looks bot-driven.