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

# Asana

> Asana Scenario seeding parameters, nested fields, and examples

Use `asana` in `twins` and put this configuration under `seed_config.asana`.

Asana work management with teams, projects, sections, tasks, subtasks, dependencies, tags, custom fields, comments, portfolios, goals, milestones, and completion state.

## Example seed

This is the complete Scenario request body for [creating a Scenario](https://docs.argalabs.com/api-reference/post-create-a-scenario.md). You can also import it with `arga test-runner scenarios import --file scenario.json`.

```json theme={null}
{
  "name": "Asana eval fixture",
  "twins": [
    "asana"
  ],
  "seed_config": {
    "asana": {
      "workspace_name": "Example Workspace",
      "team_name": "Engineering",
      "projects": [
        {
          "name": "Product Launch",
          "notes": "Coordinate the launch across engineering and support.",
          "privacy_setting": "public_to_workspace",
          "default_view": "list",
          "sections": [
            "Intake",
            "In Progress",
            "Done"
          ]
        }
      ],
      "tags": [
        {
          "name": "urgent",
          "color": "dark-red"
        },
        "customer"
      ],
      "custom_fields": [
        {
          "name": "Priority",
          "resource_subtype": "enum",
          "enum_options": [
            "High",
            "Medium",
            "Low"
          ]
        },
        {
          "name": "Estimate",
          "resource_subtype": "number",
          "precision": 1
        }
      ],
      "tasks": [
        {
          "name": "Implement OAuth callback",
          "notes": "Complete and test the authorization-code flow.",
          "project": "Product Launch",
          "section": "In Progress",
          "assigned": true,
          "completed": false,
          "resource_subtype": "default_task",
          "due_on": "2026-12-01",
          "tags": [
            "urgent"
          ],
          "custom_fields": {
            "Priority": "High",
            "Estimate": 5.5
          },
          "dependencies": [],
          "comments": [
            "Ready for review."
          ]
        }
      ],
      "portfolios": [
        {
          "name": "Delivery Portfolio",
          "projects": [
            "Product Launch"
          ]
        }
      ],
      "goals": [
        {
          "name": "Ship reliable integrations",
          "notes": "Improve integration fidelity.",
          "due_on": "2026-12-31"
        }
      ]
    }
  }
}
```

## Parameters

The following fields belong directly inside `seed_config.asana`. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

| Parameter | Type | Description |
| - | - | - |
| `user_name` | `string` | User name. |
| `workspace_name` | `string` | Workspace name. |
| `team_name` | `string` | Team name. |
| `custom_fields` | `object[]` | Custom fields fixtures in provider-native format. |
| `tags` | `array of strings or objects` | Tags. |
| `projects` | `object[]` | Projects fixtures in provider-native format. |
| `tasks` | `object[]` | Tasks fixtures in provider-native format. |
| `portfolios` | `object[]` | Portfolios fixtures in provider-native format. |
| `goals` | `object[]` | Goals fixtures in provider-native format. |

## Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

### `projects[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `notes` | `string` | Notes. |
| `privacy_setting` | `string` | Privacy setting. |
| `default_view` | `string` | Default view. |
| `sections` | `string[]` | Sections fixtures in provider-native format. |

### `tags[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `color` | `string` | Color. |

### `custom_fields[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `resource_subtype` | `string` | Resource subtype. |
| `enum_options` | `string[]` | Enum options fixtures in provider-native format. |
| `precision` | `integer` | Precision. |

### `tasks[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `notes` | `string` | Notes. |
| `project` | `string` | Project. |
| `section` | `string` | Section. |
| `assigned` | `boolean` | Enable or set assigned behavior. |
| `completed` | `boolean` | Enable or set completed behavior. |
| `resource_subtype` | `string` | Resource subtype. |
| `due_on` | `string` | Due on. |
| `tags` | `string[]` | Tags fixtures in provider-native format. |
| `custom_fields` | `object` | Custom fields. |
| `dependencies` | `array` | Dependencies fixtures in provider-native format. |
| `comments` | `string[]` | Comments fixtures in provider-native format. |
| `parent` | `string` | Parent. |

### `portfolios[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `projects` | `string[]` | Projects fixtures in provider-native format. |

### `goals[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `notes` | `string` | Notes. |
| `due_on` | `string` | Due on. |

See [Scenario seeding](https://docs.argalabs.com/twins/seeding.md) for saving, provisioning, and resetting fixtures.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.