Schedules and triggers

A script can run without anyone clicking Run: on a schedule, or on a trigger. Either way, Reminix records the run like any other, marked Schedule or Trigger. It acts as the person who created the schedule or trigger, with their access, and counts toward the workspace’s runs.

Schedules

On the script’s page, choose Schedules → Add schedule. Give it a name and say when to run: every hour, every day at 9:00, weekdays at 9:00, every Monday, or any 5-field cron. Then choose a timezone, and fill in the inputs with the script’s own form. Runs are at least 5 minutes apart and follow the timezone’s clock, including daylight saving time.

curl -X POST https://api.reminix.com/v1/scripts/nightly-report/schedules \
  -H "Authorization: Bearer $REMINIX_TOKEN" -H "X-Workspace: acme" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Weekday mornings", "cron": "0 9 * * 1-5",
        "timezone": "Europe/Berlin", "inputs": { "team": "sales" } }'

Triggers

Choose Triggers → Add trigger. Pick the event: any workspace event, such as another script’s run.completed or run.failed, script.published, or a member joining. Optionally, run only when a field of the event equals a value. Then set the inputs. A value written as {{event.data.<field>}} comes from the event:

{
  "name": "Alert on failure",
  "eventType": "run.failed",
  "filter": { "script.slug": "nightly-report" },
  "inputs": { "runId": "{{event.data.runId}}", "error": "{{event.data.error}}" }
}

A trigger starts its run within about a minute of the event. A chain of triggered runs (a run whose completion triggers another, and so on) stops after 3, so a script can never trigger itself forever.

Who can, and when they stop

• Anyone who may run a script can schedule or trigger it, as themselves. Its creator, or a workspace owner or admin, can change or delete it. For a script whose every run needs approval, only owners and admins can, since they’re the approvers.
• A person creates schedules and triggers, in the app or with a person’s token. An AI agent can list them, but asks you to create them. A workspace API key can’t create them, because there’s no person to act as.
• If its creator leaves the workspace or loses access to the script, Reminix switches the schedule or trigger off, and its card says why. Switch it back on, or recreate it, as someone who has access.
• If Reminix refuses a run before it starts, it skips that time and the schedule stays on. Its card shows the last time it was skipped and why: for example, no published version, inputs that no longer fit a new version, or the plan’s runs for the month used up.