Bupple with MailerSend

MailerSend sends the email; Bupple makes what is in it. MailerSend has nothing to call Bupple with, so it sits after the step that hears Bupple's result: an automation's Send the result › A webhook into Zapier, n8n, Make or your own code.

Send the email

From that step, call MailerSend's API:

curl -s -X POST https://api.mailersend.com/v1/email \
  -H "Authorization: Bearer $MAILERSEND_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
    "from": { "email": "hello@yourcompany.com" },
    "to": [{ "email": "dana@acme.com" }],
    "template_id": "your-template-id",
    "personalization": [{ "email": "dana@acme.com", "data": { "first_name": "Dana", "video_link": "https://…" } }]
  }'

• to and the first_name come from the result's input — the lead you started the run with.
• video_link is the file's public_url — add A public link to the automation's Send the result so the webhook carries it.
• In the MailerSend template, write {{video_link}} and {{first_name}}. A personalisation key cannot contain a dot.

Without a template

Send subject and html instead of template_id, with the run's draft (drafts[0]) as the body — for example, the welcome note from A welcome note for a new lead, after your team has read it.