Built-in · Messaging and email

Resend, in every client’s workflows.

Email from the client’s own domain, with files from the run attached, with the client’s own Resend account.

Do it in Resend

A step of its own, sent through the client’s Resend account.

Send an emailEmail from the client’s own domain, with files from the run attached

On the client’s page in Thrum: Add credential, type Resend (email).

An API key from the client’s Resend account and the from address on their verified domain.

The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.

When Resend stops answering or refuses the client’s key, you hear about it, and your client does not.

A failing request: Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause: Given it, up to an hour
Requests at once, per account: 2, per worker; the rest wait their turn
Timeout: 15 seconds, unless the step sets its own
Private and internal addresses: Refused, on every redirect too
The client’s key: Encrypted, bound to the client, and kept out of every run record
A step that keeps failing: Marks the workflow Degraded and alerts you, not the client

Resend and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.

Get early access and you’ll be among the first in. Early members get a launch perk.