September 2026
- Dashboard
See if growth pays back on Grow → Revenue
Connect Stripe and Google Ads to see Paid LTV, CAC, and payback on one scoreboard. Incomplete names what’s missing, including identify after signup when ad clicks aren’t stitching to customers.
- Dashboard
Connect Google Ads and run Paid from Ranla
Connect your ad account in Settings → Integrations. Grow → Paid shows spend and structure. Ranla can propose campaigns and edits; live spend only changes after you approve.
- Dashboard
Talk to Ranla while you work
On Paid, Campaigns, Audience, and other growth pages, Ranla sits in a side column on the same conversation as Grow. Ask about what’s on screen without leaving the page.
- Dashboard
Edit what Ranla knows about your product
Settings → Context shows the product memory from your last repo scan. Read it, fix it. Ranla uses it for strategy and copy.
September 2026
- Dashboard
See your website traffic in Acquisition → Analytics
The snippet already on your site now records visitors, visits, pageviews, bounce rate, and engaged time. Open Acquisition → Analytics for any date range, break traffic down by channel, referrer, campaign, page, country, browser, or device, and click a row to filter the whole page. Revenue sits on the same chart, with the broadcasts you sent pinned to the days they moved it.
September 2026
- Dashboard
Collect email on on-site banners and modals
Choose Collect email on Growth → On-site to show an email field. Valid submits create a contact, credit Identified, fire on_site.email_captured for automations, and optionally go to an After submit URL. Set when to show (exit intent, scroll, delay), use separate messages per path, and open Acquisition to see which pages create contacts.
September 2026
- DashboardMCP
Send from PostHog, Amplitude, or Mixpanel moments you already track
Connect the analytics you already use, pick which events matter, and Ranla copies them for people with email into its own ledger, so you can segment, automate, and send without a GitHub PR. History from the last 30 days lands quietly; new events can trigger automations.
- Dashboard
Connect Amplitude or Mixpanel the same way as PostHog
Paste Amplitude or Mixpanel credentials in Settings → Integrations. Ranla can read which product events already fire, look up one person, and once you mark moments actable, sync them for sends.
- DashboardMCP
Connect PostHog so Ranla can read what people already do
Paste a read-only PostHog key in Settings → Integrations. Ranla can see which product events already fire and what one person did this week, then mark moments actable when you are ready to send on them.
August 2026
- Dashboard
Ranla starts with a plan
After the welcome conversation, Ranla opens your first work thread by reflecting what it learned, proposing the first lifecycle flows, and asking whether to implement them.
August 2026
- Dashboard
Stop a Ranla turn while it is running
While Ranla is working, Send becomes Stop. Click it (or press Return) to cancel the current turn. Pending approvals and in-progress sends do not continue, and you can send a new message right away.
- MCP
Drive Ranla from Claude or Cursor over MCP
Connect supersendtx-mcp or ranla-mcp and message Ranla without opening the dashboard: start a durable thread, send turns, list and approve gated actions, and use read-only growth tools. Mutations still go through Ranla so approvals stay in the loop.
- Dashboard
Import large contact and suppression CSVs
Upload migration-sized CSV files from Audience or Suppressions. Imports run in the background and show up on Monitor → Imports, with a scope picker for suppression lists so marketing opt-outs do not block transactional mail.
- Dashboard
Edit campaign copy yourself
A campaign’s Content tab is now editable: change the subject, preheader, body and template slots in place and save. Works while a campaign is a draft, scheduled or paused, and pending recipients pick up the new copy on the next send.
- SDK
npm package ranla
Install the Ranla API client with npm i @supersend/ranla. new Ranla(key) sends to api.ranla.ai by default. Existing supersendtx installs are unchanged.
- API
New API keys start with rnl_
Newly created API keys start with rnl_. Existing stx_ keys keep working, and both prefixes are still accepted on the API.
- Dashboard
Reply to inbound mail from the dashboard
Inbound is now an inbox: messages are grouped into conversations, you can read the whole thread with your own replies in it, and reply or reply-all without leaving SuperSend TX. Threads can be marked unread or archived.
- APISDK
API keys with stx_ or rnl_ prefix
Bearer API keys may start with stx_ or rnl_. A rnl_ key with the same secret after the prefix authenticates as the existing key. Newly created keys still start with stx_. Official SDKs and MCP accept both prefixes.
- Dashboard
Preview and test campaign emails
On a campaign’s Content tab, Preview shows the email as a chosen recipient would see it, and Send test delivers a copy to any inbox using that contact’s details.
- Dashboard
Export suppressions to CSV
Export the current Suppressions filters from the toolbar. The file lands on Monitor → Exports and stays available for 30 days.
- Dashboard
Export inbound messages to CSV
Export the current Inbound filters from the toolbar. The file lands on Monitor → Exports and stays available for 30 days.
- Dashboard
Export emails to CSV
Export the current Emails filters from the toolbar. The file lands on Monitor → Exports and stays available for 30 days.
- Dashboard
Export campaigns to CSV
Export the current Campaigns filters from the toolbar. The file lands on Monitor → Exports and stays available for 30 days.
- Dashboard
Export Audience contacts to CSV
Export the current Audience contacts filters from the toolbar. The file lands on Monitor → Exports and stays available for 30 days. You get an in-app notification when it is ready.
- Dashboard
Send a real test email from an automation
On an automation’s test panel, Send test email delivers a real message to the address you enter and skips delays, without activating the flow. Dry-run still simulates without sending.
- Dashboard
Install wires Audience contacts at signup
When SuperSend TX setup instruments your repo, it upserts contacts with POST /contacts at signup (plus lifecycle events). CSV import stays for backfill. Live users should come from your product.
- Dashboard
Ranla can read your codebase, if you allow it
Ranla asks before reading source files. If you allow it, it studies the repo so it can write product copy and make decisions from the actual product, not just commit titles. Turn it off anytime in Settings → Integrations.
- Dashboard
Import contacts from CSV
Drop a CSV on Audience, or add contacts from your app with POST /contacts. Extra columns become attributes you can segment on.
- Dashboard
Paste HTML templates in the dashboard
Create a template as Paste HTML (or keep using the visual builder). Raw-HTML templates now include preheader and Test send, and switching to the visual builder asks for confirmation before deleting your HTML.
- Dashboard
Automation dry-run tests
Test a draft or paused automation from the canvas without activating it. Dry-run skips delays/waits and stubs email/SMS so you can verify the flow before going live.
- DashboardInfra
Free production sending
After you verify a domain and add a payment method (no charge until you upgrade), Free includes real sends to any recipient: 3,000/mo · 100/day · 1 domain. Upgrade when you need more volume.
- SDK
Public Nodemailer transport source
supersendtx-nodemailer now ships the full transport implementation in its public GitHub repo (not a re-export stub). Prefer import from supersendtx-nodemailer; supersendtx/nodemailer still works.
- Dashboard
Username login and profile settings
Sign in with your email or a username on the password form. Settings → Profile lets you set a username, update your name, and set or change your password with an email verification code.
- SDK
Symfony Mailer transport
composer require supersendtx/symfony-mailer for a first-class Symfony Mailer transport (DSN supersendtx+api://…). Laravel’s mailer uses the same package under the hood.
- SDK
Clerk and Payload email adapters
Deliver Clerk email.created webhooks with supersendtx-clerk, and wire Payload 3 email with supersendtxAdapter from supersendtx-payload. Guides at /guides/clerk and /guides/payload.
- SDK
Auth.js / NextAuth email provider
Drop-in magic-link provider for Auth.js. npm install supersendtx-authjs, add SuperSendTX({ from }) to providers, set AUTH_SUPERSENDTX_KEY. Same pattern as other Auth.js email providers; requires a database adapter.
- Dashboard
Guided setup: test, domain, and code in one place
New accounts land in a full-screen setup flow: five quick questions, then a hub with the three things that actually matter: send a test email, connect your sending domain, and add SuperSend TX to your code. Do them in any order. The domain and the code both finish in the background, so you can start them and come back; the hub keeps their status and is always reachable from Guided setup in the sidebar. On the code step, connect the SuperSend TX GitHub App and an agent installs the SDK, adds the environment variable, wires one real send path, and opens a pull request you review like any other. Inference is on us, no API key needed. Prefer to wire it up by hand? That tab is still there.
July 2026
- DashboardDocs
Visual template builder v2
Block editor with slash menu, drag reorder, versioned publish and restore, starter gallery, global CSS, read-only Code tab, and templates push from git. Sends resolve the published version. Draft edits never break live traffic.
July 2026
- SDKDocs
Official SDKs for Python, PHP, Ruby, and Go
The Node client is no longer the only one. supersendtx is on PyPI and RubyGems, supersendtx/supersendtx is on Packagist, and the Go module is at github.com/Super-Send/supersendtx-sdks/go, plus a supersendtx/laravel package with config and a facade. Every client wraps the same REST contract, so from / to / subject / html works the same everywhere.
- APIDashboard
Account-scoped SMTP relay
Create SMTP credentials in the dashboard and send through smtp.supersendtx.com with the same domain verification and billing rules as POST /emails, for Supabase custom SMTP, Clerk, and legacy apps.
- Docs
Supabase Auth integration guide
Docs and marketing page for wiring Supabase Send Email hooks to SuperSend TX via an Edge Function: signup, reset, magic link, and invite mail on your domain.
- DashboardAPI
Webhook test events in the dashboard
Send signed test payloads from /webhooks, see per-endpoint HTTP results, and verify SuperSendTX-Signature handling without leaving the app.
- DashboardAPI
Inbound MX on DNS apply
Apply DNS now provisions inbound MX for Cloudflare and GoDaddy when inbound is enabled on a domain. GoDaddy credentials can be stored in Settings → Integrations like Cloudflare.
- MCPDocs
Smithery listing
SuperSend TX MCP is published on Smithery (SuperSend/supersendtx-mcp) with OAuth connect for agent toolchains.
- MCPAPI
Hosted MCP OAuth
Remote MCP clients can authorize via OAuth at app.supersendtx.com and connect to mcp.supersendtx.com without pasting API keys.
- DashboardDocs
Starter template gallery
Five published starters (password reset, verification, welcome, receipt, team invite) with copy-into-account from the templates dashboard.
- Docs
React Email guide
Docs guide for sending with the react field, peer dependencies, and preview workflow using create-email.
- MCPAPI
Hosted MCP + expanded tools
mcp.supersendtx.com serves streamable HTTP MCP with Bearer stx_ auth. MCP tool surface expanded across domains, webhooks, templates, and deliverability.
- DocsMCP
Agent Skills
Official Agent Skills for Cursor and compatible agents, plus /ai/agent-skills docs and .well-known discovery.
- DashboardAPI
Inbound email dashboard
Received messages list and detail view for domains with inbound enabled, with email.received webhooks.
API contract
Breaking API changes are announced here and in the OpenAPI spec. SDK and CLI versions on npm follow semver for the public client packages.