Dataify YouTube Comment By ID

submit youtube comment collection jobs through dataify builder by video id. after a successful submission, give the user the task_id, the returned or inferred status, and direct them to dataify to view results.

use this skill when the user wants to collect, scrape, crawl, fetch, or extract youtube comments by video id, or when they ask in chinese with meanings like "youtube评论信息采集", "youtube评论信息抓取", "youtube评论采集", "youtube评论抓取", or similar. also use when the user provides a task_id or status, needs to configure DATAIFY_API_TOKEN, or is troubleshooting dataify builder requests.

inputs

• dataify api token: long-form bearer token for authenticating builder requests. stored locally as environment variable DATAIFY_API_TOKEN. obtain from dataify dashboard top-right corner or register at dataify login.
• video_id (required): unique youtube video identifier. example: 8RePenzQH80. user may provide one or multiple ids.
• load_replies (optional, default 10): integer >= 0. time or iterations for loading comment replies on the page.
• num_of_comments (optional, default 10): integer >= 0. total number of comments to collect per video.
• file_name (optional, default {{TasksID}}): custom output file name. builder auto-generates from task id if not changed.

external connection: dataify builder endpoint at https://scraperapi.dataify.com/builder?platform=1.

procedure

1. display the parameter checklist table showing video_id (required, default 8RePenzQH80), load_replies (required, default 10), num_of_comments (required, default 10), and file_name (optional, default {{TasksID}}). if user has already provided values, show those in place of defaults.
2. ask: "do you want to change any of these values before i submit the task?"
3. ask: "do you want to collect multiple youtube comment groups? if yes, provide multiple groups of video_id, load_replies, and num_of_comments."
4. collect user responses. if multiple groups requested, gather each video_id, load_replies, and num_of_comments tuple.
5. normalize all parameter groups into a list of objects. apply defaults where user did not specify values.
6. trim leading/trailing whitespace from all video_id values.
7. resolve dataify api token: check explicit user input first, then check saved DATAIFY_API_TOKEN environment variable. store resolved token for next step.
8. validate each video_id (non-empty after trim), each load_replies (integer >= 0), each num_of_comments (integer >= 0), and file_name (non-empty). halt with specific error message if validation fails.
9. convert numeric values to strings (e.g., "load_replies":"10").
10. serialize normalized parameter list to json string for spider_parameters field.
11. construct form data: spider_name=youtube.com, spider_id=youtube_comment_by-id, spider_errors=true, file_name=<user_value_or_default>, spider_parameters=<json_string>.
12. submit POST request to https://scraperapi.dataify.com/builder?platform=1 with authorization header Bearer <resolved_token>, content type application/x-www-form-urlencoded, and form fields from step 11.
13. read data.task_id and data.status (or status if present) from builder response.
14. output the task_id, status, and dashboard link to user.
15. stop. do not poll for results or wait for completion.

decision points

• if user provides api token in request: use it for this run only. proceed to validation.
• if no explicit token and DATAIFY_API_TOKEN saved locally: use saved token without re-prompting. proceed to validation.
• if no explicit token and no saved DATAIFY_API_TOKEN: ask user to enter their api token. after user provides token, ask: "would you like to save this token as DATAIFY_API_TOKEN for future use?" if yes, output shell commands (powershell or bash) to set the environment variable and ask user to run them. if no, use token for this run only.
• if user has no api token at all: direct them to dataify login to register or log in and retrieve token from dashboard top-right.
• if user wants multiple comment groups: repeat steps 4-5 to gather each group's parameters, then serialize all groups into a single json array for spider_parameters.
• if any parameter fails validation (empty video_id, non-integer load_replies, non-integer num_of_comments, empty file_name): halt execution and output the specific validation error. do not submit request.
• if builder response lacks task_id: likely authorization header, token value, spider_name, or spider_id is incorrect. advise user to check token and try again.
• if builder response contains "Necessary parameters is empty!": spider_parameters was not sent as a json string, or one parameter object is missing required fields. recheck serialization and field presence.
• if network timeout or http error: advise user to retry and check internet connectivity.

output contract

on successful builder submission, return:

• task_id: string identifier for the created dataify task (from data.task_id field in response).
• status: string status value, e.g., "pending", "running", "completed" (from data.status or status field).
• parameters submitted: markdown table or json showing final video_id, load_replies, num_of_comments, and file_name values.
• dashboard url: clickable link to dataify dashboard with utm_source=skill.
• message: confirmation message: "task created successfully. task_id: [task_id]. status: [status]. visit dataify dashboard to view or manage results."

