Give dealer website URLs, get the vehicles each dealer currently lists for sale on its own website, one row per vehicle (VIN, year, make, model, trim, price, mileage, specs, dealer location, link) plus one status row per dealer. Covers franchise and independent car dealers on 21 website platforms, RV dealers on Interact RV, Inventrue and Coast Technology, truck dealers on iManPro, the DriveTime, Camping World, Rush, SelecTrucks, Ryder, Velocity and TEC chains, and other sites that publish standard schema.org vehicle data. Data comes from the dealers' own public websites; this app is not an official product of any dealer or website provider
Lowe's Keyword Search
Give a Lowe's search keyword, expected count, and sort to get public product search listings with title, brand, category, rating, and product links.
Original · en-USVolver a la traducción
Descripción general
Retail and brand teams that watch Lowe's usually make assortment and share-of-search calls from the same product card a shopper sees: title, brand, category, rating, review count, and the product page. This app turns one public Lowe's search keyword into a structured table of those listings so category reviews, competitor scans, and catalog matching can start from storefront search instead of a one-off screenshot.
Each row keeps the Search keyword beside the SKU ID, SPU ID, Model ID, and Product URL, so later comparisons stay attached to the query that produced them. Rating and Review count stay in the source text, and Product status is kept as the original listing label. It is a search-listing workbook, not a substitute for a full product detail page, inventory position, or variant matrix.
Data notes
Each row is one public Lowe's keyword search listing for the submitted Search keyword and Sort order. The same SKU ID is kept once in the returned set. Listings are returned in collection order. Product status is the source label as shown on the card, including values such as 在售. Rating and Review count remain source text rather than normalized numbers. Collected at is returned without a timezone; Source created time is a Unix millisecond timestamp when present. Alternate image, Item number, and Source collect time may be empty on a listing card. Search keyword, Business ID, and Task keyword repeat the search context across rows from the same query. A No-data flag distinguishes a search that produced no listings from ordinary product rows.
The collection does not cover private seller tools, warehouse inventory, fulfillment data, or product-detail fields that are not visible on public Lowe's search.
What a result looks like
Each row is one Lowe's search listing.
| Product title | SKU ID | Brand | Rating | Product URL | Search keyword |
|---|---|---|---|---|---|
| HP3600Plus+500X 3600 -Watts Portable Power Station (1 Solar Panel Included) | 5017225957 | Jackery | 0 | https://www.lowes.com/pd/Jackery-Jackery-Solar-Generator-3600-Plus-with-1-Solar-Panel-500W/5017225957 | Jackery |
| SolarSaga 200W 91.3-in x 21.2-in x 1-in 200-Watt Portable Solar Panel | 5015759393 | Jackery | 4.7 | https://www.lowes.com/pd/Jackery-Solar-Panels-200W/5015759393 | Jackery |
Category, Review count, and Product image are also available when the card shows them.
Use cases
- For assortment scans, group rows by Search keyword and Brand, then read Product title and Category to see which products occupy the first results for that query.
- For reputation checks, compare Rating and Review count to separate well-reviewed SKUs from unrated or thinly reviewed cards.
- For catalog matching, join SKU ID, SPU ID, Model ID, and Product URL to an internal product list and keep the Product image for visual QA.
Alcance y límites
One keyword search per task with an expected result count from 1 to 240; results are returned in complete batches of 24 and may be rounded up; coverage is limited to public Lowe's keyword search listings.
- Adecuada para
- When you need public Lowe's product search listings for one keyword and sort order.
- When you need to compare product titles, brands, categories, ratings, review counts, and product links from search cards.
- No usar para
- When you need a full product detail page, inventory, fulfillment, or variant matrix beyond the search card.
- When you need an immediate single-record lookup rather than a background keyword collection task.
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 1If no products are returned, confirm the keyword can be searched on public Lowe's, then retry with a broader brand or product phrase.
- 2Keep completed records after a partial success; resubmit the same input after a failed or expired task.
- 3Retry later after rate limiting, temporary unavailability, or a timeout.
- 4If authentication fails, verify the API Key configured for the execution environment.
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
- Search keyword
keywordObligatoriostringProduct, brand, or phrase to search on Lowe's. Each task accepts one keyword from 1 to 512 characters.EjemploJackery - Expected result count
expected_countObligatoriointegerExpected number of product listings from 1 to 240; results come back in complete batches of 24, so the actual count may be rounded up and a partial batch is still billed as 24 listings.Rango1–240Ejemplo1 - Sort order
sort_orderOpcionalstring(enum)How Lowe's should rank the search listings. Default is Default; choose Best selling, a price order, Most popular, or Highest rated when you need a different ranking.Valores permitidosDefault0Best selling2Price: low to high51Price: high to low52Most popular6Highest rated11Predeterminado0
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Alternate image
alternate_image_urlstringBackup product image URL from the search card; empty when the source does not return one.Ejemplohttps://mobileimages.lowes.com/productimages/3c276865-0b5a-4a89-b625-8f995c1382bd/73741189.jpeg - Business ID
biz_idstringBusiness identifier attached to the search record; in the current shape this repeats the search keyword.EjemploJackery - Brand
brand_namestringProduct brand name shown on the Lowe's search card; empty when the source does not return one.EjemploJackery - Category ID
category_idstringLowe's category identifier for the listing; empty when the source does not return one.Ejemplo107784
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"alternate_image_url": "https://mobileimages.lowes.com/productimages/3c276865-0b5a-4a89-b625-8f995c1382bd/73741189.jpeg",
"biz_id": "Jackery",
"brand_name": "Jackery",
"category_id": "107784",
"category_name": "SOLAR_GENERATORS",
"crawl_time": "2026-09-11T19:08:13",
"image_url": "https://mobileimages.lowes.com/productimages/26fcd8db-042f-4987-91c3-07b4477fafb7/73741094.jpeg",
"item_number": "<item_number>",
"keyword": "Jackery",
"model_id": "60-360050-US00073",
"product_title": "HP3600Plus+500X 3600 -Watts Portable Power Station (1 Solar Panel Included)",
"product_url": "https://www.lowes.com/pd/Jackery-Jackery-Solar-Generator-3600-Plus-with-1-Solar-Panel-500W/5017225957",
"rating_score": "0",
"review_count": "0",
"sku_id": "5017225957",
"source_collect_time_ms": 0,
"source_created_at_ms": 1789124892867,
"spu_id": "5017225957",
"status_code": "在售",
"task_item": "Jackery",
"no_data": false,
"vendor_number": "110974"
}Integración
Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino. Esta App se ejecuta de forma asíncrona y se puede cancelar a mitad de camino: Tras la cancelación, la ejecución se detiene. Los registros ya entregados se conservan y se facturan.
Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.
Configuración del cliente
Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/lowes-keyword-search",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Deja que la IA lo configure por ti
¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (De forma predeterminada te guía para iniciar sesión y nunca te pide que envíes tu API Key en el chat.)
detail.access.mcp.composeHint
Precios
Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran. Se factura en unidades de 24 registros; cualquier unidad parcial se redondea a 24 registros.
Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.
Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.
Ver créditosPruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.