zomato-order

Automate Zomato food orders by driving the browser with saved session cookies.

364|53|Updated May 9, 2026

Search Tags:#browser automation #playwright #food ordering #session cookies #zomato #payment link #checkout workflow

Ready to run

npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill zomato-order

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: zomato-order
Source: https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/shop-restaurant/zomato-order
Command: npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill zomato-order

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, chromium, node.js, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of placing Zomato orders without a public API by automating the browser-based ordering flow in a way that avoids repeated OTP logins.

Core Features & Use Cases

Two-phase cookie-based automation: run a one-time setup to capture login cookies, then reuse them for subsequent orders.
Browser-driven order creation: restores a logged-in session, helps you browse restaurants, build a cart, and reach the payment stage.
Payment link handoff: captures and shares the payment URL so you can complete payment yourself, reducing risk of handling payment credentials.
Use case: when you want lunch or dinner delivered regularly, set up once and then repeatedly place orders with minimal effort while the user confirms payment.

Quick Start

Say: "Order food from Zomato" and the Skill will run setup if no cookies exist, then proceed to the payment page and share the payment link for you to complete payment.

Frequently Asked Questions about zomato-order

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate food ordering on Zomato without a public API?▼

Automate Zomato food ordering by driving the browser with Playwright. The workflow uses a two-phase flow to save session cookies during setup, then restores them to build a cart and reach the payment page automatically.

Can I use Playwright to avoid repeated OTP logins for recurring Zomato orders?▼

Yes, Playwright avoids repeated OTP logins by capturing session cookies during a one-time manual setup. These saved cookies are reused to restore the logged-in session for subsequent automated checkout workflows.

How does browser automation handle the checkout workflow for food delivery?▼

Browser automation handles the checkout workflow by restoring saved session cookies, navigating the restaurant menu to build the cart, and driving the browser to the payment page to capture a payment URL.

Do I need to provide payment credentials to automate the Zomato checkout process?▼

No, you do not provide payment credentials to automate the Zomato checkout process. The automation stops at the payment page, captures the payment URL, and hands it off for you to complete the transaction manually.

What is the best way to set up recurring food delivery automation with Node.js?▼

The best way to set up recurring food delivery automation with Node.js is running a one-time setup flow that saves login cookies to a file, then executing a script that reuses that session to place orders automatically.

Why does the Zomato order automation stop at the payment page?▼

Zomato order automation stops at the payment page to securely hand off the payment URL. Capturing the payment link for manual completion reduces the risk of handling sensitive payment credentials during the browser-driven workflow.