# Use Google Docs for a supplier instruction revision

Example: A supplier document names a discontinued material. The buyer approved a replacement in a separate message.

By Righthand Team · 2026-10-18

Source: https://www.righthand.ai/blog/use-google-docs-for-a-supplier-instruction-revision

Keep Google Docs 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 supplier document names a discontinued material. The buyer approved a replacement in a separate message.

[Provider documentation](https://developers.google.com/workspace/docs/api/how-tos/overview). The documentation gives information about creation and modification of documents through its API. Document operations and account authorization remain distinct requirements.

## Make account access explicit

If Google Docs 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 instruction document.
>
> Prepare a revision using the approved replacement.
>
> Show the affected passages before a account write.
>
> Send the owner the result before 3 PM Friday.
>
> Use Pacific time.

## Use the provider records for the result

Identify the exact document before the task. Give the assistant the approved text source. Use a copy for the first edit test and compare the resulting content.

Do not extend a material approval to unrelated contract text.

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 revision changes two material references. A third passage gives an old delivery date.

The buyer gives approval for the material revision and gives a decision about the date 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 Google Docs 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).