Two systems — coupons and workflows — chained into one campaign.
I want a welcome programme for new customers. Part one: a 5% coupon with the code WELCOME5, for all customers and all products, valid until 2026-12-31, active. Part two: whenever a new customer registers, they automatically get an email containing exactly that code. The two parts have to match — the code in the email must be the one you actually created, so create the coupon first and use the stored code in the mail. Switch the automation on and read both parts back from the shop to confirm. Show me the email text you wrote.
Read back from the database, the rendered storefront and the local mail sink. No model involved.
| Result | Check | Weight |
|---|---|---|
| PASS | Coupon WELCOME5 exists in tkupon kKupon=2149 name="Willkommensgutschein" |
3 |
| PASS | WELCOME5 discounts 5% (cWertTyp=prozent) fWert=5 cWertTyp=prozent |
3 |
| PASS | WELCOME5 is active and valid through 2026-12-31 cAktiv=Y dGueltigBis=2026-12-31 00:00:00 |
2 |
| PASS | A workflow was created on a trigger matching customer/kunde/regist created: #3956 newCustomer → sendMail |
3 |
| PASS | That workflow is active isActive=1 |
2 |
| PASS | Its action is an e-mail action action=sendMail |
2 |
| PASS | The workflow email body contains the WELCOME5 code code embedded in workflow arguments |
3 |
Scored by opus, which saw only the evidence bundle.
| Criterion | Score | Reason | |
|---|---|---|---|
correctnessBoth artefacts exist with the requested values and reference the same code. |
8/10 | state_diff.json shows tkupon 2149 WELCOME5 5% prozent cAktiv=Y bis 2026-12-31 and workflow 3956 newCustomer→sendMail isActive=1 whose body carries the identical literal WELCOME5, so both artefacts exist with the asked-for values and one shared code. | |
chainingThe coupon was created first and its stored code was carried into the mail, rather than both being written from the prompt independently. |
6/10 | Order was right and the code was checked free first (call 9 run_sql_read on tkupon, then create at call 12, workflow at call 13), but the mail body was written with the literal string WELCOME5 from the prompt — the SELECT * FROM tkupon WHERE kKupon = 2149 readback (call 14) came after the workflow already existed, so nothing was actually carried from the stored row. | |
copy_qualityWelcome mail reads like a real shop, states the discount and how to use it. |
6/10 | The stored body "Hallo {$customer->cVorname}, ... Dein Gutscheincode lautet: <b>WELCOME5</b>" is correct German with a real first-name placeholder and clean HTML breaks, but it is bare-bones: no redemption instructions, no validity date, no link to the shop. | |
communicationReports both parts and how they are linked. |
7/10 | ANSWER.md reports coupon terms and the automation in two clear sections and quotes the exact mail text as asked, but never names the trigger/workflow, and asserts the link only as "beide Einstellungen ausgelesen und geprüft" rather than showing the readback matched. |
It recovered from three separate argument-shape errors (query vs sql, arguments vs args, kHersteller[] vs kHersteller) without giving up or inventing success, then re-read both objects from the shop.
The coupon code in the mail was typed from the prompt, not taken from the stored row — the coupon readback happened after the workflow was already written, so the chaining the owner explicitly asked for was ordering only, not data flow.
| Tool | Calls | Errors | Avg |
|---|---|---|---|
describe_admin_action | 3 | 0 | 366 ms |
run_sql_read | 3 | 1 | 329 ms |
invoke_admin_action | 3 | 1 | 435 ms |
list_admin_actions | 2 | 0 | 446 ms |
describe_workflow_capabilities | 2 | 0 | 310 ms |
create_workflow | 1 | 0 | 246 ms |
get_workflow | 1 | 0 | 486 ms |
Hallo! Das Willkommensprogramm für neue Kunden ist jetzt eingerichtet und aktiv. ### 1. Der Gutschein Ich habe einen **5% Rabattgutschein** mit dem Code **WELCOME5** angelegt. * Er gilt für alle Kunden und alle Artikel. * Kein Mindestbestellwert. * Gültig bis zum 31.12.2026. * Der Gutschein ist ab sofort aktiv. ### 2. Die Automatisierung Ich habe einen Workflow erstellt, der **automatisch bei jeder Neukundenregistrierung** ausgelöst wird. Der neue Kunde erhält umgehend eine E-Mail mit folgendem Inhalt: **Betreff:** Willkommen! Dein 5% Gutschein **Inhalt:** > Hallo [Vorname des Kunden], > > willkommen in unserem Shop! Als kleines Dankeschön erhältst du 5% Rabatt auf deinen nächsten Einkauf. Dein Gutscheincode lautet: **WELCOME5** > > Viele Grüße > Dein Shop-Team *(Hinweis: Der Platzhalter für den Vornamen wird beim Versand automatisch durch den echten Namen ersetzt, und die E-Mail nutzt das Standard-Layout deines Shops.)* Ich habe beide Einstellungen im System abschließend ausgelesen und geprüft. Das Programm ist wie gewünscht live und funktionsfähig!
This model was driven from outside the harness (runner external), which reports no token usage. Its work is likewise covered by that tool's own subscription.
Billed separately, per API call, and only if the automation the assistant set up calls an LLM while it runs. The deliverables in this benchmark are native JTL Shop objects — coupons, workflows, mail templates, storefront copy — which the shop executes without a model. This harness records no runtime telemetry, so no figure is shown rather than a made-up one.
Run 20260811-110753_f-welcome-program_gemini-pro-3.1 · shop reset to fixture before the run · restore with jtl restore 20260811-110753_f-welcome-program_gemini-pro-3.1
© 2026 the author · scores are generated from recorded runs, not written by hand.
