Prometheus

Query metrics, inspect targets, and manage alerts with the Prometheus HTTP API.

Detail	Value
Category	Monitoring
Base URL	https://prometheus.example.com/api/v1
Authentication	Basic Auth
Endpoints	8
Connector key	prometheus

Using Prometheus in a workflow

1. Go to Connections and click New Connection.
2. Pick Prometheus from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /query	Evaluate instant query
GET /query_range	Evaluate range query
GET /series	Find time series
GET /labels	List label names
GET /label/{label_name}/values	List label values
GET /targets	List targets
GET /rules	List rules
GET /alerts	List active alerts

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /query

Evaluate instant query

Detail	Value
Operation ID	monitoring.instantQuery
Method	GET
Path	/query

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prometheus connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.instantQuery.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prometheus API reference.

GET /query_range

Evaluate range query

Detail	Value
Operation ID	monitoring.rangeQuery
Method	GET
Path	/query_range

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prometheus connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.rangeQuery.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prometheus API reference.

GET /series

Find time series

Detail	Value
Operation ID	monitoring.findSeries
Method	GET
Path	/series

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prometheus connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.findSeries.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prometheus API reference.

GET /labels

List label names

Detail	Value
Operation ID	monitoring.listLabelNames
Method	GET
Path	/labels

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prometheus connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listLabelNames.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prometheus API reference.

GET /label/{label_name}/values

List label values

Detail	Value
Operation ID	monitoring.listLabelValues
Method	GET
Path	/label/{label_name}/values

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prometheus connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listLabelValues.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prometheus API reference.

GET /targets

List targets

Detail	Value
Operation ID	monitoring.listTargets
Method	GET
Path	/targets

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prometheus connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listTargets.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prometheus API reference.

GET /rules

List rules

Detail	Value
Operation ID	monitoring.listRules
Method	GET
Path	/rules

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prometheus connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listRules.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prometheus API reference.

GET /alerts

List active alerts

Detail	Value
Operation ID	monitoring.listAlerts
Method	GET
Path	/alerts

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prometheus connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listAlerts.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prometheus API reference.