Tutorial
How to configure YouTube Community comments
Read comments on a community post. This guide explains how to configure the run and review its inputs in CrowdYeti.
- Input: Post or video URL.
- Output: Author, Comment, Profile URL, Source input, Data type.
- Coverage: Source accessibility and provider support determine available records and fields.
- Limits: Dates may only be available as relative text. Complete comment history is not verified. Public results may be incomplete. The limit is a maximum, not a guaranteed collection size. Up to 500 records per Scout input; fewer may be available.
- Availability: Use available credits for live runs without manual activation. Runs remain subject to service availability and account restrictions. Check Settings and review the maximum credit cost before starting.
- Usage: Review the record limit and maximum credit cost in setup. Unused reserved credits return after the charge is confirmed; a search that finds nothing can still cost credits, but a run is not charged if the source breaks and returns nothing.
Choose your source: Start with post or video url. Use the exact public source that fits your research question, and check it contains the activity you want to inspect.
Review the available fields: Available output includes Author, Comment, Profile URL, Source input, Data type. Decide which details are useful and retain source links with your selection. Actual coverage depends on the source and provider.
Keep observed facts separate from inferred details. Missing fields should remain missing rather than being presented as verified information.
Choose your selection criteria: Write down what makes a record useful before adding deeper research. A relevant topic, a clearly expressed need or a public profile that fits your brief is more useful than a large unreviewed list.
Configure your run: Open Scout setup, enter the source and review its supported options and record limit.
Save a separate draft when changing the research source or purpose, so the intended inputs and review criteria remain clear.
Inspect coverage and limits: Public platform totals do not guarantee that every record is accessible. Review available fields, duplicate handling and source limits before treating a dataset as complete.
Review before execution: Use available credits for live runs without manual activation. Runs remain subject to service availability and account restrictions. Check Settings and review the maximum credit cost before starting.
Saving a workflow does not start collection. Start the run explicitly, follow its progress in Runs and review the saved records before exporting.
For the current product boundary and a tour of the workspace, read Getting started.
