← Back to library

Collect office snack requests in Slack and stage a cart

Agentic-commerce startup nekuda runs an OpenClaw assistant named Gila on an office machine, tagged in Slack. Its skill file tells it to collect what people ask for, merge it into one list, wait for an approver, fill a basket through the Instacart integration inside ChatGPT, report back in the channel and remember preferences. Payment stays manual.

  • OutcomeTurn teammates' grocery requests in a chat channel into a clean list, get it approved, and have an assistant build the delivery cart and post the link back.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditnekuda
View original
Works with
OpenClawChatGPT

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • Someone manually gathers snack requests each week
  • Your team already uses Slack
  • You want a human to approve spending

Not for: Purchases without approval; Large catering orders with dietary risks

What do you need, and what do you get?

You need

  • A chat channel for requests
  • An assistant with a shopping-app connection
  • A named approver

You get

  • A compiled shopping list
  • An approved cart link
  • Notes on preferences for next time

How does it work, step by step?

  1. Write the skillDescribe collect, compile, approve, build cart, post back, remember.
  2. Gather requestsLet teammates tag the assistant with what they want.
  3. Ask for approvalSend the compiled list to the authorized person before building the cart.
  4. Use a text-native appHave the assistant describe items to the shopping app rather than clicking a website.
  5. Report backDrop the basket link and a recap into the channel, then note what to do differently.

The prompt

Our own prompt, inspired by nekuda and written to work in OpenClaw and ChatGPT. Values in lime are placeholders.

Prompt0 variables
Each Thursday, collect grocery requests from #office in the last week. Combine duplicates into one list with quantities. Send it to [approver] and wait for a yes. Then fill an Instacart basket under $[cap] and share the link with a short recap in #office. Never pay. Save notes on substitutions and preferences for next time.

Inspired by nekuda: We Connected OpenClaw 🦞 with Instacart ChatGPT App - and Something Awesome Happened. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Browser-based shopping agents are slow and trip fraud checks; the authors found the app route steadier.
  • Removing the human payment step is tempting; keep it until the history is clean.

Our take

nekuda's office OpenClaw assistant Gila is a nicely scoped chore with spending controls in the right place. Tagged in Slack, it collects what people ask for, merges a list, waits for an approver, fills a basket through the Instacart integration inside ChatGPT, reports back in the channel and remembers preferences, while payment stays manual. The memory step is what makes it better over time, for example learning which brands people actually eat. Set a spending cap in the skill and have the assistant flag anything above it before asking for approval. The same pattern suits office supplies, coffee beans or event catering. Keep the approver list short and named. Prefer text-native shopping flows over brittle screen clicking when available. Review the preference memory quarterly so departed colleagues' favorites do not linger. Never store card details in the skill file. Confirm dietary restrictions in the channel before finalizing the cart. Share the staged basket in the channel so teammates can spot mistakes before checkout.

Where the time goes back: The weekly round of collecting, listing and ordering shrinks to an approval click.

FAQ

Who pays?
A person completes payment; the team keeps that step manual for now.
Why go through the ChatGPT app?
Describing items in plain text to the shopping app avoided brittle browser automation.

Source and credit

Inspired by nekuda. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
We Connected OpenClaw 🦞 with Instacart ChatGPT App - and Something Awesome Happened
Creator
nekuda
Published on
nekuda.substack.com (Substack)
Original date
Apr 9, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
OpenClaw
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks β†’

Related playbooks

Operations & AdminWorkflowβœ“ AI dry run

Write your needs down before building a DIY agent server

Before following an AI through a self-hosted assistant setup, list what you need, try hosted options first, and set a stop point so the project does not become a second job.

Credit: u/No-Star7003 on r/AI_Agents

Minutes
Operations & AdminWorkflowβœ“ AI dry run

Answer meeting-request emails with specific open times

Emails that ask for a meeting are spotted automatically and answered with concrete times that fit your calendar, with a buffer between meetings.

Credit: n8n Team (n8n-team)

Under an hour
Operations & AdminPromptβœ“ AI dry run

Audit what your agent assumes about you, with evidence

Ask your agent to list the preferences, limits and past choices it uses to shape its work for you, label each as something you said, something it inferred or of unknown origin, show where it came from and what it could change, then bring you the five that matter most so you can confirm, correct, narrow or delete them before it edits anything.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminWorkflowβœ“ AI dry run

Give Codex a research-folder instructions file

Open your research project folder in Codex, add a plain-language instructions file about role, standards, style and critique, and save every big result as a file.

Credit: Mushtaq Bilal, PhD (@MushtaqBilalPhD)

Under an hour
Operations & AdminWorkflowβœ“ AI dry run

Have AI double-check grading and add fuller feedback

Run a second review over work your TA already graded, catch missed issues, and give students fuller feedback before you post grades.

Credit: Panos Ipeirotis (@ipeirotis)

Under an hour