> For the complete documentation index, see [llms.txt](https://docs.spreo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spreo.io/boards/actions.md).

# Actions

Actions help you keep track of meeting outcomes and next steps.

Assign an action to a team member from a sticky, and the Action will be added to your team dashboard.

Team members will be notified of their assigned, upcoming, and overdue actions by email.

### Actions Demo Video

{% embed url="<https://www.tella.tv/video/actions-and-mentions-4xx7>" %}

### Creating Actions

<figure><img src="https://content.gitbook.com/content/wEhLPSRTDuhd61395hZu/blobs/5VYN8Ckpacuw9K8vS49q/actions.png" alt=""><figcaption></figcaption></figure>

Actions are created from sticky notes - one action per sticky.

There are two way you can assigns actions on stickies - either by typing @ inside a sticky, or with the “Assign Action” option in a sticky’s toolbar.

Start typing @ and you’ll see a menu appear with various options. Select ‘assign action’ and then follow the prompts:

* Select who to assign the action to
* Select a due date (optional)

And that’s it, your action has now been created. To view, edit or delete your new action item, click on the action status on your sticky note.

<figure><img src="https://content.gitbook.com/content/wEhLPSRTDuhd61395hZu/blobs/DgtQNXOXlzrwg0Pxl8WN/actions-detail.png" alt=""><figcaption></figcaption></figure>

From this view you can:

* Change who the action is assigned to
* Update the action status
* Set or edit a due date
* Delete the action
* Navigate to the Action Items dashboard

You can also assign actions to one or multiple sticky notes by using the sticky note toolbar which appears above a sticky when it is selected.

This will lead you through the same steps as if you had created the action via the @ menu. If applying to a selection of sticky notes, the same inputs will be applied to all.

When a team member is assigned an action, they will receive a [notification](/boards/notifications.md) which will redirect them to the [Action Items dashboard](/dashboard/action-items.md).

### Importing Actions

To bring existing Action Items directly into a board for your next meeting, use the import options in the sidebar.

<figure><img src="https://2875185778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwEhLPSRTDuhd61395hZu%2Fuploads%2Fd5S620mr7rD0XTOMr1i7%2Factions-import.png?alt=media&amp;token=897e48f0-e661-49ab-8272-4c33ec980131" alt=""><figcaption></figcaption></figure>

Imported actions will remain synced to their original source and can be updated across boards via the original sticky note, an imported version or from updates made in the [Action Items Dashboard.](/dashboard/action-items.md)


---

# 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://docs.spreo.io/boards/actions.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.