Schedules and triggers

A capability can run without anyone clicking Run — on a schedule, or on a trigger. Either way the run is recorded like any other, marked Schedule or Trigger, and acts as the person who created it: with their access, counted on the workspace’s runs.

Schedules

On the capability’s page, Schedules → Add schedule: a name, when (every hour, every day at 9:00, weekdays at 9:00, every Monday — or any 5-field cron), a timezone, and the inputs (the capability’s own form). Runs are at least 5 minutes apart and follow the timezone’s clock, daylight saving included.

curl -X POST https://api.reminix.com/v1/capabilities/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

Triggers → Add trigger: the event (any workspace event — another capability’s run.completed or run.failed, capability.published, a member joining…), optionally only when a field of the event equals a value, and the inputs. A value {{event.data.<field>}} is taken from the event:

{
  "name": "Alert on failure",
  "eventType": "run.failed",
  "filter": { "capability.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…) stops after 3, so a capability can never trigger itself forever.

Who can, and when they stop

• Anyone who may run a capability can schedule or trigger it — as themselves. Its creator, or a workspace owner or admin, changes or deletes it. For a capability whose every run needs approval, only owners and admins can (they are the approvers).
• They are created by a person — 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 cannot (there is no person to act as).
• If its creator leaves the workspace or loses access to the capability, a schedule or trigger is switched off, and its card says why. Switch it back on (or recreate it) as someone who has access.
• If a run is refused before it starts (no published version, inputs that no longer fit a new version), that time is skipped; the schedule stays on.