> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/operations/tasks/how-to-create-a-task.md).

# Create a Task

Create tasks in PaintScout to track reminders and follow-ups linked to deals, contacts, and companies.

Tasks keep important reminders and follow-ups tied directly to your deals, contacts, and companies.

{% hint style="danger" %}
**Important:** this feature requires the paid **Operations add-on.**
{% endhint %}

***

## Creating a New Task

1. On the **Tasks page**, click **New Task**.
2. This opens the **Create New Task** dialog.

In the dialog, fill out the following details:

* **Task Title** – A clear name for the task (e.g., “Call customer for follow-up”).
* **Deal** – Select the Deal to link this task to. *(Some basic deal details can be edited here.)*
* **User** – Choose yourself or another team member as the task's assignee.
* **Description** – Add any notes or details about the task.
* **Due Date & Time** – Set when the task should be completed. Add a due date so the task appears in **Upcoming**.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-d7fb80829ce3a28ba9a770819117cd0adf54d317%2F1676519616_80e3c091b2c6db69dc18e1fa1c0d?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Use a single task for one-off work. If you need the same group of tasks on multiple deals, use [Checklists](/support/operations/tasks/checklists.md) instead.
{% endhint %}

***

## Where Does the Task Appear?

* A newly created task will appear on the **Upcoming** tab if assigned a due date.
* The task is also automatically shown on the related **Deal, Contact and Company** pages, in both the **Tasks section** and the **Activity log**.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-31a82a1eeead44033bbfd1c136a26276c7991fd1%2F1676521379_6cfd3915113807857627b265ba06?alt=media" alt=""><figcaption></figcaption></figure>

&#x20;&#x20;

## Related articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Introduction to Tasks</strong></td><td>Overview of the tasks page including categories, filtering, sorting, and managing follow-ups linked to deals.</td><td><a href="/support/operations/tasks/introduction-to-tasks.md">Introduction to Tasks</a></td></tr><tr><td><strong>Managing Tasks</strong></td><td>Manage your task workflow in PaintScout — create, edit, complete, and delete tasks linked to deals for organized follow-ups and reminders.</td><td><a href="/support/operations/tasks/managing-tasks.md">Managing Tasks</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.paintscout.com/support/operations/tasks/how-to-create-a-task.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
