Integrations
Koltrix plays well with any system that speaks HTTP, SMTP, or webhooks.
Built-in
| Service | What we use it for |
|---|---|
| Clerk | Auth, organisations, multi-org switcher |
| Stripe | Billing — checkout, customer portal, webhooks |
| OpenRouter (or any OpenAI-compatible) | AI classify, summarise, auto-reply |
| Cloudflare | DNS-01 ACME challenges, edge proxying |
| MinIO (or any S3-compatible) | Email body + attachment storage |
| Meilisearch | Full-text search across your inbox |
SDK-style
| Language | Best path |
|---|---|
| Node | fetch for REST + nodemailer for SMTP (samples in Sending email) |
| Python | requests for REST + smtplib for SMTP |
| Go | net/http for REST + net/smtp for SMTP |
| PHP | PHPMailer over SMTP |
| Ruby | Net::SMTP or Net::HTTP |
Zapier / Make / n8n
Use Koltrix's REST API as a generic webhook target on the producer side, and configure outbound webhooks to send your events to Zapier/Make hook URLs.
Forms
Embed a form on your site that posts to your own backend, which then calls
POST /api/v2/lists/{list_id}/subscribers. Don't put the API key in the
browser — keep it server-side.
<!-- minimal hand-off -->
<form action="/api/subscribe" method="post">
<input name="email" placeholder="[email protected]" />
<button>Subscribe</button>
</form>// /api/subscribe handler
await fetch(`https://api.koltrix.com/api/v2/lists/${LIST_ID}/subscribers`, {
method: "POST",
headers: { Authorization: `Bearer ${process.env.KOLTRIX_KEY}` },
body: JSON.stringify({ email: req.body.email }),
});Inbound email parsing
Receive emails to addresses on your verified domain at Settings → Domains,
and they'll appear in the dashboard inbox. If you need to programmatically
handle them, hit POST /api/webhooks/inbound with the route you configured.