List Jobs
cortex.list_jobs
ActionBusiness appsconnection required
Calls the Cortex API with the connection's credentials.
List the jobs the connection's user can see, newest first.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Cortex
- Secret shape
- the Cortex organisation API key, or {"api_key": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
data_type_filter Only return jobs whose observable had this data type, such as ip. | string | No | — | — | — |
data_filter Only return jobs whose observable matches this value. | string | No | — | — | — |
analyzer_filter Only return jobs run by this worker, named by its Cortex id. | string | No | — | — | — |
range How much of the result set to return, as a Cortex range window: '0-49' for the first fifty, or 'all' for every match. Leave it blank for Cortex's own default page. | string | No | — | — | 0-49 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"range": "0-49"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The jobs, exactly as Cortex returned them. | array | — |
count How many jobs this response carried. | number | — |
{
"count": 0,
"items": []
}See List Jobs run in a workflow.
In a technical demo we add the Cortex connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.