> ## Documentation Index
> Fetch the complete documentation index at: https://docs.custral.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks

> Follow-ups being completed, and the record they hang off.

## Overview

A task is a piece of follow-up work. It usually hangs off a record, and it can
also stand alone, which is the one thing to design a receiver around.

One trigger today. `task.completed` fires when a task is marked done, and
carries `recordId` **only when the task belongs to a record**. On a standalone
task the field is absent rather than null, so read it as optional.

Completion is the only task event. Creating, assigning, reassigning and
rescheduling emit nothing.

## Related documentation

<CardGroup cols={2}>
  <Card title="Tasks" icon="circle-check" href="/team/tasks/overview">
    How tasks are created, assigned and completed in the app.
  </Card>

  <Card title="Task types" icon="list-check" href="/team/tasks/types">
    The kinds of task a workspace can raise.
  </Card>
</CardGroup>

## Triggers

<CardGroup cols={1}>
  <Card title="task.completed" icon="circle-check" href="/dev/webhooks/events/task-completed">
    A task was marked done, with the record it hangs off.
  </Card>
</CardGroup>


## Related topics

- [Task Types](/team/tasks/types.md)
- [Task Overview](/team/tasks/overview.md)
- [task.completed](/dev/webhooks/events/task-completed.md)
- [Workflow Actions](/automation/workflows/actions.md)