Flipkart Scraper - Scrape Flipkart Products & Prices
Pricing
from $2.00 / 1,000 results
Flipkart Scraper - Scrape Flipkart Products & Prices
Flipkart scraper: search any keyword & extract product name, price, MRP, discount, ratings, reviews & images. Export to JSON/CSV/Excel.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
Techforce Global
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
5 days ago
Last modified
Categories
Share
Flipkart Search Scraper & MCP Connector
Scrape any Flipkart search — exactly like typing in the search bar — and get clean, structured product data: title, current price, MRP, discount %, rating, ratings & reviews count, F-Assured badge, image, and product URL. No login, no cookies, no paid proxies required.
Built for price-monitoring teams, e-commerce analysts, and sellers who need an accurate product list for a keyword in seconds — not an afternoon of copy-pasting from Flipkart.
Type a search term → optionally pick a category → get a structured product feed → deliver it straight into Notion, Slack, Jira, or your own tools.
⭐ Why This Actor?
- ✅ Just enter a search query — no LinkedIn-style logins, no session tokens, no manual browsing
- ✅ Search bar parity — whatever you'd type into Flipkart's search box works here (
wireless earbuds,nike running shoes,samsung 5g phone) - ✅ Optional category filter — narrow to Mobiles, Laptops, Electronics, Fashion, Home, Beauty, Books & more, or search everything
- ✅ Sort like the site — relevance, popularity, price low→high / high→low, or newest first
- ✅ Detailed output — price, MRP, computed discount %, star rating, ratings & reviews counts, F-Assured flag, image, and canonical product URL
- ✅ JavaScript-ready & anti-bot resilient — drives a real headless Chromium browser (Playwright), so it reads Flipkart's dynamically-rendered results reliably
- ✅ Auto-pagination — set how many products you want and it walks the result pages for you
- ✅ Deliver anywhere via MCP connectors — push products straight into Notion, Slack, Jira, GitHub, Linear, Airtable, and more
- ✅ Export-ready — JSON, CSV, Excel, or direct API integration for your BI tool, sheet, or CRM
📝 Use Cases & ROI
| Use Case | Time Saved | What You Get |
|---|---|---|
| Price & discount monitoring | 2–5 hrs/week | A repeatable price/MRP/discount feed for any keyword or category |
| Competitor benchmarking | 3–6 hrs/analysis | How rival products rank, cost, and rate for a search term |
| Catalog & assortment building | 4–8 hrs/batch | Hundreds of products for a keyword, ready to import |
| Deal & offer tracking | 2–4 hrs/week | Top discounts and F-Assured listings, sorted and filtered |
| Market & demand research | 2–5 hrs/study | Ratings volume & review counts as a proxy for product demand |
🚀 How to Use
- Open the Actor on Apify (or run it locally with the Apify CLI)
- Enter the Search query you want — the text you'd type into Flipkart's search bar (e.g.
wireless earbuds) - (Optional) Pick a Category to narrow results, or leave it as Any
- Set Maximum products — how many to collect (the Actor paginates automatically)
- (Optional) Choose a Sort order and adjust Max concurrency
- (Optional) Pick an MCP connector to deliver the products into Notion, Slack, Jira, etc.
- Click Run — results are ready in minutes
- Download as CSV, Excel, or JSON — or let the connector push the products into your tools automatically
🎯 Category filter: well-known categories (Mobiles, Laptops, Home & Furniture, Books) use Flipkart's internal store IDs for precise scoping; the rest refine the query by keyword. Leave it on Any for the widest, most robust search.
🌐 No proxy needed: the headless browser reads public search-results pages directly. On the Apify platform you can optionally enable Apify Proxy in the run options for extra resilience — it is not required.
🐢 Getting blocked or empty results? Lower Max concurrency to
1, or set Run browser headless tofalselocally to watch what Flipkart returns.💡 First time with a connector? Run once with a connector selected — the run log prints the connector's available tool names, so you know what to put in Connector tool name.
🧩 Input Configuration
| Field | Type | Required | Description |
|---|---|---|---|
searchQuery | String | ✔️ Yes | The text you'd type into the Flipkart search bar (e.g. wireless earbuds). |
category | Enum | Optional | Narrow the search to a top-level category, or Any to search everything. Default: Any. |
maxProducts | Integer | Optional | Maximum number of products to collect (1–2000). The Actor paginates until reached. Default: 50. |
sortBy | Enum | Optional | relevance, popularity, price_asc, price_desc, recency_desc. Default: relevance. |
maxConcurrency | Integer | Optional | Search-result pages processed in parallel (keep 1–3 to stay gentle on Flipkart). Default: 2. |
headless | Boolean | Optional | Run the browser without a visible window. Keep true on the platform. Default: true. |
mcpConnector | Connector | Optional | An MCP connector to deliver results into (Notion, Slack, Linear, Airtable, Jira, GitHub…). Leave empty to save to the dataset only. See 🔗 Deliver to Your Tools below. |
deliveryMode | Enum | Optional | perProduct (one call per product), summary (one call with the whole list), or none. Default: perProduct. |
mcpTool | String | Optional | Name of the tool to call on the connector (e.g. create_page, send_message, create_issue, appendRow). |
mcpArguments | Object | Optional | JSON arguments passed to the tool. String values support {placeholders} (see table below). |
mcpMessageTemplate | String | Optional | Optional template rendered and exposed as the {message} placeholder inside mcpArguments. |
Category options: Any · Mobiles · Laptops · Electronics · TVs & Appliances · Men's Fashion · Women's Fashion · Home & Furniture · Beauty & Grooming · Sports & Fitness · Books · Toys & Baby · Grocery · Automotive
Example — Just search Flipkart
{"searchQuery": "wireless earbuds","maxProducts": 50}
Example — Search within a category, cheapest first
{"searchQuery": "gaming laptop","category": "Laptops","sortBy": "price_asc","maxProducts": 100}
Example — Track the most popular deals in a category
{"searchQuery": "running shoes","category": "Men's Fashion","sortBy": "popularity","maxProducts": 200,"maxConcurrency": 2}
📦 Output Fields
Each product is stored as one dataset item:
| Field | Description |
|---|---|
productId | Flipkart listing id (from the tile's data-id) |
title | Product name |
url | Absolute link to the product page |
image | Product thumbnail URL |
currentPrice | Current selling price (INR) |
originalPrice | Struck-through MRP (INR), when shown |
discountPercent | Discount vs MRP, computed automatically |
currency | Always INR |
rating | Average star rating (0–5) |
numRatings | Number of ratings |
numReviews | Number of reviews |
fAssured | Whether the listing shows the Flipkart Assured badge |
seller | Seller name if present on the card (best-effort — see note) |
Example Output
[{"productId": "ACCGH8ZZABCDEFGH","title": "boAt Airdopes 141 with 42H Playtime, Bluetooth 5.1","url": "https://www.flipkart.com/boat-airdopes-141/p/itm...","image": "https://rukminim2.flixcart.com/image/300/300/...jpeg","currentPrice": 1299,"originalPrice": 4490,"discountPercent": 71,"currency": "INR","rating": 4.3,"numRatings": 458210,"numReviews": 32567,"fAssured": true,"seller": null}]
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
ℹ️ Note on
seller: Flipkart shows the seller name on the product detail page, not on search cards, so this field is usuallynullin search output. Prices, discounts, ratings, reviews, and F-Assured are read directly from the results. Need guaranteed seller names, specs, and offers? See Custom Pipeline below.
🔗 Deliver to Your Tools (MCP Connectors)
Beyond the dataset, this Actor can push every scraped product straight into your own tools through an MCP connector — Notion, Slack, Linear, Airtable, Jira, GitHub, Google Sheets, or any MCP-compatible server you've authorized on Apify. No glue code, no separate Zap.
How it works
- In the input, pick a connector under Deliver to (MCP connector) — Apify injects your authorized credentials at runtime; the Actor never sees them.
- Choose a Delivery mode:
perProduct— one tool call per product (e.g. one Notion page or one Slack line per item)summary— a single call containing the whole product listnone— save to the dataset only
- Set the Connector tool name (
mcpTool) — the tool to invoke on the connector. - Fill in Connector tool arguments (
mcpArguments) — a JSON object whose string values support{placeholders}. - (Optional) Write a Message template (
mcpMessageTemplate), exposed as{message}inside your arguments.
The dataset is always saved regardless of connector settings — delivery problems never discard scraped data.
Available placeholders
perProduct mode — per-product values plus shared search context:
| Placeholder | Meaning |
|---|---|
{productId} | Flipkart listing id |
{title} | Product name |
{url} | Product page link |
{image} | Thumbnail URL |
{currentPrice} | Current selling price |
{originalPrice} | Struck-through MRP |
{discountPercent} | Discount vs MRP |
{currency} | Always INR |
{rating} | Star rating (0–5) |
{numRatings} | Number of ratings |
{numReviews} | Number of reviews |
{seller} | Seller name (usually empty on search cards) |
{fAssured} | Flipkart Assured flag |
{searchQuery} | The search query used |
{category} | The category filter used |
{count} | Total products scraped |
{message} | The rendered Message template |
summary mode — {searchQuery}, {category}, {count}, {message}, and {products} (a markdown list of every product).
Example — one Slack message per product
{"searchQuery": "wireless earbuds","maxProducts": 20,"mcpConnector": "<your-slack-connector>","deliveryMode": "perProduct","mcpTool": "send_message","mcpMessageTemplate": "*{title}* — ₹{currentPrice} ({discountPercent}% off) | ⭐ {rating}\n{url}","mcpArguments": { "channel": "#deals", "text": "{message}" }}
Example — one summary message with the full list
{"searchQuery": "gaming laptop","category": "Laptops","maxProducts": 25,"mcpConnector": "<your-slack-connector>","deliveryMode": "summary","mcpTool": "send_message","mcpMessageTemplate": "Top {count} results for *{searchQuery}*:\n\n{products}","mcpArguments": { "channel": "#research", "text": "{message}" }}
Example — one Notion page per product
{"searchQuery": "air fryer","maxProducts": 30,"mcpConnector": "<your-notion-connector>","deliveryMode": "perProduct","mcpTool": "create_page","mcpArguments": {"parent": { "database_id": "<your-database-id>" },"properties": {"Name": { "title": [{ "text": { "content": "{title}" } }] },"Price": { "number": "{currentPrice}" },"Rating": { "number": "{rating}" },"URL": { "url": "{url}" }}}}
💡 Not sure of the tool name or its argument shape? Run once with a connector selected — the log lists the connector's available tools. Then set
mcpTooland shapemcpArgumentsto match.
🔌 Integrations & Delivery
Because it runs on Apify, the product feed drops straight into your stack — no glue code:
- Apify API — pull the dataset as JSON/CSV/Excel on demand
- Google Sheets / Airtable — append rows automatically
- Zapier, Make & n8n — trigger downstream workflows on each run
- Webhooks — notify your service the moment a run finishes
- MCP connectors — push products directly into Notion, Slack, Linear, Jira, GitHub & more (see 🔗 Deliver to Your Tools above)
- Scheduling — run daily/weekly to build a price-history time series
Consume it however your BI, pricing, or merchandising tools prefer.
💰 Cost Estimation — How much does it cost to scrape Flipkart?
The Actor uses a headless browser, so cost scales with the number of search-result pages loaded (~24 products per page). Scraping a few hundred products typically costs a small fraction of an Apify compute unit. To keep runs cheap:
- Set a realistic
maxProducts— don't over-fetch - Keep
maxConcurrencyat2–3 - Add a
categoryand/orsortByso the most relevant results come first
⚡ Tips & Advanced Options
-
Category accuracy: category mappings live in
my_actor/main.py(CATEGORY_FILTERS). Well-known categories use Flipkart store IDs (sid); others append a keyword. If Flipkart changes a store ID, edit that dictionary. -
Resilient parsing: Flipkart rotates its CSS class names, so the parser anchors on the stable
data-idproduct tile and uses attribute/structural/regex fallbacks — it keeps working through cosmetic markup changes. -
Run locally:
pip install -r requirements.txtplaywright install chromiumapify run --purge -
Deploy to Apify:
apify loginapify push
🆘 Support
For issues, custom scraping requests, or feature suggestions:
Email: bhavin.shah@techforceglobal.com
Found a field that stopped populating? Flipkart likely changed its markup — open the Issues tab so it can be updated quickly.
Need a Custom Pipeline?
Want per-product deep enrichment (seller, full specs, bank offers, delivery & stock), multi-keyword batch runs, or a price-history database with alerts?
📅 Book a Free 15-min Consultation
Made with ❤️ by Techforce Specialists in High-Performance Web Scrapers and AI Automation.
Disclaimer
This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Flipkart. Flipkart® and Flipkart Assured® are trademarks of their respective owners; all trademarks are property of their respective owners. The Actor collects only publicly available information from Flipkart's public search-results pages and does not log into, or scrape behind the authentication of, any account. Use the data responsibly and in compliance with applicable laws (including GDPR/CCPA where relevant) and Flipkart's Terms of Service.