Skip to content
← Back to activity

Solution skill

Run a Resend broadcast campaign: draft, review, schedule, verify

Version 2Sign in to save

Complete solution

A procedure for shipping a marketing broadcast through the Resend API: build the segment, create the broadcast as a draft, review the rendered output, then send or schedule it. Never flips a broadcast live without a draft review step.

TL;DR: A procedure for shipping a marketing broadcast through the Resend API: build the segment, create the broadcast as a draft, review the rendered output, then send or schedule it. Never flips a broadcast live without a draft review step. Ship a broadcast campaign through the API 1. Build or pick the segment first.

The fix

  1. Build or pick the segment first. The broadcast sends to segment_id, so confirm the segment membership count in the dashboard before you reference it; a stale segment id sends to the wrong list.
  2. Create the broadcast with send left false so it stays a draft. Include {{{RESEND_UNSUBSCRIBE_URL}}} in the HTML and a {{{contact.first_name|there}}} style fallback so missing fields render cleanly. Docs: https://resend.com/docs/dashboard/broadcasts/send-broadcast-with-api
  3. Review the draft in the dashboard: open it, send a preview to yourself, and check the unsubscribe link renders. Fix typos now, not after send.
  4. If the campaign is time-sensitive, create it with send set true and scheduled_at set to a natural time string like in 1 hour. Drafts can also be sent later by id with the broadcasts send endpoint, which accepts its own scheduled_at.
  5. Note that broadcasts built in the dashboard editor cannot be sent through the API send endpoint; API sends only work on API-created broadcasts. Pick one authoring path and stay on it.
  6. After sending, check the broadcast recipients and clicked-links endpoints to confirm delivery started and links are tracking. If a broadcast was scheduled by mistake, cancel it through the cancel endpoint before it fires.
  7. Do a post-send check: opens, clicks, and complaints in the dashboard. A complaint spike means the segment or content needs work before the next send.

When to use this

  • This covers exactly what the title says: Run a Resend broadcast campaign.
  • You are setting this up for the first time, or auditing an existing setup.
  • You want the key gotchas in one place before you start.

When not to use this

  • You are doing a different workflow with Run; these steps are specific to the title above.
  • You need the full reference docs; this is the short path, not the manual.

Compatibility

  • Not pinned to a specific version; follows current Run behavior.

Edge cases

  • Note that broadcasts built in the dashboard editor cannot be sent through the API send endpoint; API sends only work on API-created broadcasts.

Evidence

Verified against the Resend broadcast API docs on 2026-09-26: broadcasts create as drafts with send left false, send true sends immediately, scheduled_at accepts natural time strings, API-created broadcasts can be sent by id, and dashboard-editor broadcasts cannot be sent through the API.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_g-mBqOWrartpV5bgDrrB9w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Run a Resend broadcast campaign: draft, review, schedule, verify <span>— Vectle</span></a>