Implementing the Google Drive integration: test and production checklist

Practical implementation guide for the Google Drive integration, with a checklist for test and production. The numbered steps describe the order; then use the per-environment checklists.

Things to watch

• The integration is interactive (no webhook/cron needed); but the CRM module must be active and users need the right Drive permissions.
• The redirect URI must match the Google project exactly.
• The integration works within the Drive of the connected account; prefer a dedicated account.

Checklist — test environment

• ☐ Google Cloud project created/selected.
• ☐ Google Drive API enabled.
• ☐ OAuth consent screen configured with the Drive scope.
• ☐ OAuth client (Web application) created; Client ID + secret noted.
• ☐ Redirect URI registered as i-Reserve shows it.
• ☐ Auth screen filled + Step 1 consent + Step 2 connect done (connection tested).
• ☐ Base folder, subfolder pattern and auto-create set.
• ☐ CRM module active; test user with Drive permissions.
• ☐ Tested: create folder/file, upload, rename, delete from an entity.

Checklist — production environment

• ☐ Production OAuth client with production redirect URI; secret managed separately.
• ☐ OAuth consent screen published if needed (so the refresh token does not expire prematurely).
• ☐ Dedicated Google account connected (not a personal account).
• ☐ Base folder/pattern aligned with the real folder structure (no test folders).
• ☐ CRM module + Drive permissions set up for the relevant roles.
• ☐ First live operation verified.
• ☐ Rollback known: setting the integration inactive hides the file manager without changing Drive data.