Avnet Silica New Product Introductions Scraper

Monitor newly introduced electronic components on Avnet Silica and turn public launch pages into structured, export-ready data.

The Actor discovers products by supplier, market, technology, keyword, or publication date. It can also enrich known NPI URLs with technical overviews, variants, applications, benefits, development tools, evaluation boards, manufacturer links, and technical documents.

No Avnet account, browser, or proxy is required for this public NPI workflow.

What does the Avnet Silica NPI scraper do?

Avnet Silica publishes a large New Product Introductions catalog for engineers and component buyers.

This Actor automates that catalog:

• 🔎 discovers public NPI records from Avnet Silica's catalog
• 🏭 filters launches by supplier such as NXP or STMicroelectronics
• 🚗 filters records by market or technology taxonomy
• 📅 keeps only records newer than a chosen date
• 🧠 enriches each launch with its technical overview
• 🧰 extracts tools, software, and evaluation board links
• 📄 collects technical document names and URLs
• 🔗 accepts direct Avnet Silica NPI detail URLs
• 📦 exports results to JSON, CSV, Excel, XML, or RSS through Apify

Use list-only mode for a lightweight monitor, or detail mode when your downstream system needs engineering context.

Who is it for?

Electronics distributors can monitor supplier launch activity and update internal component catalogs.

Procurement teams can spot new alternatives and pass launch records into sourcing workflows.

Hardware engineers can collect applications, benefits, development tools, and technical PDFs before component evaluation.

Market intelligence teams can compare launch velocity across suppliers, markets, and technologies.

Component-content teams can ingest clean product-introduction records into PIM, search, newsletter, or research systems.

Automation developers can schedule repeat runs and trigger webhooks when new records appear.

Why use this Actor?

Avnet Silica's NPI page is designed for interactive browsing, not repeatable ingestion.

The Actor handles the underlying public CMS endpoint, pagination, entity decoding, URL normalization, detail extraction, retries, and dataset writes.

Benefits include:

• ⚡ HTTP-only execution without browser startup
• 🎯 exact Avnet Silica NPI scope rather than challenged Avnet Shop commerce pages
• 🧩 one consistent record shape for list-only and enriched workflows
• 🛡️ strict validation that rejects unrelated direct URLs
• 🔁 bounded retries and conservative detail concurrency
• 💳 pay-per-result billing with a small run-start charge

What Avnet Silica data can I extract?

Field	Description
title	New component or product-family title
supplier	Supplier inferred from the public manufacturer link when details are enabled
shortDescription	Catalog summary from the NPI listing
publicationDate	Normalized ISO publication timestamp
imageUrl	Absolute product-introduction image URL
detailUrl	Canonical Avnet Silica NPI detail URL
subtitle	Product-page technical subtitle
technicalOverview	Main technical narrative before application sections
variantsAndFeatures	Named family variants and their descriptions
applications	Application list from the detail page
benefits	Product benefits and capability bullets
toolNames	Development tools, software, kits, and evaluation boards
toolUrls	Links associated with tools and boards
manufacturerLinks	External manufacturer resources found in the technical content
documentNames	Technical document titles
documentUrls	Technical PDF and document URLs
scrapedAt	ISO timestamp for collection time

Optional fields are omitted when the source page does not publish them or when enrichment is disabled.

How to scrape Avnet Silica new components

1. Open the Actor input page.
2. Enter a supplier, market, technology, keyword, or direct NPI URL.
3. Choose the maximum number of product introductions.
4. Leave Include technical details enabled for engineering context.
5. Leave Include technical documents enabled to collect document links.
6. Click Start.
7. Preview the dataset while the run is active.
8. Export the records or connect an integration.

A small supplier-filtered input is the best first run.

Input parameters

Discovery filters

• supplier — exact public taxonomy label, such as NXP, STMicroelectronics, or Nordic Semiconductor
• market — exact market label, such as Automotive
• technology — exact technology label, such as Power
• keyword — case-insensitive title and short-description match
• publishedAfter — inclusive ISO date, for example 2026-01-01

Supplier, market, and technology filters can be combined.

Direct NPI URLs

Use startUrls when you already know the launch pages to collect.

Only URLs on my.avnet.com under /silica/products/new-products/npi/ are accepted.

When direct URLs are present, discovery filters are ignored.

Run controls

