# Netdocuments Documents Info Parser Spider (`getdataforme/netdocuments-documents-info-parser-spider`) Actor The Netdocuments Documents Info Parser Spider is a web scraping tool that extracts detailed metadata from NetDocuments blog posts, including titles, publication dates, author details, and social media links.... - **URL**: https://apify.com/getdataforme/netdocuments-documents-info-parser-spider.md - **Developed by:** [GetDataForMe](https://apify.com/getdataforme) (community) - **Categories:** AI, Automation, E-commerce - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $9.00 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README *** ## README.md ### Netdocuments Documents Info Parser Spider #### Introduction The **Netdocuments Documents Info Parser Spider** is a powerful web scraping tool designed to extract detailed information from NetDocuments blog posts. It efficiently gathers data such as titles, publication dates, author details, and social media links, providing valuable insights for various applications. #### Features - **Comprehensive Data Extraction**: Captures essential metadata including title, date published, writer name, and more. - **High-Quality Output**: Ensures reliable and accurate data collection from NetDocuments blogs. - **Flexible Configuration**: Allows customization of URLs and item limits to suit specific needs. - **Efficient Performance**: Optimized for speed and resource management during scraping operations. - **User-Friendly Interface**: Easy setup with clear input parameters and straightforward execution. #### Input Parameters Table | Parameter | Type | Required | Description | Example | |--------------|----------|----------|-----------------------------------------------------------------------------|----------------------------------------------| | BlogUrls | array | Yes | The blog URLs for the spider. | `["https://www.netdocuments.com/blog/example"]` | | item\_limit | integer | No | Maximum items to scrape per actor run. Set to 0 for no limit. | `10` | #### Example Usage ##### Input JSON ```json { "BlogUrls": [ "https://www.netdocuments.com/blog/true-ai-search-vs-ai-assisted-querying/" ], "item_limit": 10 } ``` ##### Output JSON ```json [ { "category": "BLOG", "title": "True AI Search vs. AI-Assisted Querying", "date_published": "January 21, 2026", "writer_image": "https://www.netdocuments.com/wp-content/uploads/2026/01/jared-beckstead.webp", "writer_name": "Jared Beckstead", "designation": "Senior Product Marketing Manager", "document_details": "", "topics": [ "AI", "AI search" ], "social_media_links": { "linkedin": "https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fwww.netdocuments.com%2Fblog%2Ftrue-ai-search-vs-ai-assisted-querying%2F&title=True%20AI%20Search%20vs.%20AI-Assisted%20Querying", "facebook": "https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.netdocuments.com%2Fblog%2Ftrue-ai-search-vs-ai-assisted-querying%2F&title=True%20AI%20Search%20vs.%20AI-Assisted%20Querying", "x": "https://x.com/share?url=https%3A%2F%2Fwww.netdocuments.com%2Fblog%2Ftrue-ai-search-vs-ai-assisted-querying%2F&text=True%20AI%20Search%20vs.%20AI-Assisted%20Querying", "mail": "mailto:?subject=True%20AI%20Search%20vs.%20AI-Assisted%20Querying&body=True%20AI%20Search%20vs.%20AI-Assisted%20Querying%20\u2014%20https%3A%2F%2Fwww.netdocuments.com%2Fblog%2Ftrue-ai-search-vs-ai-assisted-querying%2F" }, "actor_id": "Wzf2SxRyL35GTEm4w", "run_id": "vr3kkHCL7yf3xqyvu" } ] ``` #### Use Cases - **Market Research and Analysis**: Extract insights from industry blogs to understand market trends. - **Competitive Intelligence**: Monitor competitors' blog content for strategic planning. - **Price Monitoring**: Track pricing strategies discussed in blog posts. - **Content Aggregation**: Compile relevant articles for newsletters or reports. - **Academic Research**: Gather data for studies on digital marketing and AI technologies. - **Business Automation**: Automate the collection of blog metrics for business analysis. #### Installation and Usage 1. Search for "Netdocuments Documents Info Parser Spider" in the Apify Store. 2. Click "Try for free" or "Run". 3. Configure input parameters as needed. 4. Click "Start" to begin extraction. 5. Monitor progress in the log. 6. Export results in your preferred format (JSON, CSV, Excel). #### Output Format The output is a JSON array containing objects with fields such as `category`, `title`, `date_published`, `writer_image`, `writer_name`, `designation`, `document_details`, `topics`, and `social_media_links`. Each object represents a blog post with its associated metadata. #### Support Section ### Support For custom/simplified outputs or bug reports, please contact: - Email: support@getdataforme.com - Subject line: "custom support" - Contact form: [Contact Us](https://getdataforme.com/contact/) We're here to help you get the most out of this Actor! *** # Actor input Schema ## `BlogUrls` (type: `array`): The blog urls for the spider. ## `item_limit` (type: `integer`): Maximum items to scrape per actor run. Set to 0 for no limit. ## Actor input object example ```json { "BlogUrls": [ "https://www.netdocuments.com/blog/true-ai-search-vs-ai-assisted-querying/" ], "item_limit": 10 } ``` # Actor output Schema ## `results` (type: `string`): Scraped data items from dataset # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("getdataforme/netdocuments-documents-info-parser-spider").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("getdataforme/netdocuments-documents-info-parser-spider").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call getdataforme/netdocuments-documents-info-parser-spider --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,getdataforme/netdocuments-documents-info-parser-spider" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/Wzf2SxRyL35GTEm4w/builds/PUAniUpeWxuEk5koN/openapi.json