Use Airtable for a vendor contact ownership question
Example: A supplier table contains two people for one account. The records do not identify who can give approval for delivery changes.
Keep Airtable 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 table contains two people for one account. The records do not identify who can give approval for delivery changes.
Provider documentation. The documentation gives information about filtering and sorting records for API list operations. Formula conditions and sort fields determine the selected records.
Make account access explicit
If Airtable is available in Connections, 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 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 supplier records.
>
Send contact roles and missing approval authority.
>
Prepare the authority question for the buyer.
>
Send the owner the result before 3 PM Friday.
>
Use Pacific time.
Use the provider records for the result
Identify the base, table, and field meanings before selecting records. Do a test of the filter with a known included record and a known excluded record.
Contact presence does not establish decision authority.
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.
An illustrative result and next step
Both contacts can discuss delivery, but the records have no supplied approval authority for changes.
The buyer identifies the authorized contact before giving a revised delivery request.
Try one account task
- Give the Righthand one identified source record.
- Compare its result with that source.
- Examine the account record after a permitted write.
- Examine the work in Activity.
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 Airtable directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.