Documentation

Google

Calendar, Sheets, Drive, Google Ads and postal address validation — under a single connector, in BYO mode.

Google

The Google integration bundles several capabilities under a single connector: Calendar, Sheets, Drive, Google Ads and postal address validation. Each one is enabled independently according to your needs, with "Sign in with Google" connection (managed OAuth) or your own app.

Calendar (Google Calendar)

  • List the events of a calendar over a period (google.calendar_list_events) — useful so an agent knows your availability.
  • Create an event via the google_calendar_create_event node — for example, to book a confirmed appointment.

Typical use: a personal assistant that checks the calendar, proposes a time slot, then creates the appointment.

Google Sheets

  • Read a sheet (google.sheets_read) — fetch rows to process them in a pipeline.
  • Append rows via the google.sheets_append tool or the google_sheets_append node (exactly-once write).
  • google_sheets_read node — deterministic read of a range, published into the context.

Typical use: log every pipeline run into a tracking sheet, or use a sheet as a small business configuration base.

Google Drive

  • Search and read files (google.drive_*), upload a document, manage files in a folder.
  • google_drive_list / google_drive_upload nodes — listing and depositing files (upload exactly-once).
  • Folder watching — the google_drive_changes receiver detects new files in a folder (polling with a cursor) and triggers a pipeline.

The Drive scope is sensitive: restrict access to the folders that are strictly necessary.

  • Performance report — fetch the metrics of your campaigns (google.ads_report).
  • Conversion upload — push offline conversions back to Google Ads via a dedicated node.

Address validation

The google.verify_address tool validates and normalizes a postal address (useful before a physical mailing or to clean up a customer record).

Connection (BYO + vendor fallback)

  1. Administration → Integrations → Google.
  2. Enter your Google credentials (API key for address validation; OAuth account for Calendar and Ads).
  3. Resolution your account > shared account: if you have not configured your own access, betool can route certain calls through a pooled vendor account.

Metering only applies when the call goes through the shared vendor account (e.g. address validation on the pooled key). On your own account (BYO), you pay Google directly, with no betool margin.