The Archive · Desktop reference · Local API

Automations

Task templates that run on a schedule. 12 operations of the TALOS Desktop local API.

Reference for TALOS Desktop 0.1.25 generated from the source of the release · released

Task templates that run on a schedule. Paths are relative to /api/v1.

List the automations: tasks that run on a schedule.

Answers The JSON envelope.

Errors1
CodeStatusMeaning
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Create an automation: a task template that runs every so many minutes, with an optional daily limit and model.

Body

istruzioni
Not yet described.
modello
The model it runs with, as vendor/model-name.
coordinazione
Not yet described.
ripeti
Not yet described.
pianificazione
Not yet described.
taskIdrequired
The task template to start from: an id from GET /api/v1/tasks.
nome
A name for the automation.
intervalloMinutirequired
How often it runs, in minutes.
limiteAlGiorno
The most runs per day.

Answers The JSON envelope.

Errors2
CodeStatusMeaning
AUTOMATION_ORIGIN_FORBIDDEN 403 —
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Turn an automation on or off.

Path

automationId
The automation.

Body

attivarequired
true or false.

Answers The JSON envelope.

Errors2
CodeStatusMeaning
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

POST /automations/{automationId}/coordinazione

Section titled “POST /automations/{automationId}/coordinazione”

Not yet described in this reference: the parameters, fields and errors below are read from the release.

Path

automationId
The automation.

Body

coordinazione
Not yet described.

Answers The JSON envelope.

Errors2
CodeStatusMeaning
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Delete an automation.

Path

automationId
The automation.

Body

Answers The JSON envelope.

Errors2
CodeStatusMeaning
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Not yet described in this reference: the parameters, fields and errors below are read from the release.

Path

automationId
The automation.

Body

decisione
Not yet described.
modello
The model, as OpenRouter names it (vendor/model-name), or <provider>:<model> for a provider’s own endpoint; default: the server’s.
coordinazione
Not yet described.
ripeti
Not yet described.
pianificazione
Not yet described.
contesto
Not yet described.

Answers The JSON envelope.

Errors3
CodeStatusMeaning
INTERNAL_ERROR 500 An unexpected error on the server; the Doctor has the detail, under the reference shown.
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Not yet described in this reference: the parameters, fields and errors below are read from the release.

Path

automationId
The automation.

Body

decisione
Not yet described.
modello
The model, as OpenRouter names it (vendor/model-name), or <provider>:<model> for a provider’s own endpoint; default: the server’s.
coordinazione
Not yet described.
ripeti
Not yet described.
pianificazione
Not yet described.
contesto
Not yet described.

Answers The JSON envelope.

Errors3
CodeStatusMeaning
INTERNAL_ERROR 500 An unexpected error on the server; the Doctor has the detail, under the reference shown.
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Not yet described in this reference: the parameters, fields and errors below are read from the release.

Path

automationId
The automation.

Body

decisione
Not yet described.
modello
The model, as OpenRouter names it (vendor/model-name), or <provider>:<model> for a provider’s own endpoint; default: the server’s.
coordinazione
Not yet described.
ripeti
Not yet described.
pianificazione
Not yet described.
contesto
Not yet described.

Answers The JSON envelope.

Errors3
CodeStatusMeaning
INTERNAL_ERROR 500 An unexpected error on the server; the Doctor has the detail, under the reference shown.
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

POST /automations/{automationId}/runs/{runId}/letta

Section titled “POST /automations/{automationId}/runs/{runId}/letta”

Not yet described in this reference: the parameters, fields and errors below are read from the release.

Path

automationId
The automation.
runId
The workflow run.

Body

decisione
Not yet described.
modello
The model, as OpenRouter names it (vendor/model-name), or <provider>:<model> for a provider’s own endpoint; default: the server’s.
coordinazione
Not yet described.
ripeti
Not yet described.
pianificazione
Not yet described.
contesto
Not yet described.

Answers The JSON envelope.

Errors3
CodeStatusMeaning
INTERNAL_ERROR 500 An unexpected error on the server; the Doctor has the detail, under the reference shown.
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

POST /automations/{automationId}/runs/{runId}/proposta

Section titled “POST /automations/{automationId}/runs/{runId}/proposta”

Not yet described in this reference: the parameters, fields and errors below are read from the release.

Path

automationId
The automation.
runId
The workflow run.

Body

decisione
Not yet described.
modello
The model, as OpenRouter names it (vendor/model-name), or <provider>:<model> for a provider’s own endpoint; default: the server’s.
coordinazione
Not yet described.
ripeti
Not yet described.
pianificazione
Not yet described.
contesto
Not yet described.

Answers The JSON envelope.

Errors3
CodeStatusMeaning
INTERNAL_ERROR 500 An unexpected error on the server; the Doctor has the detail, under the reference shown.
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Not yet described in this reference: the parameters, fields and errors below are read from the release.

Path

automationId
The automation.

Answers The JSON envelope.

Errors2
CodeStatusMeaning
NOT_FOUND 404 Nothing answers at this address, or the resource it names does not exist.
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Not yet described in this reference: the parameters, fields and errors below are read from the release.

Answers The JSON envelope.

Errors1
CodeStatusMeaning
QUERY_INVALID 400 The request is not valid: a query parameter or a body field is missing, unknown or malformed.

Any operation can also answer the common errors.

Type to search the guides.