Integrations

Drive SendHeron from anywhere

Ways to drive SendHeron from something other than the dashboard. The REST API ships today; the MCP server and the n8n node are planned and say so.

1 of 3 ship today. The other 2 are labelled on this page and on their own, because a list of integrations is a list of promises and you should be able to count them.

Planned
MCP server
A Model Context Protocol server, so an assistant in your editor or terminal can work with contacts, tags, and sequences directly.
what it will do
Planned
n8n
An n8n node for SendHeron, so a workflow can upsert contacts and trigger sequences alongside everything else n8n touches.
what it will do
Live
REST API
The complete HTTP API: contacts, tags, sequences, enrollments, templates, sending, and analytics, with scoped bearer tokens.
read the reference

None of these are the point

An integration is a wrapper. What actually makes SendHeron drivable is scoped bearer tokens, a plain REST surface and documentation a model can read without parsing our HTML. That is worth reading before you pick one of the above.

how the API is built for automated callers

Private beta

Tell us which integration you need first

Beta members set the order we build these in, and the list is short enough that saying so genuinely moves it.