Distillation

Date: Aug 5, 2026

• 🟡 (20:11) User asked why not trigger newsletter sending with an API call.
• 🟡 (20:11) Assistant explained Loops POST /v1/events/send is contact-scoped, not mailing-list-scoped: it requires either email + eventName or userId + eventName; there is no documented request shape using mailingListId to broadcast to a list.
• 🟡 (20:11) Assistant stated the optional mailingLists field on a Loops event changes that contact's mailing-list membership and does not broadcast the event to mailing-list members.
• 🟡 (20:11) Assistant stated Loops public API provides: find one contact by email or user ID; create/update contacts; view mailing lists; send an event to one identified contact; create and edit campaigns.
• 🟡 (20:11) Assistant explained a Loops workflow mailing-list setting acts as a filter: when one contact receives an event, Loops checks whether that contact is in the selected list; one event does not fan out to all contacts in the list.
• 🟡 (20:11) Assistant stated the documented Loops API model is one API event -> one contact enters the workflow, not one API event -> every mailing-list contact enters the workflow.
• 🟡 (20:11) Assistant identified 2 API capabilities that would enable unattended sending from the reusable GitHub Action if available: (1) a bulk workflow event endpoint; (2) a campaign-publish endpoint.
• 🟡 (20:11) Assistant recommended asking Loops support whether they provide an undocumented/private API for bulk workflow triggering or campaign publishing.
• 🟡 (20:11) Assistant concluded that, absent such APIs, the clean Loops implementation remains generating a complete campaign draft in Loops and manually clicking Publish.