🛒 Flipkart Seller for n8n

Run your Flipkart shop on autopilot. Connect your seller account to WhatsApp, Slack, Google Sheets, Shopify, your ERP or your accountant — and let the boring parts happen by themselves.

No code. No API knowledge. Just pick what you want to do and fill in two or three fields.

58 operations · 10 sections · 3 nodes · 0 dependencies

🌟 Key Features

🪄 Simple Mode on Every Screen

Every operation opens with two or three plain-English fields and sensible defaults. Want today's unpacked orders? Set Show to Waiting to be packed and Time Range to Today. That's the whole setup — the node works out Flipkart's filter types, state codes, date formats and paging for you.

Need the full control panel? Flip the Advanced switch. Nothing you already filled in is lost.

🏷️ One-Click Pack & Ship

Select Pack & Ship (All Steps) and a single node does the entire pre-dispatch run:

• Generates the shipping label and GST invoice
• Waits while Flipkart builds them (usually 5–10 seconds)
• Downloads the PDF, ready to save or print
• Marks the order ready for courier pickup

Auto invoice numbering: leave it on Auto-Generate and you get INV-2627-00001, INV-2627-00002… counting up correctly across the Indian financial year.

📦 Bulk Updates Straight from a Spreadsheet

Point Update Stock or Change Price at your Google Sheet columns and hit go.

• Auto-batching: Flipkart only accepts 10 products per request — the node splits your rows automatically.
• Per-row results: every SKU comes back with its own success or failure, so one bad row doesn't hide the other forty.
• Plain-English summary: "42 updated, 3 failed: TSHIRT-118: listing does not exist"
• 🧪 Dry Run: see exactly what would be sent, without sending a thing.

🔔 Real-Time Order Alerts — Two Ways

• Push (Flipkart Seller Trigger): Flipkart tells you the instant an order lands. Needs a one-off support ticket to register your address.
• Polling (Flipkart Seller Poll Trigger): works everywhere, zero setup. Checks on your schedule for new orders, state changes, new returns, updated returns or finished reports.

Not sure which? Start with polling. It needs nothing from Flipkart's support team and it doubles as a safety net if a pushed message ever goes missing.

📄 Real PDFs, Not Just Data

Everything printable comes out as a proper file you can save to Drive, email, or send to a printer:

• 🏷️ Shipping labels — with invoice, label-only, or raw thermal-printer format
• 🧾 GST invoices — as a PDF, or as line-item data
• 📋 Courier manifests — the handover sheet for pickup
• 📊 All 15 Flipkart reports — settlements, GST returns, orders, returns, inventory, profit & loss

📊 Reports Without the Waiting Around

Pick Download Report, choose Last month, done. The node requests it, waits while Flipkart builds it (these can take minutes), then hands you the finished file.

Window checks run first: ask for 5 months of profit & loss and you get "the Profit and Loss report allows at most 31 days per request" — before the call is made, not as a cryptic error afterwards.

🛡️ Smart Error Protection

• Pre-send checks: missing warehouse ID, backwards date ranges, empty orders and over-long report windows are caught before the request goes out.
• Never repeats a dangerous action: if the connection drops mid-dispatch or mid-cancel, the node stops and tells you rather than risking doing it twice.
• Keeps what worked: turn on Continue On Fail and one bad row won't throw away the fifty that succeeded.
• Errors that tell you what to do next: "Reconnect your Flipkart credential", not HTTP 401.

🧪 Practise Safely First

Switch a credential to Sandbox and the whole node points at Flipkart's practice system. The Sandbox Testing section lets you invent test orders and push them through every stage — shipped, delivered, returned — without touching a real customer.

Move to live by swapping the credential. Nothing else changes.

🤖 Ready for AI Agents

The node is usableAsTool, so an n8n AI Agent can act on "show me orders that must ship today" or "set stock of TSHIRT-118 to zero".

🚀 How to Install in n8n

The easy way — Settings → Community Nodes → Install → paste:

n8n-nodes-flipkart-seller

Or from the command line:

npm install n8n-nodes-flipkart-seller

Requires n8n v1+ on Node 20.15 or newer.

🔑 Connect Your Flipkart Account

1. Get your keys from Flipkart
Seller Hub → Help → API → register an application. Flipkart gives you an Application ID and an Application Secret. Treat the Secret like a password.

2. Add them to n8n
Credentials → Add credential → Flipkart Seller API. Paste both in, leave Environment on Production, save. n8n tests the connection immediately — a green tick means you're done.

