Dataify Google News

Use this skill to turn a user's Google News request into a Dataify Scraper API form submission.

Required Pre-Call Confirmation

Before every real API call, follow this confirmation flow. These rules override any older workflow order in this skill.

1. Parse the user's request into the API body fields and fixed engine value.
2. Apply defaults only when the parameter description explicitly states a default. Do not use example YAML values, sample prompts, placeholder values, or examples such as pizza, us, en, dates, airport codes, or tokens as defaults.
3. If a required parameter has no documented default and cannot be inferred from the user request, ask for that parameter before building the table.
4. Show a Markdown table before calling the API. Do not include Authorization. Include the complete body field list from this skill's reference document, including engine, even when a field is currently blank.
5. The table must have exactly these columns: 参数名, 当前值, 默认值, 说明.
6. After the table, ask the user whether they want to modify any parameter. Do not call the API until the user explicitly confirms.
7. If the user changes a parameter, regenerate the table and ask for confirmation again.
8. If the token is missing, stop and tell the user to sign in at Dataify Dashboard to obtain DATAIFY_API_TOKEN.

Use the bundled preview helper whenever possible to generate the confirmation table from this skill's reference document:

python3 scripts/preview_params.py --params-json '{"q":"USER_QUERY"}'

Pass every parsed current value to preview_params.py using --params-json or matching --field value arguments. The helper reads defaults and descriptions from references/*api.md; if the helper cannot parse a default, leave the default blank rather than inventing one. 9. After confirmation and token handling, call the bundled Python script with python3 and return the API response body directly without summarizing, extracting, cleaning, translating, or reshaping it.

Workflow

1. Parse the user's request into Google News fields. Use q as the query and set engine to google_news.
2. If the token is missing, stop and tell the user to sign in at Dataify Dashboard to obtain DATAIFY_API_TOKEN.
3. Build request parameters with only the fields the user requested plus required defaults. Use json: "1" unless the user asks for another output format.
4. Run the bundled Python script with python3. Run it from this skill directory, or use the absolute path to scripts/google_news.py.

python3 scripts/google_news.py --q "pizza" --json 1

If the user provided a token in the conversation instead of an environment variable, pass it with --token and avoid echoing it back in the final answer:

python3 scripts/google_news.py --token "USER_TOKEN" --q "pizza" --gl us --hl en --no_cache true

For many fields, you may pass one JSON object with shell-appropriate quoting. The script will still submit form data to the API:

python3 scripts/google_news.py --params-json '{"q":"pizza","json":"1","gl":"us","hl":"en","so":"1"}'

5. Return the script output directly to the user. Do not summarize, extract, clean, translate, or reshape the API response.

Field Mapping

Use references/google_news_api.md when you need the exact field list or examples.

Core rules:

• Always submit the API request as form data with Content-Type: application/x-www-form-urlencoded.
• Always force engine to google_news.
• Keep request values as strings unless the script accepts and normalizes a boolean.
• Omit optional fields that the user did not request.
• Ask a follow-up only when the required query q cannot be inferred.
• Normalize token values in the script. A token without Bearer is accepted and prefixed automatically.

Common mappings:

• "JSON" -> json: "1"
• "JSON+HTML" -> json: "2"
• "HTML" -> json: "3"
• "Light JSON" -> json: "4"
• bypass cache / no cache -> no_cache: "true"
• use cache -> no_cache: "false"
• country or region for Google News behavior -> gl
• interface/search language -> hl
• topic token -> topic_token
• Google Knowledge Graph MID -> kgmid
• publication token / publisher token -> publication_token
• section token -> section_token
• story token -> story_token
• sort by relevance -> so: "0"
• sort by date / latest / newest -> so: "1"