Use case: set up a weekend sale in two minutes

The workflow merchants automate first is almost always discounts. It's fiddly in the admin (collection, value, dates, limits, code) and it's exactly the kind of structured task agents nail. Here's the full flow with Shopigent.

The prompt

In Claude, Cursor, or Hermes:

Create a 20% discount code WEEKEND20 for the Hoodies collection,
valid Friday 00:00 to Sunday 23:59, one use per customer.

What the agent does

1. create_discount with dryRun: true — previews the discount document it would create. Nothing is written.

Worth knowing before you write the prompt: a discount cannot be limited to a collection through this app. create_discount builds a code with a percentage or a fixed amount; collection-scoped pricing is an admin job. Ask for the code and apply the collection limit yourself, or leave the code open to everything. 3. create_discount for real — and it lands in the audit log.

create_discount ships with its confirmation setting off, so this one goes straight through. Turn confirmation on for it in Curated Tools and the same call returns confirmation_pending until you approve it in the AI client, or on Confirmations with Approve or Decline.

What you see when the gate is on

Your AI client gets the confirmation request:

create_discount — WEEKEND20 · 20% · one per customer

You can approve in the client, or open Confirmations and choose Approve or Decline. Approve runs the tool only if the server check passes. Decline does not run it. The page does not show the token. This is not a dialog on every write.

Variations that work just as well

• "How is WEEKEND20 doing?" → get_discount (editing an existing discount is not a capability)
• "How did WEEKEND20 perform?" → list_orders gets you the orders, but it returns no discount attribution — that lives in your Shopify reports, not through this app
• "Kill the sale now" → delete_discount (confirmation again — deletes are gated by default, and you can turn that off per tool)

Why this beats doing it by hand

Not because clicking is hard — because the agent fills in the code, dates, and limits, and the audit log stores the call. If you turn confirmation on for create_discount, you review that one paused call before it runs.