3. Save yourself typing (optional but worth it)
Paste your warehouse code into Default Location ID and you'll never have to enter it again on any screen. Find it at Seller Hub → Manage Profile → Business Details.

Which credential do I pick?
Flipkart Seller API is for sellers running their own shop — that's almost certainly you. Flipkart Seller OAuth2 API is only for agencies managing shops on behalf of other sellers, and needs a partnership approval from Flipkart first.

⚡ Your First Workflow

1. Add a Flipkart Seller node
2. Resource → Order, Operation → Find Orders
3. Show → Waiting to be packed, Time Range → Today
4. Click Test step

Today's unpacked orders appear on the right. Hook a Slack, WhatsApp or Gmail node after it and you'll be told about them automatically.

💬 Turn on Add Summary Line under Options and each order arrives as one readable sentence:

Order OD4321 · 2 items · INR 1,299 · dispatch by Fri 12 Sep 6 PM

📚 What You Can Do

🛒 Orders

🏷️ Stock & Prices

📮 Returns

Find Returns · Approve · Reject · Mark Picked Up · Record Failed Pickup · Mark Received · Cancel

Plus Return Handover for when a Flipkart field agent scans returns at your warehouse.

🧰 Everything Else

Self-Ship Order (orders you post yourself) · Service Visit (installations and engineer visits) · Report (all 15) · Notifications (Flipkart's alerts on/off) · Account (connection health) · Sandbox Testing

🎁 Ready-Made Workflows

Five complete workflows ship inside the package, each with a sticky note listing the two things to change. Find them at node_modules/n8n-nodes-flipkart-seller/templates/ and import via Workflows → Import from File.

📖 Flipkart Words, Explained

🩺 If Something Goes Wrong

💡 Tip: turn on Continue On Fail (node → Settings) so one bad row can't stop the rest. Failed rows come back with an error field explaining why.

🔒 Your Data & Security

• Your Flipkart Secret is write-once. It never appears in error messages, logs or workflow output.
• Customer addresses and phone numbers are hidden by default. Turn Simplify off only if you genuinely need the delivery address.
• Report files download without your Flipkart key attached — those files live on separate storage, and the key doesn't belong there.
• Irreversible actions are never auto-repeated. A dropped connection mid-dispatch stops and reports, rather than risking a double send.
• Webhook messages are verified — signature-checked, replay-protected, and re-confirmed against Flipkart directly rather than trusting what was pushed.
• One credential per seller if you manage several shops, then use n8n's sharing settings to control access.
• ⚠️ n8n stores everything a workflow produced in its execution history. If yours handle customer details, check n8n's execution-pruning settings.
• ⚠️ Attaching this to an AI Agent gives the AI every operation — including cancelling orders and changing prices.

⚠️ Known Limits

Being straight with you:

• Some write formats are built from Flipkart's written docs, which are dated in places — specifically label generation, return decisions, and creating/updating listings. They follow what's documented, but weren't confirmed against a live account. If one is rejected, every such screen has a Body (JSON) box under Options to send the exact format Flipkart wants, without waiting for an update.
• The agency/partner login (OAuth2) is untested end to end — it needs a Flipkart partnership approval. The normal seller login is unaffected.
• Not included: Flipkart's older order system (superseded), FTP bulk upload (not an API), and Flipkart Ads.

Something not covered? Both credentials also work in n8n's plain HTTP Request node — choose Predefined Credential Type → Flipkart. That reaches any part of Flipkart's system, using the same saved login.

🧑‍💻 For Developers

npm install
npm run build     # compile TypeScript + copy icons
npm test          # jest — 97 tests
npm run lint      # n8n community-node rules
npm run dev       # tsc --watch

Local install: npm run build && npm link, then npm link n8n-nodes-flipkart-seller inside ~/.n8n/custom, restart n8n.

Zero runtime dependencies. Signature checking uses Node's built-in crypto; all HTTP goes through n8n's authenticated request helper.

Layout: nodes/FlipkartSeller/actions/<resource>/ holds one module per resource (UI description + handlers); actions/router.ts maps resource + operation to a handler; transport/ owns auth, base URLs, retries and error shaping; helpers/ covers pagination, batching, IST dates, polling and output shaping.

Tests cover what's easy to get wrong: forged, stale and replayed webhook requests; report links pointing at internal addresses; path traversal through IDs; non-GET requests never re-sent after an ambiguous failure; repeating pagination cursors; per-SKU batching with duplicates; and error messages staying free of secrets.

📄 Licence

MIT