Tasks
Create, organize, and run outcome-focused tasks from Vendo's Tasks workspace.
Last reviewed November 13, 2026
Tasks is the Vendo task workspace. Each task records an outcome. Its Steps are the plan, and a Run carries out that plan. Open Labs → Tasks.
What You Can Do
- Create a task manually or from an enabled template.
- Set its title, description, priority, due date, assignee, and status.
- Add Steps and edit them in place.
- Switch between list and Kanban views.
- Attach supporting files.
- Start a Run and follow the progress of each Step.
- Inspect the task history.
- Archive completed or inactive tasks.
Task Statuses
| Status | Use it for |
|---|---|
| Backlog | Accepted work that is not ready to start |
| Todo | Ready for an owner to begin |
| In Progress | Work currently being performed |
| Done | Outcome completed and checked |
| Cancelled | Work intentionally stopped |
You set the task status. Each Run has its own status. A completed Run does not change the task status.
Create a Task
- Open Labs → Tasks.
- Select New task.
- Enter a clear outcome, an optional description, a priority, and a due date.
- Click Create task.
- Open the task to add Steps and attachments.
A new task starts with the status Todo.
If Templates is available, choose a template and review its outputs and trigger before you create the task. Template availability is workspace-specific.
Steps
Steps show as a numbered list in the task.
- To add a Step, click Add a step… and type. Press Enter to start the next Step.
- To change a Step, edit its text in place. Vendo saves the change automatically.
- To collapse or expand a Step, click the arrow beside its number.
- Each Step has a status, an assignee, and optional dependencies on other Steps.
- A lock shows a Step that you cannot change. Hold the pointer over the lock to see the reason.
- To let the Agent add missing Steps from the task description, select Plan with AI in the task’s ⋯ menu.
Run Behavior
How a task runs depends on its Steps.
- A task with Steps for people or Destinations runs with Start. Each Step must have an assigned person or be a Destination.
- Before you start a Run, set the trigger of each active Destination to the task.
- During a Run, each Step shows its Run status. A Step waits until the Steps that it depends on are complete.
- The assigned person gets a notification when a Step is ready. After 24 hours, Vendo sends a reminder. After 72 hours, Vendo notifies the person who started the Run.
- While a Run is in progress, its Steps keep the instructions that the Run started with. Changes to a Step apply to the next Run.
- A task with only Destination Steps can also run on a schedule, or after a Source finishes an import.
- Agent tasks and templates run with Run. They require the Automation runtime to be enabled for the environment.
Before you rely on an Automation in production:
- Confirm that the task reports that it is ready.
- Test it with an input that you can reverse.
- Inspect the run history and output.
- Verify that the downstream system changed as intended.
- Define an owner for failed runs.
If running is unavailable, you can still use the task to plan and track work. Contact your Vendo representative before you use it to run work.
Archive or Delete
Archive a task to remove it from the active views and keep access to it. Archiving cancels the open Runs of the task, so no Step continues to wait.
Delete a task only when you no longer need the task record. You cannot archive or delete a task that controls the trigger of a Destination. First, change the trigger of that Destination.
Related
- Decisions: review proposed changes before they run
- Orchestration: monitor data movement and jobs
- Agent: investigate data and prepare work
- Activity Logs: investigate operational failures