article-content-extractor-api-skill

This skill helps users run the Article Content Extractor BrowserAct template and extract structured public data. Use this skill when users ask to collect article content extractor data, scrape article content extractor results, monitor public records from this source, export structured records for a

Article Content Extractor Automation Skill

📖 Brief

This skill uses BrowserAct's Article Content Extractor API template to extract structured public data. It starts the official workflow template, waits for completion, and prints the returned result so the Agent can use the data for research, monitoring, reporting, or downstream automation.

✨ Features

1. No hallucinations, ensuring stable and accurate data extraction: Pre-set workflows avoid AI generative hallucinations, ensuring stable and precise data extraction.
2. No CAPTCHA issues: No need to handle reCAPTCHA or other verification challenges.
3. No IP restrictions or geo-blocking: No need to handle regional IP restrictions or geofencing.
4. Faster execution: Tasks execute faster compared to pure AI-driven browser automation solutions.
5. Extremely high cost-efficiency: Significantly lowers data acquisition costs compared to high-token-consuming AI solutions.

🔑 API Key Guide

Before running, check the BROWSERACT_API_KEY environment variable. If not set, do not take other measures; ask and wait for the user to provide it. Agent must inform the user:

"Since you haven't configured the BrowserAct API Key yet, please go to the BrowserAct Console to get your Key."

🛠️ Input Parameters

Agent should configure the following parameters based on user requirements:

1. Article URLs
   • Type: string
   • Description: Public article URLs to open, one per line or separated by commas.
   • Example: https://blog.apify.com/what-is-web-scraping/
   • Default: https://blog.apify.com/what-is-web-scraping/
2. Count
   • Type: number
   • Description: Maximum number of article URLs to process.
   • Example: 5
   • Default: 5

🚀 Invocation Method

Agent should run the standalone script from this skill directory:

bash

python -u ./scripts/article_content_extractor_api.py "https://blog.apify.com/what-is-web-scraping/" "5"

⏳ Running Status Monitoring

Since this task involves automated browser operations, it may take several minutes. The script continuously outputs timestamped status logs such as [14:30:05] Task Status: running. Agent guidelines:

• Keep monitoring terminal output while waiting for the script result.
• As long as new status logs appear, the task is running normally; do not mistake it for a deadlock or unresponsiveness.
• Only if the status remains unchanged for a long time or the script stops outputting without returning a result should you consider the retry mechanism.

📊 Data Output

After successful execution, the script retrieves and prints the BrowserAct API response. The returned data may include these fields:

• title: Extracted title value when available.
• author: Extracted author value when available.
• published_date: Extracted published date value when available.
• updated_date: Extracted updated date value when available.
• publisher: Extracted publisher value when available.
• article_text: Extracted article text value when available.
• summary: Extracted summary value when available.
• hero_image_url: Extracted hero image url value when available.
• tags: Extracted tags value when available.
• canonical_url: Extracted canonical url value when available.
• source_url: Extracted source url value when available.

Ground conclusions in the extracted data and handle missing fields gracefully.

⚠️ Error Handling & Retry

If an error occurs during script execution such as network fluctuations or task failure, the Agent should follow this logic:

1. Check Output Content:

   • If the output contains "Invalid authorization", it means the API Key is invalid or expired. Do not retry; guide the user to re-check and provide the correct API Key.
   • If the output contains "concurrent" or "too many running tasks" or similar concurrency limit messages, it means the current subscription plan's concurrent task limit has been reached. Do not retry; guide the user to upgrade their plan. Agent must inform the user:

     "The current task cannot be executed because your BrowserAct account has reached the limit of concurrent tasks. Please go to the BrowserAct Plan Upgrade Page to upgrade your subscription plan and enjoy more concurrent task benefits."

   • If the output does not contain the above error keywords but the task failed such as output starts with Error: or returns empty results, the Agent should automatically try to re-execute the script once.

2. Retry Limit:

   • Automatic retry is limited to one time. If the second attempt fails, stop retrying and report the specific error information to the user.

🌟 Typical Use Cases

1. Market research: Collect structured public records for quick analysis.
2. Competitive monitoring: Compare public products, listings, reviews, prices, or availability.
3. Dataset enrichment: Add clean fields to spreadsheets, CRMs, or BI workflows.
4. Lead generation: Identify relevant entities and URLs for downstream outreach.
5. Review analysis: Collect ratings and text signals where the template exposes review fields.
6. Pricing checks: Track current prices, total prices, or availability where supported.
7. Content research: Extract public text, metadata, or search results for editorial workflows.
8. Trend discovery: Find ranked or recent records around a destination, keyword, category, or source.
9. Operational reporting: Produce repeatable JSON output for scheduled reports.
10. API automation: Use BrowserAct workflow results as an input to other applications.