• maxItems — maximum dataset records, from 1 to 10,000
• includeDetails — visit technical detail pages
• includeDocuments — include document names and links during enrichment
• maxConcurrency — parallel detail requests, from 1 to 10

Keep concurrency conservative to protect reliability of the public CMS.

Example inputs

Monitor NXP launches

{
  "supplier": "NXP",
  "maxItems": 25,
  "includeDetails": true,
  "includeDocuments": true
}

Watch automotive introductions since 2026

{
  "market": "Automotive",
  "publishedAfter": "2026-01-01",
  "maxItems": 100,
  "includeDetails": true
}

Cheap list-only monitoring

{
  "technology": "Power",
  "maxItems": 50,
  "includeDetails": false
}

Enrich one known NPI page

{
  "startUrls": [
    { "url": "https://my.avnet.com/silica/products/new-products/npi/2026/stmicroelectronics-stm32g4/" }
  ],
  "maxItems": 1,
  "includeDetails": true,
  "includeDocuments": true
}

Example output

{
  "title": "STMicroelectronics STM32G4",
  "supplier": "Stmicroelectronics",
  "shortDescription": "The STM32G4 series combines...",
  "publicationDate": "2026-01-01T08:00:00.000Z",
  "detailUrl": "https://my.avnet.com/silica/products/new-products/npi/2026/stmicroelectronics-stm32g4/",
  "subtitle": "STM32G4 - Running at 170 MHz combined with three different hardware accelerators",
  "variantsAndFeatures": [
    "STM32G4x1 — Entry-level microcontrollers...",
    "STM32G4x3 — High-performance microcontrollers..."
  ],
  "applications": ["Motor control", "Industrial devices", "Digital power"],
  "toolNames": ["STM32CubeMX", "B-G431B-ESC1", "NUCLEO-G474RE"],
  "documentNames": ["STM32G4 series", "Reference manual"],
  "scrapedAt": "2026-07-19T00:00:00.000Z"
}

Actual optional fields depend on what each public NPI page contains.

How much does it cost to scrape Avnet Silica NPI data?

The Actor uses pay-per-event pricing:

• a small $0.005 start charge per run
• one NPI record event for each dataset item
• lower per-record rates on higher Apify plan tiers

The formula-calibrated BRONZE rate is $0.000089325 per record; FREE is $0.00010272, with deeper discounts on higher plan tiers.

A 25-record run at the BRONZE rate is approximately $0.0072 including the start event.

Apify's free usage credit may cover small monitoring workflows. Your exact cost is shown before and after every run.

List-only mode avoids detail requests, making it useful for frequent launch checks.

Scheduled component monitoring

Create an Apify schedule to run daily or weekly.

Use publishedAfter as a broad safety window, then deduplicate by detailUrl in your destination.

A typical workflow is:

1. run each morning for one supplier
2. export records to a named dataset, database, or spreadsheet
3. compare detailUrl values against previously seen launches
4. notify engineering or procurement only for unseen records

For many suppliers, create separate tasks so each alert has a clear source and owner.

Integrations and workflow patterns

Google Sheets: append launch records for procurement review and status tracking.

Make: trigger a scenario, filter by application, and create a product-intelligence card.

Zapier: send a Slack or email alert for every newly observed detailUrl.

Webhooks: start document ingestion after a successful run.

Dataset API: load normalized records into a PIM, data warehouse, or internal search index.

Cloud storage: export technical document URLs for a separate approved download pipeline.

A useful engineering workflow is to route records containing evaluation boards to a prototype backlog while sending production-focused parts to sourcing.

JavaScript API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/avnet-silica-new-product-introductions-scraper').call({
  supplier: 'NXP',
  maxItems: 25,
  includeDetails: true,
  includeDocuments: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Never hard-code production API tokens in source control.

Python API example

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/avnet-silica-new-product-introductions-scraper').call(run_input={
    'market': 'Automotive',
    'publishedAfter': '2026-01-01',
    'maxItems': 50,
    'includeDetails': True,
})

for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item['title'], item['detailUrl'])

Use environment variables or your secret manager for credentials.

cURL API example

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~avnet-silica-new-product-introductions-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "technology": "Power",
    "maxItems": 20,
    "includeDetails": false
  }'

After the run succeeds, fetch items from its defaultDatasetId through the dataset API.

Use with Apify MCP

Connect Claude Code with this exact command:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/avnet-silica-new-product-introductions-scraper"

