Distillation

Date: Aug 5, 2026

• 🔴 (20:00) User stated missing condition variables in Loops email sections never fail the send; they only hide the section, so condition variables are optional at send time.
• 🔴 (20:00) User stated the newsletter architecture should add a form that submits to the newsletter service, replacing any approach that submits directly to Loops with an API key.
• 🔴 (20:00) User stated email addresses must remain only in the private service and Loops, and must never be put in AT Protocol records or the public repository.
• 🔴 (20:00) User stated the blog repository should contain only the Astro form, manifest client, and shared rendering helpers.
• 🔴 (20:00) User stated the blog repository must never contain Loops keys, subscriber data, or webhook secrets.
• 🔴 (20:00) User stated newsletter system architecture should store states received, approved, sent, and failed.
• 🔴 (20:00) User stated documents storage should include: tenant ID, document URI, content hash, title, URL, date, status, Loops campaign/message IDs, failure reason, and timestamps, with unique (tenant_id, document_uri).
• 🔴 (20:00) User stated the recommended MVP architecture is a small serverless service with managed SQL or KV storage.
• 🔴 (20:00) User stated the most AWS-aligned option is API Gateway/Lambda, DynamoDB, and a queue for Loops requests.
• 🟡 (20:00) Assistant documentation extract indicated Loops Create Campaign API creates a draft campaign and related email message in one request; only name is required.
• 🟡 (20:00) Assistant documentation extract indicated Loops Create Campaign returns id, emailMessageId, and emailMessageContentRevisionId.
• 🟡 (20:00) Assistant documentation extract indicated emailMessageContentRevisionId should be saved and passed back as expectedRevisionId when updating an email message to avoid 409 Conflict errors from stale revisions.
• 🟡 (20:00) Assistant documentation extract included Loops CLI command: loops campaigns create --name "Spring product announcement" -o json.
• 🟡 (20:00) Assistant documentation extract included Loops JavaScript fetch example using POST https://app.loops.so/api/v1/campaigns with Authorization: Bearer <your-api-key> and JSON body { name: "Spring product announcement" }.
• 🟡 (20:00) Assistant documentation extract included Loops JavaScript SDK example: import { LoopsClient } from "loops"; const loops = new LoopsClient("<your-api-key>"); const data = await loops.createCampaign({ name: "Spring product announcement" });
• 🟡 (20:00) Assistant documentation extract included campaign update example using POST https://app.loops.so/api/v1/campaigns/${campaignId} with JSON body containing audienceSegmentId.
• 🟡 (20:00) Assistant documentation extract referenced documentation index URL https://loops.so/docs/llms.txt.
• 🟡 (20:00) Assistant documentation extract referenced Loops API example pages: API Examples, Contacts API examples, Events API examples, Workflows API examples, and Transactional email API examples.