> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/plugins/integrations/practice-management/asana.md).

# Asana

With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Asana and, when **Write** access is enabled, perform approved actions in Asana. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/)

## Connect Asana

1. Create an **Asana** connection and name it for the firm team or workspace.
2. Sign in with an Asana user who belongs to the required workspace, teams, and projects.
3. Approve the authorization request and return to Filed.
4. Verify with a non-sensitive project before enabling write access.

If a project is missing, add the authorized Asana user to that project. Private projects remain unavailable until that user has membership.

## Verify the connection

After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm workspace, team, and project membership. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow.

## Manage permissions

Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Asana data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change.

## Troubleshooting

**The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has workspace, team, and project membership.

**The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review workspace, team, and project membership, then reconnect if the account or environment was wrong.

**The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem.

## Using this integration with Filed Chat and Routines

Use **Chat** for one-off questions and guided work on a client, such as finding Asana information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Asana data on a schedule or in response to a trigger.

Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them.

## Example prompts

Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled.

* “Summarize the Asana information for \[client name] for \[date range].”
* “Find items in Asana that need review before \[deadline].”
* “With write access enabled, prepare the approved Asana update and show the proposed changes first.”

## Capabilities

### See work and deadlines in one place

Use Filed to retrieve the projects, tasks, assignments, and due dates available to the connected practice-management account. This gives Chat and Routines firm context for client work.

### Create or update approved work

When **Write** access is enabled, Filed can support creating and updating approved tasks or work items. Use this for consistent follow-up and assignment workflows after your firm has reviewed the outcome.

### Work within existing project access

Filed can only use the workspaces, teams, projects, and boards the authorized user can access. Manage that scope in the provider rather than sharing a broader login.


---

# 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.filed.com/reference/plugins/integrations/practice-management/asana.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.
