Righthand
← All posts

Use Google Calendar to identify a site visit and travel conflict

Example: A consultant accepted a site visit. The travel block starts before a different meeting ends, but the customer appointment must remain fixed.

Keep Google Calendar 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 consultant accepted a site visit. The travel block starts before a different meeting ends, but the customer appointment must remain fixed.

Provider documentation. The documentation gives information about event creation with a calendar, start time, and end time. Attendee notifications depend on the event settings.

Make account access explicit

If Google Calendar 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 visit and travel events.

>

Show the conflicting travel period.

>

Prepare alternatives without changing the customer visit.

>

Send the owner the result before 3 PM Friday.

>

Use Pacific time.

Use the provider records for the result

Select the intended calendar before the event action. Use exact dates and the local time zone. An attendee invitation is an outward action.

A travel block is not customer permission to change an appointment.

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

The visit remains Thursday at 2 PM. The travel block conflicts with a 1 PM internal meeting.

The consultant moves the internal meeting before giving approval for calendar changes.

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.

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 Calendar 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. Get a Righthand.