Skip to content
agentusehub

Pre-stage household grocery carts from Instacart history

An OpenClaw add-on scrapes Instacart order history, predicts what the household is running out of, fills the cart twice weekly and texts; nothing ships until the user taps Place Order.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

An OpenClaw add-on scrapes Instacart order history, predicts what the household is running out of, fills the cart twice weekly and texts; nothing ships until the user taps Place Order.

Reported experience

  1. What they did

    A nightly script imports each day's Instacart orders into a local SQLite database using Instacart's own item IDs, via a community CLI. A SQL analyzer takes the median days between purchases for each item and marks items due, soon, or not due. On Wednesday and Saturday at 7:45am, a script adds the due items to the cart by ID. At 8am it sends one iMessage. The CLI has no checkout action, so the user places the order.

  2. How it went

    Moving from an LLM clicking through the browser to canonical IDs took accuracy from eleven of fourteen items wrong on a typical run to 100%. The loop is fully deterministic, with no LLM in it.

  3. Worth knowing

    The earlier browser-clicking LLM version got most items wrong, so use item IDs rather than search. Setup is about 20 minutes, needs an active Instacart session, and the example scheduling uses macOS launchd.

Example prompts

Try with OpenClaw
Look at my [Instacart] order history, work out what my household is likely running low on, and fill a cart for [store] with those items twice a week. Text me a summary of the cart with quantities and the total. Don't place the order. Wait for me to confirm it.
Shopping & Errands

Call local stores to check toy stock

A writer used Gemini's calling feature to phone local stores about a Labubu figure and got text or email summaries of availability, price and hours.

Gemini