Actions

Tasks

Tasks are where automation happens in Stubber

# Basic Info

Tasks are configured inside the editor platform and are used to run a series of automatic operations on the data present on a Stub.

Stubber uses tasks to facilitate automation.
You can kick off many different types of tasks to do actual changes to systems.

More complex automation decisions are done by using conditions on each individual task. This allows running tasks based on other values or the outcome of previous tasks.

# Parameters

name

The unique name of the task within the action

tasktype

Specifies the type of task to run. Any of the documented task types

params

Params allows configuring task specific settings, like headers for an API call or model name for a GPT chat.

See the specific task pages for more information.

# Debugging Tasks

Each task returns data from the task that allows inspection of the result of the task. Each task also returns a key called success being true or false.

In order to debug slow tasks you can inspect the task_duration_ms to see which tasks took the longest to execute.