CheckRoostCheckRoost
Integrations

Resend

Send alerts and digests from your own domain instead of ours, so the mail your client receives comes from you.

Resend is an email delivery service. CheckRoost uses one already, which is why alerts arrive with nothing connected. Adding your own key changes whose domain they are sent from.

What it does in CheckRoost

  • Alerts and digests come from a domain you have verified with Resend, not from ours.
  • Delivery, bounces and suppression appear in your own Resend dashboard, so when somebody says an alert never arrived you can check rather than guess.
  • A client asking why an outage alert came from somebody else has an answer.
  • CheckRoost still decides what to send and when. This changes who posts it.

Leaving it disconnected is a working setup

Alerts go out from this installation’s address with your organization’s name on them — “Acme IT via CheckRoost” — and replies go to your support address. Connect Resend when mail from your own domain matters to you.

Hooking it up

  1. Step 1. Verify your domain in Resend

    Do this first. Resend gives you DNS records to add wherever your domain’s DNS is hosted, and verification is what proves you may send as it. Until it is verified every send is rejected, so verifying afterwards means finding out on a real alert about a real outage.

  2. Step 2. Create an API key

    Resend→API Keys, with Sending access only, restricted to the domain you verified. That is all CheckRoost needs, and a key scoped that narrowly can send as that domain and do nothing else. A full-access key works too; CheckRoost then also checks the domain is verified before saving it.

  3. Step 3. Paste the key and a from address into CheckRoost

    Settings→Integrations→Resend, as an owner or admin. The address, such as [email protected], must be on the domain you verified. The key is checked against Resend before it is saved, and stored encrypted.

  4. Step 4. Send yourself a test

    Send a test email on the same screen sends one message to your own address, through exactly the path an alert takes — the same key, the same from address. The result appears beside the button within a few seconds, in Resend’s own words if it is refused. Do it now rather than finding a DNS problem on the day an outage alert does not arrive.

If a send fails

It is recorded as failed, with Resend’s reason, and never as delivered. The integration page shows the last error, so a key that stopped working is visible on the screen that connected it rather than discovered on the day an alert did not arrive.

Disconnecting

Removes the key and the from address, and mail goes back out from this installation’s address under your organization’s name.