# Asana

## What this integration can do

Asana commonly serves as:

* A source of tasks or project status
* A scheduled review target for reminders and follow-up
* A data source for workflow checks before posting results elsewhere
* A chat-style surface when task comments should be routed into Hookshot

## Prerequisites

* Access to the Asana workspace, project, or task area you want to use
* Permission to complete the connection flow
* A clear reminder or review workflow

## Connect

1. Open **Integrations**.
2. Select **Asana**.
3. Complete the connection flow.
4. Confirm the integration is connected.

## Trigger Access

Use Trigger Access when Asana activity should start the Protege.

Examples:

* A configured project-level source
* A live Asana event path in your workspace
* A managed project or portfolio used for task-comment activity

## Tool Access

Use Tool Access when the Protege should inspect Asana state before acting.

Examples:

* Check whether a task is complete
* Review project state before sending a reminder
* Update or respond to Asana work when the workflow allows it

## Chat setup

For Asana chat-style workflows, choose the exact projects or portfolios Hookshot should monitor. A Protege should not watch a broader Asana area than the workflow owner can review.

## Permissions and scopes

Review the Asana connection carefully. In practice, Hookshot needs permission to:

* Access the tasks or project objects that matter for your workflow
* Read enough context to decide whether a reminder or follow-up is necessary

Use the smallest practical project or workspace scope for the job.

## How to verify

* Confirm Asana is connected
* Confirm the relevant trigger source or scheduled workflow is ready
* Confirm any managed project or portfolio selection is correct
* Use a known incomplete or known test item
* Check Event Feed for the scheduled or live activity
* Check Audit for the resulting reminder or follow-up run

## Common mistakes

* Running a reminder workflow against the wrong project
* Forgetting to verify the exact task or project boundary
* Treating a scheduled review as verified before a real scheduled test occurs

## Troubleshooting

* If the workflow never starts, review the schedule or Asana trigger setup.
* If the Protege runs but reminds on the wrong work, narrow the project or task boundary.
* If Audit shows a run with unexpected behavior, confirm the Asana source and downstream destination are both correct.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryprotege.com/integrations/asana.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.