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

# Tasks

> Tasks are internal reminders and follow-ups, tracked alongside threads rather than on them.

Tasks are reminders or follow-ups that your team needs to action. Each task has a title, description, status, priority and can be assigned to a user or a machine user. Tasks can also be linked to an account to give them context.

<Snippet file="graphql/sdk-note.mdx" />

Tasks live alongside threads in the Plain app but are not threads themselves. They are a lighter-weight to-do, useful for things like "send onboarding follow-up next Friday" or "check in on this customer after their renewal".

Use the API when you want tasks to be created or updated as a side-effect of something happening in your own systems (for example, automatically creating a follow-up task when a deal closes in your CRM).

Plain also raises tasks itself. When the [Customer Agent](https://www.plain.com/docs/product/agents/ari.md) can't answer a customer from your knowledge sources, it records a [knowledge gap](https://www.plain.com/docs/graphql/knowledge-gaps.md), and creates a task to fill it once a second thread asks the same question. Read the gap from the task's `sourceLinks`; see [Get the knowledge gap behind a task](https://www.plain.com/docs/graphql/tasks/get.md#get-the-knowledge-gap-behind-a-task).

Subscribe to [task webhook events](https://www.plain.com/docs/webhooks/task-created.md) to react to tasks created, updated, or deleted in Plain, including tasks raised for knowledge gaps.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.