Use cases
Each of these starts as a script someone already has. Reminix lets you choose who runs it and how, and it records every run.
Let AI agents act, with a person in the loop
Jordan in support wants to ask Claude to refund $40 to a customer who paid twice. Someone should check before the money goes out.
How it's set up. Connect the agent to Reminix once. Every script you can run is a tool it can call by name. Then make agents' runs of refund-customer wait for an owner or admin to approve them. The script carries the team's own rules. A refund over $500 needs a manager, and used credits come off the refund.
Refund $40 on order A-10423. The customer paid twice.
Used Reminix
refund_customer
The $40.00 refund for A-10423 is waiting for approval. Once someone approves it, the refund goes out in Stripe. The script then updates the ticket and emails the customer.
Waiting for approval: refund-customer, order A-10423, $40.00
Runbooks your support team can run
An engineer has a script that unlocks a customer's account after too many sign-in attempts. Support needs it several times a day, and today they ask in a channel and wait.
How it's set up. Publish the script to Reminix and share it with the Support team only. They get a form, and the admin key stays in Reminix.
Unlock an account
Run
Customer email jane@example.com
Reports on a schedule
On the first of every month, someone pulls last month's revenue out of Stripe into a spreadsheet for Finance. When they're away, it waits.
How it's set up. Give the report's script a schedule for 8:00 on the 1st of each month, in your timezone. Reminix records each run like any other, and the CSV the script writes comes back as a file to download.
await reminix.schedules.create("monthly-report", {
name: "First of the month",
cron: "0 8 1 * *",
timezone: "Europe/London",
}); reminix.schedules.create(
"monthly-report",
name="First of the month",
cron="0 8 1 * *",
timezone="Europe/London",
) Syncs and batch jobs that take minutes
The nightly sync copies the day's orders from the shop to the warehouse. It takes minutes, so it lives on one person's laptop. Nobody else can see whether it ran or why it failed.
How it's set up. Give the script a longer timeout. Long runs need Pro or Business, up to 10 or 15 minutes. The run returns right away and shows its log and progress as it goes. You can cancel it while it runs.
for i, page in enumerate(pages, 1):
sync_page(page)
print(
f"::progress {i * 100 // len(pages)} Page {i} of {len(pages)}",
file=sys.stderr,
)
print(json.dumps({"pages": len(pages)})) Follow up when something fails
When the nightly sync fails, someone should see the error before customers notice.
How it's set up. Publish an alert-on-failure script and give it a trigger. When a run of the sync fails, the trigger runs the alert with that run's id and error.
{
"type": "event",
"name": "Alert on failed sync",
"event": "run.failed",
"filter": { "script.slug": "nightly-sync" },
"inputs": {
"runId": "{{event.data.runId}}",
"error": "{{event.data.error}}"
}
} Run a script when another service calls
A customer disputes a $40 charge. Someone sees Stripe's email the next morning, looks the charge up and accepts the dispute by hand.
How it's set up. Give the script a webhook trigger that checks Stripe's signature, and add its URL in Stripe. Each dispute starts a run with Stripe's event. With approval on, a person approves it before any money moves.
{
"type": "webhook",
"name": "Stripe dispute",
"inputMode": "request",
"signature": "stripe",
"signingSecret": "whsec_…"
} Something else?
If you have a script for it, Reminix can probably run it. Tell us what you need, or read how scripts work. Using another tool for this today? See how Reminix compares.
Start free. Free for 500 runs a month. No card needed.