All automations at once
Every automation of the workspace side by side over a window: totals, a row for each automation and a point for each day.
Runs the real call on your workspace.
GET /automations/analytics
Every automation of the workspace side by side over a window: totals, a row for each automation and a point for each day.
Example
Needs automations:read. since and until are ISO 8601 timestamps, and automationIds takes up to 50 ids separated by commas. The window defaults to the last 30 days and spans at most 366.
curl "$OE/automations/analytics?since=2026-10-01T00:00:00Z" -H "$AUTH"{ "object": "automation_analytics", "since": "2026-10-01T00:00:00.000Z", "until": "2026-10-11T09:30:00.000Z", "totals": { "automations": 3, "live": 2, "entered": 512, "active": 41, "completed": 448, "exited": 12, "sent": 690, "delivered": 682, "opened": 411, "clicked": 103, "bounced": 8, "complained": 0, "unsubscribed": 5 }, "series": [{ "date": "2026-10-10", "entered": 46, "completed": 40, "exited": 1, "sent": 61 }], "automations": [ { "id": "aut_7c2e9a1f4b8d30c65e1a9f27", "name": "Welcome series", "status": "live", "triggerKind": "audience_joined", "timezone": "Europe/London", "entered": 459, "active": 38, "completed": 412, "exited": 9, "sent": 611, "delivered": 604, "opened": 371, "clicked": 96, "bounced": 7, "complained": 0, "unsubscribed": 4 } ]}automationIds narrows totals and series. automations still lists every automation, so a picker can offer them all.
active is counted now, whatever the window. Everything else is counted inside it.
Each automation counts its days in its own time zone, so a date in series is the same calendar day in each of them.
Google Workspace