Google Drive: set expectations, verify app, and narrow permissions

When adding Google Drive as a data source, Jason Reichle at 15:28 encounters a warning “Google hasn’t verified this app”, but proceeds only with my encouragement. He then explains how he would like to limit granted access to a specific folder (Al Serize on 9/4 had same request).

Recommended action Items to increase trust & reduce abandons:

1. Set the user’s expectations before they get the warning.

2. Update the email address referenced in the warning from [email protected] to [email protected] (more trusted).

3. Get Lamatic verified by Google.

4. Limit permissions to something less than the entire Google Drive.

#1 - Set Expectations:

A simple way to boost trust is to explain the permissions they’ll be asked to grant in advance of the Google prompt (see highlighted area in the screenshot below).

Suggested message text (for the highlighted area in the screenshot above):

Add Credentials

Add a unique name to reference this Credential within the workflow builder.

Note: Google will ask you to grant lamatic.ai access to your Google Drive. This access is used strictly by the Lamatic application to allow you to create workflows using the information found on the authorized Google Drive.

#2 - Update Lamatic app author

Reference a more trusted email address than [email protected] on the warning below (e.g., [email protected]).

#3 - Get Lamatic verified by Google:

Not sure what is required to do this, but getting verified would increase trust a lot.

#4 - Narrow the permissions:

Not sure if this is even possible, but the screen below is scary. Multiple users have requested that permissions be limited here to a specific folder (they have sensitive stuff in other folders and don’t want to grant access to this data).