Your Resend account, your domain, your sending reputation.

What the Resend integration actually does

Once your Resend key is connected to your workspace, Creaiter uses it to send campaign email. The chat can draft the campaign, generate the copy for it, and dispatch it through Resend without you assembling the message in a separate tool.

Personalization runs through merge tags, so a field like a first name resolves per recipient rather than shipping to your customers as literal text in curly braces. Links can carry campaign tracking parameters, which is what makes the analytics side able to tell you later which email drove the visit.

• Campaign email is sent through your own Resend account and API key
• Merge tags resolve per recipient rather than going out as raw placeholders
• Campaign tracking parameters can be added to the links in a send
• A view in browser link is generated for recipients whose client mangles the layout
• Sends are paced in batches on a schedule rather than fired all at once
• Your workspace's own key is used when one is connected, and Creaiter reports which key sent a campaign

How to connect Resend

Two accounts, one paste. The part that takes the longest is not Creaiter's step, it is verifying your sending domain inside Resend, because that involves DNS records and DNS takes as long as DNS takes.

• Create a Resend account at resend.com if you do not have one
• Add your sending domain in Resend and complete their DNS verification
• Create an API key in Resend and copy it once
• In Creaiter, open Settings, then Integrations, then the Resend card
• Paste the key and save it
• Send a test to yourself before you send to anyone else

Compliance is built into the send, not left to you

Every campaign email Creaiter dispatches carries the pieces a legitimate marketing email is supposed to carry: a working unsubscribe link, the header that lets an email client offer one click unsubscribe, and a postal address in the footer.

Unsubscribes are then honored on the way out. Before a send, Creaiter checks the recipient against the do not send list, so someone who opted out does not receive the next campaign because a list got re-imported. This is not a setting you can forget to switch on, which is the point.

Sends are also paced rather than blasted. A brand new sending domain that fires thousands of messages in one minute is teaching every inbox provider to distrust it, and that damage is difficult to undo. Batching is slower and it protects the asset you actually care about.

What day to day looks like

You describe the campaign in the chat. Creaiter drafts it, you edit, and you send. The message goes out over your Resend account, from your domain, with unsubscribe handling attached.

Because the drafting, the sending and the content repository all sit in one place, the email that supports a blog post is written next to the blog post rather than reconstructed from memory in another tool two weeks later.

What the Resend integration does not do

The honest boundary, including the parts that cost you money elsewhere.

• It does not give you a Resend account. You create one, and Resend bills you directly under their own pricing
• It does not verify your sending domain for you. That is DNS work you complete inside Resend
• It does not send campaign email through a different email provider. Resend is the campaign send path
• It does not rescue a poor sending reputation, warm a cold domain overnight, or guarantee inbox placement
• It does not run paid advertising on any network
• It is not a sales CRM, and it does no backlink auditing