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

# Send a capture to Asana

> Connect an Asana project and create a task with supported assignees, sections, tags, dates and custom fields.

Asana delivery creates a task in a project from a saved capture. A workspace owner connects the default project. Members send there; owners can choose another workspace/project destination that the connected Asana identity can access for one task.

## Requirements and connection

Setup requires a workspace owner. Use **Continue to Asana** when OAuth is available or **Use a token instead** with a personal access token that can read the project and create tasks. Tekma asks for **Project ID**. A display name or browser URL is not a substitute for that ID. The identity must be able to see project sections, members, tags and custom-field metadata.

1. Open **Settings → Integrations** and choose **Connect** beside Asana.
2. Choose **Continue to Asana** and authorize, or choose **Use a token instead** and enter the token.
3. Enter **Project ID** and choose **Connect Asana**. Tekma checks the project before saving.
4. Confirm **Connected** in the integrations list. Use **Manage** to choose a new destination without replacing credentials.

## Send a task

1. Open a saved capture and choose **Send to app → Asana**.
2. Wait for **Loading preview…** and review the project, title, saved description and private link.
3. Choose an **Assignee**, existing **Tags** (up to ten), project **Section**, **Due date**, and supported custom fields. Custom fields can be text, number, enum, or multi-enum. Tekma does not offer people, date/reference, read-only, formula, or other app-defined custom fields. Existing values are selected from the project metadata; Tekma does not create tags or options.
4. Use **Edit visible fields** to hide optional controls, add context, then choose **Send to Asana**.
5. Open the returned task and check its section and fields. If delivery was not confirmed, inspect Asana before retrying.

Owners may choose a **Workspace** and **Project** for this send when the connected identity has access. Changing the project clears sections, tags, members and custom-field selections. Members stay on the configured project, and an alternate choice does not update the workspace default.

| Field             | Supported values                                            |
| ----------------- | ----------------------------------------------------------- |
| Workspace/project | Configured project; owner-only accessible alternate project |
| Assignee          | An available Asana assignee for the selected project        |
| Tags              | Existing project tags; maximum 10                           |
| Section           | Existing section in the selected project                    |
| Due date          | Date accepted by Asana                                      |
| Custom fields     | Existing text, number, enum, and multi-enum fields/options  |

The task body includes report text, sanitized source URL, capture kind and a private Tekma URL. It does not upload video, screenshots, comments, or raw diagnostics. Section membership is applied as part of initial creation; it is not a later move.

## Troubleshooting

If the project disappears, verify project access and reconnect or update the token. If a section, tag or option is missing, confirm it exists in that project and refresh the preview. A provider-required field of an unsupported type can still block creation; Tekma cannot satisfy it with a hidden value. An ambiguous response may mean the task exists, so search Asana before sending again.