How tasks fit in
Tasks belong to an agent. When you run a task, you provide a connection and the task input defined by its schema. Deck creates a task run that executes the work. Workflows can chain multiple tasks into a single execution.Creating tasks
Tasks can be created in the Dashboard with prompting or from a template. They can also be created through the API. Once created, you reference them by ID in your API calls.Read vs. write
Tasks can be read operations (fetching data) or write operations (performing actions).| Type | Examples |
|---|---|
| Read | Fetch account balance, list transactions, download statements |
| Write | Submit a form, make a payment, cancel a reservation |
Input and output schemas
Every task defines a contract through JSON Schema:- Input schema validates what you send when running the task. Deck rejects requests that don’t match before the agent starts.
- Output schema defines the structure of the data the agent returns. Regardless of how the source renders its data, Deck returns a consistent shape.
Task statuses
| Status | Meaning |
|---|---|
learning | The agent is learning how to perform the task. You can run it, but expect lower success rates. |
test | The agent understands the task but is still improving. Higher success rates than learning. |
live | Production-ready. The agent fully understands the task. |
learning or test while the agent adapts to the changes.