Triggers
Set up
Section titled “Set up”npm install @reminix/sdkimport { createClient } from "@reminix/sdk";
const reminix = createClient(); // reads REMINIX_API_KEYpip install reminixfrom reminix import Reminix
reminix = Reminix() # reads REMINIX_API_KEYnpm install -g @reminix/clireminix loginexport REMINIX_API_KEY="<your API key>"List a script’s triggers
Section titled “List a script’s triggers”GET /v1/scripts/{slug}/triggers
The events that start it.
await reminix.triggers.list("alert-on-failure");reminix.triggers.list("alert-on-failure")reminix triggers list alert-on-failurecurl -X GET "https://api.reminix.com/v1/scripts/alert-on-failure/triggers" \ -H "Authorization: Bearer $REMINIX_API_KEY"| Field | Description |
|---|---|
slug |
Run a script on an event
Section titled “Run a script on an event”POST /v1/scripts/{slug}/triggers
Starts a run, as you, when an event of eventType happens in the workspace (GET /v1/workspace/event-types lists them) and its data matches filter — within about a minute.
await reminix.triggers.create("alert-on-failure", { name: "Nightly sync failed", eventType: "run.failed",});reminix.triggers.create( "alert-on-failure", name="Nightly sync failed", event_type="run.failed",)reminix triggers create \ alert-on-failure \ --name 'Nightly sync failed' \ --event-type run.failedcurl -X POST "https://api.reminix.com/v1/scripts/alert-on-failure/triggers" \ -H "Authorization: Bearer $REMINIX_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name":"Nightly sync failed","eventType":"run.failed"}'| Field | Description |
|---|---|
slug | |
name | A name for the trigger, shown in the app. |
eventType | The event that starts a run: any webhook event type, such as run.failed. |
filter | Event data fields (dotted paths) that must equal these values. |
inputs | The script's inputs for each run, by name; a value "{{event.data.<path>}}" takes it from the event. |
environment | The environment its runs use. Default: the request's (X-Environment), else the workspace's default. |
More about this endpoint
A chain of triggered runs stops after 3.
Change a trigger
Section titled “Change a trigger”PATCH /v1/scripts/{slug}/triggers/{triggerId}
Its name, filter, inputs, or switch it on or off.
await reminix.triggers.update("alert-on-failure", "<trigger-id>");reminix.triggers.update("alert-on-failure", "<trigger-id>")reminix triggers update alert-on-failure '<trigger-id>'curl -X PATCH "https://api.reminix.com/v1/scripts/alert-on-failure/triggers/<trigger-id>" \ -H "Authorization: Bearer $REMINIX_API_KEY" \ -H "Content-Type: application/json" \ -d '{}'| Field | Description |
|---|---|
slug | |
triggerId | |
name | A name for the trigger, shown in the app. |
filter | Event data fields (dotted paths) that must equal these values. |
inputs | The script's inputs for each run, by name; a value "{{event.data.<path>}}" takes it from the event. |
enabled | Whether it fires. Default: true. |
environment | Move its runs to another environment. |
More about this endpoint
Its creator, or an owner or admin.
Delete a trigger
Section titled “Delete a trigger”DELETE /v1/scripts/{slug}/triggers/{triggerId}
Its creator, or an owner or admin.
await reminix.triggers.delete("alert-on-failure", "<trigger-id>");reminix.triggers.delete("alert-on-failure", "<trigger-id>")reminix triggers delete alert-on-failure '<trigger-id>' --yescurl -X DELETE "https://api.reminix.com/v1/scripts/alert-on-failure/triggers/<trigger-id>" \ -H "Authorization: Bearer $REMINIX_API_KEY"| Field | Description |
|---|---|
slug | |
triggerId |