/automations/:project_id.
Each row shows the run’s name, Source (Scheduled or Test), the time it sent, its status, the report Type, and the Date range it covered. Test runs are also tagged with a Test badge. You can search by name and filter by report type, and the list is paginated.
Status values
When to check history
- Debugging a missed delivery — confirm a scheduled run actually fired and whether it succeeded or failed.
- Verifying a test — a test send shows up here as a Test row right after you trigger it.
- Auditing — confirm an end-of-month report went out on time.
Endpoint
The history is served byGET /v1/automations/:project_id/history — note that it’s scoped by project, not by a single automation id. It aggregates the runs of every automation attached to that project into one timeline and is paginated via page and limit.
Archiving a run from the history list removes the underlying report snapshot for that run, not the automation itself. The automation keeps running on its schedule.