Connect Google accounts and resources
Connect Google Sheets, Calendar, Drive or Contacts, select the resources the workflow may use, and recover permissions without sharing credentials.
Reviewed
Connect the intended Google account, then select the resources your workflows need. Completing OAuth alone does not mean every spreadsheet, calendar or file is available to an action.
Authorize the account
- Open Settings > Integrations and choose Google Sheets, Google Calendar, Google Drive or Google Contacts.
- Start the connection when its setup control is enabled.
- In Google's authorization screen, verify the account and requested permissions. Return to Waaru after approval.
- Confirm the connected account and any number-access restrictions shown in Waaru.
- Complete the resource selection for that provider before using a workflow action.
Use an account that can access the business resources you intend to select. Do not paste access tokens or credentials into a flow variable, note or support request.
Select the provider's resources
| Connection | What to configure | What to verify before a workflow uses it |
|---|---|---|
| Google Sheets | Select a spreadsheet using the provided picker, then choose the worksheet and fields offered by the action. | The selected sheet belongs to the intended account and contains the expected headers and data types. |
| Google Calendar | Select the calendars exposed by the connection page. | Availability checks and managed-event actions refer to the intended calendar and timezone. |
| Google Drive | Select the files or folders offered through the resource picker. | The exact item is permitted for the metadata, folder, upload or import action being configured. |
| Google Contacts | Connect the account whose People records the action should use. | Search/get/create/update operations target the correct account; the current connector does not expose deletion. |
Use the action catalog to see which operations are enabled in your account and editor. Do not assume an item shared elsewhere in Google automatically appears as a bound resource in Waaru.
Test and maintain access
Choose a small, permitted record for the first test. Verify both the workflow result and the source application. For a write, confirm the changed record rather than relying only on the completed action label.
If a connection requires reconnection, authorize the intended account again and recheck the resources and permissions. A disconnected account or removed resource can make a previously configured action unavailable. Update affected mappings and validate before reactivating dependent work.
Next: Configure connected actions, send a prepared Drive file, or review other integrations.
Join and leave recorded live support
Review recording consent, join an available support call, control microphone and optional screen sharing, and end access in Waaru Care.
Connect commerce, CRM and booking apps
Prepare store, payment, shipping, CRM and booking connections, select supported resources, and test the actions and events enabled in your Waaru account.