Hand off to your ESP
The MCP builds drafts but doesn't upload or send. How a draft built by your assistant gets to Salesforce Marketing Cloud, Marketo, Braze and the rest.
The flow today
AI host ──MCP──▶ Stensul draft ──you──▶ review, approve, complete ──▶ Upload to ESP ──▶ send from your ESP- Your assistant builds the draft and gives you the edit link.
- You open it in Stensul, review it (copy, images, custom buttons, mobile), and run it through your approval workflow.
- You complete the email. Mandatory accessibility and brand rules must pass first.
- You upload it with Upload to ESP in Stensul. The ESP connector must be connected by an admin and added to the library, and you need the
upload_esppermission. - You send from your ESP as usual.
Connectors
See Integrations for every ESP and marketing automation platform Stensul uploads to.
Automating the last mile
If you need completed emails to reach another system automatically, Stensul can POST each completed email to a webhook you host, signed with an X-Stensul-Signature HMAC-SHA256 header. For server-to-server work there’s also the Stensul REST API, which can render an email as HTML, PDF or PNG. Both are set up by an admin; the webhook is covered in the Stensul help center.