Documentation

Google

Calendar, Sheets, Drive, Google Ads, Analytics 4, Search Console, Business Profile and address validation — each capability connected separately, in BYO mode.

The Google integration bundles several capabilities: Calendar, Sheets, Drive, Google Ads, Google Analytics 4, Search Console, Business Profile and postal address validation. Each one is connected independently (you only grant the scopes you need), with "Sign in with Google" (managed OAuth) or your own app.

Calendar (Google Calendar)

  • List the events of a calendar over a period (google.calendar_list_events, google_calendar_list_events node) — useful so an agent knows your availability.
  • Create an event (google.calendar_create_event, google_calendar_create_event node) — for example, to book a confirmed appointment.
  • Delete an event (google.calendar_delete_event) — from its identifier.
  • Trigger a pipeline before an event — the google_calendar_inbound receiver periodically polls the calendar and can trigger only for events starting soon (reminder, appointment preparation). Immediate reaction to a calendar change is not available.

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, google_sheets_read node) — 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).
  • Publish a table (google.sheets_publish, google_sheets_publish node) — creates a new multi-sheet spreadsheet and returns its URL. Warning: the spreadsheet is made public by default.

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_search, google.drive_read), upload a document (google.drive_upload), create a folder, move a file, move to trash (reversible).
  • google_drive_list / google_drive_download / google_drive_upload nodes — listing, retrieving 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: by default, betool only requests access to the files it creates or that you open to it (drive.file).

  • Performance report — fetch the metrics of your campaigns (google.ads_report).
  • Manage a campaign — change its daily budget (google.ads_update_budget) or pause / reactivate it (google.ads_update_campaign_status).
  • Conversion upload — push offline conversions back to Google Ads via the google_ads_conversion_upload node.

Google Analytics 4 and Search Console

  • Analytics 4 — audience report for your GA4 properties (google.analytics_report, google_analytics_report node), read-only.
  • Search Console — search performance of your sites: queries, pages, clicks, impressions (google.search_console_report, google_search_console_report node), read-only.

Google Business Profile

  • Reviews — list the reviews and average rating of a listing (google.gbp_list_reviews, google_business_report node), and reply publicly to a review (google.gbp_reply_review).
  • Posts — publish a post on the listing (google.gbp_create_post, google_business_post 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. Settings → Services → Google, Accounts tab.
  2. Connect each capability you need: "Sign in with Google", or the credentials of your own OAuth app. Address validation uses an API key.
  3. For address validation only: if you have not configured your own key, betool can route the call through a pooled vendor key (resolution your key > shared key).

All OAuth capabilities run on your Google account, with no metering and no betool margin. Only address validation routed through the shared vendor key is billed in credits.