Documentation

Create a task

Create tasks with the InfluxDB user interface (UI), influx command line interface (CLI), or /api/v2 API.

Before creating a task, review the basics for writing a task.

Create a task in the InfluxDB UI

The InfluxDB UI provides multiple ways to create a task:

Create a task from the Data Explorer

  1. In the navigation menu on the left, select Data Explorer.

  2. Build a query and click Save As in the upper right.

  3. Select the Task heading.

  4. Specify the task options. See Task options for detailed information about each option.

  5. Click Save as Task.

Create a task in the Task UI

  1. In the navigation menu on the left, select Tasks.

  2. Click Create Task in the upper right.

  3. In the left panel, specify the task options. See Task options for detailed information about each option.

  4. In the right panel, enter your task script.

    Leave out the option tasks assignment

    When creating a new task in the InfluxDB Task UI, leave the code editor empty. When you save the task, the Task UI uses the task options you specify in the Task options form to populate option task = {task_options} for you.

    When you edit the saved task, you’ll see the injected option task = {task_options}.

  5. Click Save in the upper right.

Import a task

  1. In the navigation menu on the left, select Tasks.

  2. Click Create Task in the upper right.

  3. In the left panel, specify the task options. See Task options for detailed information about each option.

  4. Paste a raw Flux task in the code editor to the right of the task options fields.

  5. Click Save in the upper right.

Create a task from a template

  1. In the navigation menu on the left, select Settings > Templates.

  2. Find the template you want to use and click its Resources list to expand the list of resources.

  3. In the Resources list, click the task you want to use.

Clone a task

  1. In the navigation menu on the left, select Tasks.

  2. Find the task you would like to clone and click the icon located far right of the task name.

  3. Click Clone.

Create a task using the influx CLI

Use the influx task create command to create a new task. It accepts either a file path or raw Flux.

Create a task using a file

# Syntax
influx task create --org <org-name>  -f </path/to/task-script>

# Example
influx task create --org my-org -f /tasks/cq-mean-1h.flux

Create a task using raw Flux

influx task create --org my-org - # <return> to open stdin pipe

option task = {
  name: "task-name",
  every: 6h
}

# ... Task script ...

# Linux & macOS: <ctrl-d> to close the pipe and submit the command
# Windows: <enter>, then <ctrl-d>, then <enter> to close the pipe and submit the command

Create a task using the InfluxDB API

Use the /api/v2/tasks InfluxDB API endpoint to create a task.

POST http://localhost:8086/api/v2/tasks/

Provide the following in your API request:

Request headers
  • Content-Type: application/json
  • Authorization: Token INFLUX_API_TOKEN
Request body

JSON object with the following fields:

  • flux: raw Flux task string that contains a task option and a query.
  • orgID: your InfluxDB organization ID
  • status: task status (“active” or “inactive”)
  • description: task description
curl --request POST 'http://localhost:8086/api/v2/tasks' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Token INFLUX_API_TOKEN' \
  --data-raw '{
    "flux": "option task = {name: \"CPU Total 1 Hour New\", every: 1h}\n\nfrom(bucket: \"telegraf\")\n\t|> range(start: -1h)\n\t|> filter(fn: (r) =>\n\t\t(r._measurement == \"cpu\"))\n\t|> filter(fn: (r) =>\n\t\t(r._field == \"usage_system\"))\n\t|> filter(fn: (r) =>\n\t\t(r.cpu == \"cpu-total\"))\n\t|> aggregateWindow(every: 1h, fn: max)\n\t|> to(bucket: \"cpu_usage_user_total_1h\", org: \"INFLUX_ORG\")",
    "orgID": "INFLUX_ORG_ID",
    "status": "active",
    "description": "This task downsamples CPU data every hour"
}'

Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: