Campaigns

Send & schedule Lettr campaigns

A campaign is a one-to-many marketing send to an audience list/segment. Campaigns are created and designed in the Lettr dashboard — the API does not create, edit, or delete them. From code you can list them, trigger or schedule a send, cancel a schedule, and pull engagement events.

1. Load the references

• SDK calls: detect the stack via ../_shared/detect-stack.md, then read ../_generated/sdk/<lang>/campaigns.md.
• Wire contract: ../_generated/api/index.md, Campaigns section.

2. The only operations that exist

If the user wants to create or change content/audience of a campaign, that's a dashboard task — tell them, don't look for an API that isn't there.

3. Gotchas

• Sending is irreversible and goes to real people. Always confirm the target campaign's name, audience size, and content with the user before calling send. Prefer schedule (which can be cancelled) over send when there's any doubt.
• The audience must be ready first. A campaign sends to whatever list/segment it's bound to. If that audience needs building or cleaning, do it in the audience skill before sending.
• scheduled_at is a timestamp — confirm the timezone interpretation with the user; an off-by-timezone schedule sends at the wrong hour.
• Idempotency: don't retry a send blindly on a network error — re-fetch the campaign status first to see whether it already started.

4. After sending

Report the campaign id and scheduled/sent status. For results, poll GET /campaigns/{id}/events (opens, clicks, bounces). Delivery problems on individual recipients are the diagnose skill.

What this skill does not do

• It doesn't build or clean the audience — that's audience.
• It doesn't author campaign content — that's the dashboard.
• It doesn't send transactional email — that's sending.