data format: json response from builder endpoint. store task_id and status for user reference. do not store raw builder response in output; summarize it.

outcome signal

user knows the skill worked when:

1. a task_id is returned and displayed (non-empty string).
2. a status value is shown (e.g., "pending" or "running").
3. the skill outputs a link to dataify dashboard with utm_source=skill parameter.
4. no validation errors are printed.
5. no authorization errors (e.g., "invalid token") are returned from the builder.

if user saved the api token, they see confirmation output showing the powershell or bash command they ran, plus confirmation that token is now saved locally.

token handling examples

powershell (current session only):

$env:DATAIFY_API_TOKEN = "YOUR_DATAIFY_API_TOKEN"

powershell (persistent user-level):

[Environment]::SetEnvironmentVariable("DATAIFY_API_TOKEN", "YOUR_DATAIFY_API_TOKEN", "User")

bash/zsh (current session):

export DATAIFY_API_TOKEN="YOUR_DATAIFY_API_TOKEN"

bash/zsh (persistent, add to ~/.bashrc or ~/.zshrc):

echo 'export DATAIFY_API_TOKEN="YOUR_DATAIFY_API_TOKEN"' >> ~/.bashrc
source ~/.bashrc

using the helper script

for stable execution, prefer scripts/submit_dataify_youtube_comment_by_id.py (python 3.6+) instead of manual builder flow:

python3 ".\scripts\submit_dataify_youtube_comment_by_id.py" --video-id "8RePenzQH80"

if python3 not available, try python. script checks runtime version and requires python 3.6+.

override saved token or defaults for one run:

python3 ".\scripts\submit_dataify_youtube_comment_by_id.py" --api-token "YOUR_DATAIFY_API_TOKEN" --video-id "8RePenzQH80" --load-replies 10 --num-of-comments 10 --file-name "{{TasksID}}"

submit multiple groups via json array:

python3 ".\scripts\submit_dataify_youtube_comment_by_id.py" --params-json '[{"video_id":"8RePenzQH80","load_replies":"10","num_of_comments":"10"},{"video_id":"dQw4w9WgXcQ","load_replies":"10","num_of_comments":"20"}]'

script outputs json summary: task_id, status, parameters, file_name, dashboard_url, message.

troubleshooting

missing dataify api token: no explicit token passed and DATAIFY_API_TOKEN not set locally. ask user to provide token. offer to save it as DATAIFY_API_TOKEN. if user has no token, direct to dataify login. if user has token, it's in dataify dashboard top-right.

video_id cannot be empty: required youtube video id is missing or empty after trim. ask user to provide one.

load_replies must be an integer greater than or equal to 0: reply load value is not a valid integer or is negative. ask user to enter integer >= 0.

num_of_comments must be an integer greater than or equal to 0: comment count is not a valid integer or is negative. ask user to enter integer >= 0.

file name cannot be empty: file_name parameter is empty. use default {{TasksID}} or ask user for non-empty name.

necessary parameters is empty: spider_parameters was not sent as json string, or one parameter object lacks required fields (video_id, load_replies, num_of_comments). recheck serialization.

missing task_id in response: likely wrong authorization header, invalid token, incorrect spider_name, or incorrect spider_id. verify token and field values. retry request.

http 401 unauthorized: token is invalid or expired. ask user to get a fresh token from dataify dashboard.

http 4xx or 5xx errors: builder endpoint returned an error. log the full response body and advise user to retry or contact dataify support.

network timeout or connection refused: dataify builder endpoint unreachable. check internet connectivity and try again.

guardrails

• do not poll builder for results after task creation succeeds. stop immediately after receiving task_id.
• use only "api token" and "DATAIFY_API_TOKEN" when referring to authentication. no synonyms.
• do not hard-code local python paths. use system python3 or python command.
• do not claim the builder response contains youtube comment results. only confirm task creation.
• do not invent response fields. output only fields from builder response.
• always direct user to dataify dashboard after successful task creation.
• do not silently persist tokens. always ask user permission before saving DATAIFY_API_TOKEN locally.
• do not submit builder request without a resolved token.

credits: original author dataify-server. enriched per implexa quality standards.