Distillation

Date: Aug 5, 2026

• 🟡 (20:05) User asked whether the reusable action could use a transactional email for unattended sending, specifically: “hey there's a new post, here's the first paragraph”.
• 🔴 (20:05) User-provided Loops docs stated transactional email API requests require authentication (“Send a POST to this endpoint (make sure to authenticate)”).
• 🔴 (20:05) User-provided Loops docs stated that if a transactional email uses an array block, the payload must include the parent data variable tied to the array and an array of objects.
• 🔴 (20:05) User-provided Loops docs stated “Templates are added often and we're always open to taking suggestions!”
• 🔴 (20:05) User-provided Loops docs stated campaigns are the correct email type for one-off sends to an audience or segment; examples include newsletters, investor updates, product updates, and user feedback requests.
• 🔴 (20:05) User-provided Loops docs stated workflows are triggered by an event, a contact being added to the audience, or a contact property update.
• 🔴 (20:05) User-provided Loops docs stated transactional emails can be sent to any email address whether or not the recipient exists in Audience.
• 🔴 (20:05) User-provided Loops docs stated contacts can be added to Audience during transactional sends by setting "addToAudience": true in the payload.
• 🔴 (20:05) User-provided Loops docs stated workflow building includes an Event received trigger node for creating an event.
• 🟡 (20:05) Assistant concluded a new-post alert is a marketing newsletter, not a transactional email, because Loops classifies newsletters under Campaigns.
• 🟡 (20:05) Assistant concluded transactional sends target one email address per API call, ignore subscribed status, can reach unsubscribed contacts, omit unsubscribe links, and do not enforce double opt-in.
• 🟡 (20:05) Assistant concluded a pre-published Loops Workflow is unsuitable for mailing-list broadcasts because events target one contact rather than an entire mailing list.
• 🟡 (20:05) Assistant evaluated 2 approaches for unattended new-post email: (1) reusable action creates a ready campaign draft in Loops — recommended because Loops preserves consent, unsubscribes, suppression, and delivery; (2) provider-neutral reusable action with a different backend that supports compliant unattended marketing broadcasts — alternative if automatic send is required.
• 🟡 (20:05) Assistant specified the recommended Loops-ready-draft approach: read the Standard.site manifest; detect a new document; check Loops campaign history for the document AT-URI; create 1 campaign with the Loops mailing list, subject, excerpt, link, and send now when published; user reviews and clicks Publish in Loops.
• 🟡 (20:05) Assistant specified the provider-neutral unattended approach: keep the reusable GitHub Action and replace Loops campaigns with a provider/API that can create and send a compliant broadcast automatically while preserving mailing-list consent and unsubscribe behavior.
• 🟡 (20:05) Assistant specified implementation details for the Loops-ready-draft action: each repository provides LOOPS_API_KEY as a secret plus action inputs mailing-list-id, manifest-path, sender, and theme.
• 🟡 (20:05) Assistant proposed deterministic deduplication marker format in campaign names: [standard.site:<document-uri>] for retry-safe deduplication.
• 🟡 (20:05) Assistant asked whether to revise the plan for the ready-to-publish reusable action or design the provider-neutral action for unattended sends.