Real-time triggers from Google Sheets, ready-made actions in Google Analytics 4. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Google Sheets.
Workflows do something in Google Analytics 4, instantly.
Pair pages are mirrored. Each direction gets its own dedicated page.
2 Google Sheets triggers wired to 3 Google Analytics 4 actions. Most-used pairing: New Row → List GA4 Properties.
0 Google Analytics 4 triggers wired to 9 Google Sheets actions downstream.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new row is added to a Google Sheet (typically the first sheet tab). Common use: ingest form-fed rows into a CRM or notify on a new entry.
Fires when a new row is added to a Google Sheet (typically the first sheet tab). Common use: ingest form-fed rows into a CRM or notify on a new entry.
Fires when a new row is added to a Google Sheet (typically the first sheet tab). Common use: ingest form-fed rows into a CRM or notify on a new entry.
Fires when a row is updated in a Google Sheet. Useful for sync flows where the Sheet is a source-of-truth that drives downstream changes.
Fires when a row is updated in a Google Sheet. Useful for sync flows where the Sheet is a source-of-truth that drives downstream changes.
Fires when a row is updated in a Google Sheet. Useful for sync flows where the Sheet is a source-of-truth that drives downstream changes.
No code, no glue, no half-day setup. Each step is one click.
Open TinyCommand, authorize Google Sheets and Google Analytics 4 once each. Both connections are available to every workflow on your account.
Drop the Google Sheets → New Row trigger onto the canvas. TinyCommand auto-registers the webhook.
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
Drop the Google Analytics 4 → List GA4 Properties action below it. Map fields from the Google Sheets payload into the Google Analytics 4 inputs.
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
