Built into Typestate.
Brevo
Send email through your own Brevo account.
Send my emails with Brevo on Typestate.
Brevo is on, through set_email.
Send an email
Your key goes in the cockpit, never through me.
Ready on Sandbox after the next deploy.
Your website or app
What it does for a business
- An action emails a person: "email the signed-in person: subject 'Your booking is confirmed', body ..."
- Sign-in links, password resets and address proofs go out on their own, from your address
- Sandbox keeps each mail as a pretend send you can read, so tests never reach a real inbox
Writes
What an action of your backend asks Brevo to do.
DoSend an emailSends one mail after the action commits. A flow that refuses sends nothing, and a provider that is down never fails the action. Sandbox keeps a pretend copy instead.
| Parameter | Type | Needed | What it is |
|---|---|---|---|
to | text | yes | One address or a list, at most 50. |
subject | text | no | The subject line. |
text | text | no | The plain text body. |
html | text | no | The HTML body. |
template | text | no | A template's name at the provider, instead of a body. |
variables | json | no | The values the template fills in. |
from | text | no | The sender. Left out, the one set_email names. |
reply_to | text | no | Where replies go. |
What it answers, for example
{
"email": "eml_62a",
"status": "queued"
}What it cannot do yet
- It sends. Reading mail that people send to you is not built.
- Contact lists and campaigns in Brevo are not part of this.
Add Brevo to your backend
You paste your Brevo key on the cockpit's Emails page.
Send my emails with Brevo on Typestate.Choose a planMore email and related integrations
Resend
Send email from your own address: sign-in links, receipts, reminders.
Amazon SES
Send email through your own Amazon Web Services account, at volume.
SendGrid
Send email through your own SendGrid account.
Made by Typestate, and not by Brevo. Brevo does not endorse Typestate. Brevo's own site