For Claude Desktop, Cursor, or VS Code, add this HTTP server configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/avnet-silica-new-product-introductions-scraper"
    }
  }
}

Example prompts:

• "Find the five newest NXP introductions on Avnet Silica and summarize their applications."
• "Collect automotive components launched since January 2026 and list their evaluation boards."
• "Extract the technical documents linked from this Avnet Silica NPI URL."

Data quality and reliability

The list endpoint is parsed defensively because it advertises a text/html content type while returning JSON.

URLs and HTML entities are normalized before records are saved.

Duplicate detail URLs are removed within a run.

Transient requests are retried with short backoff.

If one detail page uses an unusual legacy template, the Actor retains its valid list record instead of losing the entire batch.

A malformed or unavailable listing endpoint fails the run rather than silently reporting incomplete success.

Tips for better results

• ✅ Copy taxonomy labels exactly as Avnet Silica displays them.
• ✅ Start with 5 records while validating a new workflow.
• ✅ Disable details for frequent low-cost change detection.
• ✅ Enable details only after a monitor detects unseen URLs.
• ✅ Use direct URLs when enriching a curated component shortlist.
• ✅ Treat publication dates as source-provided CMS timestamps.
• ✅ Deduplicate scheduled exports by detailUrl.
• ⚠️ Do not submit Avnet Shop URLs; commerce pages are outside this Actor's scope.

Limitations

This Actor covers the public my.avnet.com/silica/products/new-products/ catalog only.

It does not scrape Avnet Shop price, stock, lead time, cart, account, or availability data.

Older NPI pages may omit publication dates or use different technical section labels.

Supplier names on direct-URL runs depend on links published by the detail page.

Keyword matching applies to list titles and short descriptions, not full enriched page text.

The source can change its CMS structure without notice. Review logs and samples when a previously working taxonomy suddenly returns no matches.

Is scraping Avnet Silica legal?

The Actor accesses anonymous public product-introduction and technical-resource pages.

Scraping legality depends on your jurisdiction, purpose, volume, contractual obligations, and downstream use.

Use reasonable schedules and concurrency. Do not collect personal data, bypass access controls, or republish third-party documents without the necessary rights.

You are responsible for complying with Avnet's terms, manufacturer document licenses, copyright rules, and applicable law.

This documentation is operational guidance, not legal advice.

Troubleshooting

Why did my taxonomy filter return no records?

Check spelling and capitalization against Avnet Silica's current filter list. The source endpoint expects its own taxonomy labels.

Try the same run without that filter to distinguish a label mismatch from a source outage.

Why are technical fields missing?

Confirm includeDetails is true. Some older source pages publish only a short launch description and links.

The Actor omits unavailable optional fields instead of inventing values.

Why was my direct URL rejected?

Only Avnet Silica NPI URLs under /silica/products/new-products/npi/ are accepted. Avnet Shop, manufacturer, category, and unrelated URLs fail closed.

What should I inspect after an error?

Open the run log, note the failing URL and HTTP status, then retry once with a smaller input. Persistent listing-shape errors may indicate an upstream CMS change.

FAQ

Does it require an Avnet account?

No. The supported NPI catalog and detail pages are public.

Does it use a browser or proxy?

No. It uses direct HTTP against the proven public CMS surfaces.

Can I monitor one manufacturer?

Yes. Set supplier to the exact public taxonomy label and create a schedule.

Can I extract technical PDFs?

The Actor extracts document names and URLs. It does not download or redistribute document binaries.

Can I combine supplier, market, and technology?

Yes. The values are sent together to Avnet Silica's public filter endpoint.

Can I search the full technical overview by keyword?

Not in v1. Keyword filtering targets the catalog title and short description before detail enrichment.

How many records are available?

The live source count changes. During implementation discovery, Avnet Silica exposed 1,004 public NPI rows.

Can I scrape prices and stock?

No. Those belong to the separate Avnet commerce surface and are intentionally outside this product.

Related scrapers

• Google Search Scraper — discover broader manufacturer announcements and technical coverage.
• Robots.txt Generator — create robots policies for sites you operate.

Choose this Actor when the required entity is an Avnet Silica new product introduction with engineering context.

Support

If a run fails, share the Apify run URL through the Actor's Issues tab.

Include the input mode, one example NPI URL or filter value, and what output you expected.

Do not include API tokens, account credentials, or confidential BOM data.

For source-specific changes, a reproducible public URL helps us validate and restore extraction quickly.