# Use Trello to keep a cancellation reason

Example: A course card has a cancellation decision. A manager wants its list changed but must have the reason available for future planning.

By Righthand Team · 2026-10-20

Source: https://www.righthand.ai/blog/use-trello-to-preserve-a-cancellation-reason

Keep Trello 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 course card has a cancellation decision. A manager wants its list changed but must have the reason available for future planning.

[Provider documentation](https://developer.atlassian.com/cloud/trello/rest/api-group-cards/). The documentation gives information about card operations with names, descriptions, due dates, lists, and other card properties. Account permissions are necessary for access.

## Make account access explicit

If Trello 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 cancellation decision.
>
> Prepare the approved card state change.
>
> Keep the cancellation reason in the record.
>
> 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 board, list, and exact card before the task. Keep card location distinct from completion evidence. A card move must match an approved state transition.

A state change must not remove decision context that the owner wants.

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 change keeps the reason and changes the card's state only.

The manager examines the resulting card before closing associated work.

## 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 Trello 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).