Quora Monitor
Pricing
from $1.00 / 1,000 results
Quora Monitor
Entity-agnostic Quora change monitoring (question, answer, profile, topic, or post) plus bounded Space metadata, feed, and contributor monitoring, with stateful diff evidence.
Quora Monitor
Pricing
from $1.00 / 1,000 results
Entity-agnostic Quora change monitoring (question, answer, profile, topic, or post) plus bounded Space metadata, feed, and contributor monitoring, with stateful diff evidence.
Terms whose public discovery results should be checked.
Summary only, or summary plus visible feed and contributors.
Choose which visible Space section to monitor.
Check visible Space contributors for changes.
Maximum visible feed items checked in each Space.
Maximum visible contributors checked in each Space.
When Scrape Depth is detail, bounded number of question-type feed items to open and expand into full question fields (question_id, question_answer_count, question_view_count, question_details, question_created_at, question_updated_at). Zero keeps the feed-digest-only behavior.
Include visible media URLs when present.
Include bounded outbound links from feed cards.
Keep visible Space rules and participation requirements.
Keep visible Topic labels and links associated with a watched page or Space.
Check visible Space rules and settings when rendered.
Requires an Apify state store; unchanged records are omitted.
Return records even when no visible change was detected.
Opt-in age-based pruning for unseen state snapshots; zero disables pruning.
Choose the Quora language version to request when available. This selects page language; it does not translate content.
Optional export selection for API users. Leave empty to return every observed buyer-relevant field; fields absent from a page are omitted.
[]Public Space, question, answer, profile, topic, or post URLs.
Maximum records returned across watched sources.
Choose whether to return hashes, changed fields, or previous/current values.
Add one clearly labelled row for each page Quora did not make available. Leave off for a clean content-only dataset.
Optional stable name for comparing this source across scheduled runs.
Maximum records collected from each URL or search source before moving to the next source.
Standard is the cost-conscious default. Maximum reach uses stronger routing when available. Direct connection is mainly useful when you already control the connection.