Public descriptions and installed account actions for an integration
Example: A buyer sees a catalog entry and wants a customer-field update. The buyer did not examine the actual tools.
Use public descriptions for candidate selection. Use actual operation evidence for implementation, because catalog presence is insufficient.
This article is from Righthand. The story and result are illustrative.
Two records with different meanings
A public description gives documented product functions.
An installed account action is an available operation under the buyer's actual permissions.
The customer's situation
A buyer sees a catalog entry and wants a customer-field update. The buyer did not examine the actual tools.
The owner gives the Righthand the identified source material and relevant contacts. A Righthand is an assistant with email, text, phone, and Slack communication. Introduction.
The request to the Righthand
Read the supplied task requirement.
>
Identify the exact required read and write operations.
>
Send unverified installed support explicitly.
>
Send the owner the result in this conversation.
>
Get approval before you change an accepted commitment.
The assistant reads the sources for their different meanings. It compares the relevant facts and sends the difference to the owner.
If the request permits contact, the assistant sends the identified question to the supplied recipient. Send the reply to the person responsible for the decision.
An illustrative result
The catalog identifies the app. The exact field write remains unverified.
The owner does an operation test or keeps the account edit with a person.
Set access and authority for the actual task
Supplied source material can be sufficient for the first procedure. For direct account access, a connection with the applicable operation and Righthand access is necessary. Connections.
For an external action, identify the recipient and task. Ask uses an explicit instruction or approval. Connection tool permissions are another required control. Communications Policy.
Try the difference with one case
- Give the assistant one example of each source.
- Include a difference that affects the task.
- Compare the returned difference with both sources.
- Make sure that the test recipient receives a permitted message.
- Examine the work in Activity.
A satisfactory result must keep the difference and identify the next owner decision. It must not silently replace one source with the other.
When another approach is sufficient
A direct record or a human review can be sufficient when it gives the answer and no further conversation is necessary. A Righthand is an alternative when you want responsibility for the next information request and decision handoff.