X / Twitter

Configure the per-workspace Apify-backed X collector. Candidates are ranked by velocity — (likes + 3 × retweets) / age_hours — and merged into project/x/x.json in place. Needs the APIFY_TOKEN workspace secret.

API token stored as the APIFY_TOKEN workspace secret, shared by every Apify-backed collector (Google Trends, X, TikTok). The stored value is never sent back to the browser — leave the field blank to keep the stored token, or type a new one and Save to replace it. Saving a blank field changes nothing; use Remove to delete the stored secret. Test validates the currently stored token against Apify.

Scrape window, engagement floors, store retention and the per-run Apify cost caps.

Search queries, the relevance allowlist, the scraper actor and the language filter.

Keywords

Search queries for the X actor. Leave the list empty to fall back to the Hacker News keywords (workspace.json.hackernews.keywords), so both sources stay on one topic list.

Relevance keywords
None defined. Add one below.

Allowlist gate applied to every candidate before it is written — off-topic viral posts are dropped. Empty falls back to the keywords above.

Languages