How we handle GDPR data-subject requests on a deadline
Legal
People request snacks through a Slack shortcut, and an agent batches the requests weekly, prepares an order, and posts it for the office manager to approve before placing anything.

Keeping an office stocked is a small recurring chore that never quite has an owner. Requests come in over Slack, hallway conversations, and sticky notes; the office manager reconciles them into an order; and half the time a request is forgotten by the time the order goes in. It's low-stakes, but it's steady work.
We handle it with an agent on Kortix. People request snacks through a Slack shortcut, and once a week the agent batches every request, prepares an order, and posts it for the office manager to approve. Nothing is placed until a person signs off.
Snack requests arrive one at a time and out of band. Someone asks in a channel, someone else mentions it in passing, and the office manager is left assembling a list from memory. Requests get dropped, duplicates slip through, and the order goes in later than it should.
The task is simple but constant. It needs one place to collect requests, a way to batch them on a schedule, and a person's sign-off before any money is spent — none of which a shared spreadsheet or a recurring calendar reminder actually provides.
Requests come in through a Slack shortcut, so there's one place to submit them. Once a week a cron trigger spawns an isolated session that collects the week's requests, prepares an order against the ordering account, and posts the draft in Slack for the office manager to approve. Only after approval does it place anything.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the snack batching skill and the weekly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a weekly office snacks agent in this workspace.
Create the agent agents/office-snacks.md. Its job is to batch the week's snack requests into one draft order for the office manager to approve. It may read and post in #office through Slack, and it uses the ORDERING_ACCOUNT_API_KEY secret for the ordering account.
Create the skill skills/snack-batching/SKILL.md with these rules:
Add a cron trigger weekly-snack-batch to kortix.yaml. It runs the office-snacks agent every Monday at 08:00 with the prompt "Load the snack-batching skill and run this week's snack-batching pass."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect Slack. Credentials are
brokered server-side and never enter the agent's machine. Then add your
ordering account's API key as the ORDERING_ACCOUNT_API_KEY secret, granted
to this agent only.
Collects requests and posts the draft order for approval.
Builds the cart within budget and orders only after approval.
Merge the change request, then start a session with the office-snacks agent and send this prompt. Check the cart and the total before you let the schedule take over.
Run this week's snack-batching pass in #office.
The change request added this trigger to kortix.yaml. From now on the agent
runs every Monday at 08:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: weekly-snack-batch name: Weekly snack batch on: cron: "0 0 8 * * 1" run: agent: office-snacks prompt: Load the snack-batching skill and run this week's snack-batching pass.The draft post is the only output of the weekly run. The agent checks out only after the office manager writes an explicit approval in the draft's thread. Silence, an emoji or a question is not approval. When the thread is still open at the next weekly run, its items roll into the new batch instead of a stale order.
Each run ends with one draft order in the channel. This is what a run looks like in the session:
Collected 14 requests and merged them into 8 lines, plus the 3 standing staples. The cart totals $138.40 against the $150 budget. Nothing is purchased until the office manager approves in the thread.
Once it works, paste any of these into the same session.
Once a month, list every item requested in three or more weeks and propose it as a standing staple in a change request.
Mark each line in the draft order as vegan, gluten-free or contains nuts when the vendor listing says so.
After an order is placed, post in #office on the morning it is due to arrive, with the list of what is coming.
Because the agent can prepare an order that spends money, the controls matter even for a small chore:
Requests stop getting lost, duplicates get consolidated, and the office manager reviews a finished order instead of assembling one. The spending step stays behind a person, so the automation saves the busywork without ever placing an order on its own.