Skip to content

Out of stock substitute offer with customer accept link

When an order contains an item you cannot ship, the agent proposes a discounted in stock substitute and emails the customer an accept or reject link. The run pauses until they answer, then the order is swapped or refunded.

Ecommerce and resaleWorks with LangGraph · n8n+1Community example
Build your promptSee requirements

What it does

  • Checks each new order for fraud risk and stock
  • Picks a comparable in stock item and a discount
  • Drafts the offer email with two links
  • Pauses the order until the customer clicks
  • Logs every step for audit

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Sending the offer email
  • Issuing any refund
  • Orders flagged for fraud review

You decide what happens next.

More about this workflow

This setup is for online sellers and resale shops juggling listings, orders and buyers. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it checks each new order for fraud risk and stock. Next, it picks a comparable in stock item and a discount. Then it drafts the offer email with two links. After that, it pauses the order until the customer clicks. Finally, it logs every step for audit. It works with your store admin, email and database, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before sending the offer email, issuing any refund and orders flagged for fraud review, and says plainly if a step cannot be undone.

“the agent does not cancel the order”
HamzaAli2002 HamzaAli2002 on GitHub · Sep 15, 2026
Before you startStore admin · Email accessScoped permissionsLangGraph or n8n
Explore required tools and model recommendations

Tools and access

  • Shopify

    Handles the store admin part of this job. Grant read orders and products.

    API required: Yes. Needs a Shopify app with an access token and the admin scopes you approve.

    Sign up: Shopify

  • Gmail

    Handles the email part of this job. Grant read-only plus compose (drafts) scopes.

    API required: Yes. Needs a Google Cloud project with an OAuth app and the Gmail API turned on. The agent signs in through OAuth with only the scopes you pick.

    Sign up: Google Workspace

  • Supabase

    Handles the database part of this job. Grant a role limited to one table.

    API required: Yes. Needs a Supabase project and an API key. Give the agent a role limited to one table.

    Sign up: Supabase

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Gemini 3.8 Flash

Built for agent workflows, with a free tier to test on.

$0.75 per million input tokens and $3.75 per million output tokens through December 31, 2026. $1.50 and $7.50 from January 1, 2027.

Google docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for many listings at once.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

same category, price band

percent off the substitute

2Your prompt

4 of 4 still empty
Fill these in before you run it: [STORE OR ORDER DATABASE] [SUBSTITUTE RULES: same category, price band] [DISCOUNT: percent off the substitute] [FRAUD RISK CUTOFF] You are the Out of stock substitute offer with customer accept link agent. When an order contains an item you cannot ship, the agent proposes a discounted in stock substitute and emails the customer an accept or reject link. The run pauses until they answer, then the order is swapped or refunded. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Checks each new order for fraud risk and stock - Picks a comparable in stock item and a discount - Drafts the offer email with two links - Pauses the order until the customer clicks - Logs every step for audit What you must never do without a yes from a person: - Sending the offer email - Issuing any refund - Orders flagged for fraud review Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: LangGraph, n8n, OpenAI Agents SDK

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Shopify with its own login, not yours. Grant read orders and products.
  2. 2Connect Gmail with its own login, not yours. Grant read-only plus compose (drafts) scopes.
  3. 3Connect Supabase with its own login, not yours. Grant a role limited to one table.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: sending the offer email, issuing any refund, orders flagged for fraud review.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Out of stock substitute offer with customer accept link](https://trustcase.dev/badge/out-of-stock-substitute-offer-with-customer-accept-link.svg)](https://trustcase.dev/use-cases/out-of-stock-substitute-offer-with-customer-accept-link)
HTML
<a href="https://trustcase.dev/use-cases/out-of-stock-substitute-offer-with-customer-accept-link"><img src="https://trustcase.dev/badge/out-of-stock-substitute-offer-with-customer-accept-link.svg" alt="Trustcase trust score for Out of stock substitute offer with customer accept link" height="20"></a>

More ecommerce and resale workflows

Other workflows that use the same tools

  • Weekly CRM health report

    Sales. Every Monday it checks the CRM for duplicates, missing fields and stuck deals, compares with last week and writes a short report. Numbers come from queries, not the model.

  • Weekly KPI summary with number checks

    Operations. Every Monday an agent writes the short management summary on supplier and delivery performance. It only sees data through read only tools, a control chart sets the traffic light, code checks every number and a person approves before it goes out.

  • Daily media briefing with cited sources

    Marketing. Reads about a thousand news items a day for a communications team and drafts a briefing where every claim links to its source. A named analyst approves it before anyone senior sees it, and high risk stories trigger an alert within 15 minutes.