Asana: Add a project to a task
Asana tasks.addProjectForTask: arguments, response, policy and SDK examples.
← Tasks operations · Get started
Operation asana.addprojectfortask
Provider route: POST /tasks/{task_gid}/addProject. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/asana with npm, or alter-sdk-asana with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { AsanaIntegration } from "@alter-ai/asana";
async function execute(input: Parameters<AsanaIntegration["tasks"]["addProjectForTask"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new AsanaIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.tasks.addProjectForTask(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_asana import AsanaIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = AsanaIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.tasks.add_project_for_task(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.task_gid | string | Required within parent | |
query | object | Optional | Additional keys: not allowed |
query.opt_pretty | boolean | Optional | |
body | object | Required within parent | |
body.data | Model | Required within parent | Expand Add a project to a task — request body — body data |
Referenced models: Add a project to a task — request body — body data
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | JSON | Root | |
$ (allOf 1) | object | All variants apply | |
$ (allOf 1).data | Model | Optional | Expand Delete a tag — response body — data data |
$ (allOf 2) | Model | All variants apply | Expand Delete a tag — response body — data |
Referenced models: Delete a tag — response body — data data, Delete a tag — response body — data
Schemas
Section titled “Schemas”Delete a tag — response body — data data
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | An empty object. Some endpoints do not return an object on success. The success is conveyed through a 2-- status code and returning an empty object. |
Delete a tag — response body — data
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
data | Model | Required within parent | Expand Delete a tag — response body — data data |
Referenced models: Delete a tag — response body — data data
Add a project to a task — request body — body data
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
project | string | Required within parent | The project to add the task to. |
insert_after | JSON | Optional | |
insert_after (anyOf 1) | string | Alternative | A task in the project to insert the task after, or `null` to insert at the beginning of the list. When used with `section`, `null` will insert at the beginning of the specified section, otherwise the task must be in the specified section. |
insert_after (anyOf 2) | null | Alternative | |
insert_before | JSON | Optional | |
insert_before (anyOf 1) | string | Alternative | A task in the project to insert the task before, or `null` to insert at the end of the list. When used with `section`, `null` will insert at the end of the specified section, otherwise the task must be in the specified section. |
insert_before (anyOf 2) | null | Alternative | |
section | JSON | Optional | |
section (anyOf 1) | string | Alternative | A section in the project to insert the task into. The task will be inserted at the bottom of the section unless combined with `insert_before: null` (end of section) or `insert_after: null` (beginning of section). Can also be combined with non-null `insert_before` or `insert_after` to position relative to a task within the section. |
section (anyOf 2) | null | Alternative |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: asana.addprojectfortask. Catalog operation: asana:addProjectForTask. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Required provider scopes: ["tasks:write"]