# Use Asana to prepare a narrow due-date update

Example: A manager approved a new date for one task. A teammate also suggested changing its assignee and scope.

By Righthand Team · 2026-10-19

Source: https://www.righthand.ai/blog/use-asana-to-prepare-a-narrow-due-date-update

Keep Asana as the source for its records. A Righthand can use available information for the decision below.

This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.

## The customer task

A manager approved a new date for one task. A teammate also suggested changing its assignee and scope.

[Provider documentation](https://developers.asana.com/docs/tasks). The documentation gives information about task properties, assignees, dates, completion, and project memberships. These properties give different task facts.

## Make account access explicit

If Asana is available in [Connections](https://docs.righthand.ai/guides/adding-your-first-connection), connect the intended account. Give the Righthand access to that connection.

Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.

For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.

[Connection Permissions](https://docs.righthand.ai/guides/add-a-connection) gives information about account access and tool permissions. Give only the access necessary for the identified task.

## The request to the Righthand

> Read the supplied task and approval.
>
> Prepare the approved date change only.
>
> Send other proposals as unanswered decisions.
>
> Get permission before writing.
>
> Send the owner the result before 3 PM Friday.
>
> Use Pacific time.

## Use the provider records for the result

Identify the task and project. Compare the task's assignee, dates, and completion independently. Prepare changes only for the property that the owner approved.

Approval for one property does not give permission for every task change.

For a permitted write, examine the resulting account record. A proposal does not establish a completed change.

For an external message, identify the recipient and permitted task. **Ask** uses an explicit instruction or approval. Connection tool permissions are another required control. [Communications Policy](https://docs.righthand.ai/security/external-communications).

## An illustrative result and next step

> The proposed update changes the due date only. Assignee and work scope remain unchanged.

The manager examines the resulting date and gives a decision about other proposals separately.

## Try one account task

1. Give the Righthand one identified source record.
2. Compare its result with that source.
3. Examine the account record after a permitted write.
4. Examine the work in [Activity](https://docs.righthand.ai/guides/working-with-your-righthand).

If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.

## When the account tools are sufficient

Use Asana directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.

[Compare plans](https://www.righthand.ai/pricing). [Get a Righthand](https://teams.righthand.ai).