Problem
List automations have no API representation — no endpoint, no ID, no name. Only automations_count and automations_active flags are visible on the list resource.
Proposed Solution
Add a GET /lists/{id}/automations endpoint returning each automation's name, trigger event (joins/leaves), action type, and active status.
Why It Matters
We manage 71 lists and cannot audit what automations are running without opening each one manually in the UI. When tracing whether a list is connected to an email sequence or a workflow trigger, the API hits a dead end — it confirms something exists but not what it does.
Current Workaround
Manual UI review of every list's Automations tab — not scriptable, not auditable at scale.
Problem
List automations have no API representation — no endpoint, no ID, no name. Only
automations_countandautomations_activeflags are visible on the list resource.Proposed Solution
Add a
GET /lists/{id}/automationsendpoint returning each automation's name, trigger event (joins/leaves), action type, and active status.Why It Matters
We manage 71 lists and cannot audit what automations are running without opening each one manually in the UI. When tracing whether a list is connected to an email sequence or a workflow trigger, the API hits a dead end — it confirms something exists but not what it does.
Current Workaround
Manual UI review of every list's Automations tab — not scriptable, not auditable at scale.