Short answer: Drop the "Google Analytics → GA Run Report" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Property ID propertyId | string | Required | Property ID. Example: 123456789 |
Start Date startDate | date | Required | Start Date. (date/time) |
End Date endDate | date | Required | End Date. (date/time) |
Metrics metrics | string | Required | Comma-separated metric names |
Dimensions dimensions | string | Optional | Comma-separated dimension names |
{"propertyId": "e.g. 123456789","startDate": "{{trigger.startDate}}","endDate": "{{trigger.endDate}}","metrics": "{{trigger.metrics}}","dimensions": "date,country,pagePath"}
{"rows": [{"metricValues": [{"value": "1500"},{"value": "1200"},{"value": "3500"}],"dimensionValues": [{"value": "20260411"}]}],"metadata": {"currencyCode": "USD"},"rowCount": 1}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.