ESP Integrations

Temway exports clean HTML you can paste into any provider (see Export and HTML). For twenty popular ESPs, you can skip the copy-paste entirely: connect your account once and push a rendered email straight into your ESP as an editable template.

This is the native companion to manual export. It keeps you in control of sending, deliverability, and audiences — Temway only writes a template into the ESP you already use.

Supported providers

Temway ships with twenty built-in ESP connectors. Each pushes your rendered email as an editable asset on the ESP side.

Why HubSpot creates a draft email, not a template: HubSpot’s Design-Manager templates require HubL markup. A marketing email accepts raw HTML, so Temway creates a draft you can review and publish from HubSpot.

Why Kit creates a draft broadcast: Kit (formerly ConvertKit) has no native HTML-template resource — its content unit is a broadcast. Temway creates a draft broadcast carrying your HTML so you can review and send from Kit.

Mailjet credential format: Mailjet uses an asymmetric key pair (API key + secret key). Enter both in a single field separated by a colon: your-api-key:your-secret-key.

ActiveCampaign account URL: ActiveCampaign hosts each account on its own subdomain (https://youraccount.api-us1.com). Temway asks for that URL alongside your API key at connect time so requests reach the right host.

Dotdigital region URL: Dotdigital hosts each account’s API on a region-specific host (for example https://r1-api.dotdigital.com for region 1). Find yours in Dotdigital under Settings → Access → API Users. Temway asks for it alongside your API username at connect time.

iContact credential format: iContact uses a three-part credential (App ID, username, and password). Enter all three in a single field separated by pipes: your-appId|your-username|your-password. Find them under iContact → Settings → Web Tools.

MailerLite sender requirement: MailerLite’s campaigns API requires a verified sender on your account, and exposes no way to list senders from outside. Temway verifies the key on connect, but the push fails with a clear pointer to the MailerLite senders screen until at least one sender is configured.

Plan requirements

ESP integrations are available on every plan, including Free. There’s no separate cap on connections or pushes — instead, pushes share the same monthly allowance as exports (downloads).

Pushing to an ESP reuses a render of your email, and each render is one of your monthly exports. Paid plans have unlimited exports, so pushes are unlimited too; on Free, pushes draw from the same 10-per-month pool as downloads. See Billing and Plans for how exports are counted.

Connecting an ESP

Connections are created at the workspace level by anyone with editor access. You connect once per workspace; every email in that workspace can then push to any connected ESP.

1. Open your workspace’s integrations settings.
2. Choose a provider and paste your credential.
3. Temway verifies the credential live before saving — if the key is invalid or lacks the required scope, the connection is rejected with a clear message.
4. Once verified, the credential is encrypted and stored. The connection appears in your list with an active status and the account name it resolved to.

Credentials by provider

• Mailchimp — your API key, which includes the data-center suffix (for example a1b2c3d4e5f6g7-us21). Temway reads the suffix to route requests to the right data center.
• Klaviyo — a private API key from your Klaviyo account settings.
• HubSpot — a private app access token. The app must grant the marketing-email write scope; without it, verification hints at a missing scope and pushes will fail.
• Campaign Monitor — your API key. Campaign Monitor scopes templates to a client, so after verifying your key Temway asks you to pick which client the templates should land in.
• SendGrid — an API key starting with SG.. Create one in SendGrid under Settings → API Keys with Restricted Access (Templates: Read & Write is sufficient).
• Brevo — your Brevo v3 API key. Temway reads your account’s primary sender at connect time so pushes can attach it to the template automatically.
• Postmark — a server token (not an account token). Find it under your Postmark server’s API Tokens tab.
• Mailgun — your Mailgun API key. Temway auto-detects whether your account lives on the US or EU region (trying US first, falling back to EU) and captures your first active sending domain at connect time.
• Mailjet — both your API key and secret key combined as apiKey:secretKey in a single field. Find them under Account Settings → Master API Key & Sub API Keys.
• Omnisend — your Omnisend API key from Settings → Notifications → API Keys.
• MailerLite — an API token from Integrations → API Tokens with Read/Write access. A verified sender must already be configured on the account before pushing.
• ActiveCampaign — your API key from Settings → Developer, plus your account URL (for example https://youraccount.api-us1.com). Both are entered together at connect time.
• GetResponse — your API key from My Account → API & OAuth. Temway reads a campaign and “from” field at connect time so pushes land in the right place.
• MailerSend — an API token from Settings → API Tokens. A domain must already be verified on the account.
• Moosend — your API key from Settings → API Keys. Temway reads a mailing list at connect time so pushes land in the right place.
• Kit — your Kit API key from Settings → Advanced → API Secret Key. Kit (formerly ConvertKit) authenticates via the X-Kit-Api-Key header.
• Dotdigital — your Dotdigital API username, plus your region’s API URL (for example https://r1-api.dotdigital.com). Dotdigital hosts each account on a region-specific API host; find yours in Dotdigital under Settings → Access → API Users. Both are entered together at connect time.
• Mailtrap — your Mailtrap API token from Settings → API Tokens. Temway lists templates on connect to verify the token.
• Elastic Email — your Elastic Email API key from Settings → API Keys → SMTP/API. Temway reads your account on connect.
• iContact — your App ID, username, and password combined as appId|username|password in a single field. Find all three under iContact → Settings → Web Tools. Temway reads your account, client folder, and campaign at connect time.

Reconnecting and removing

• Test an existing connection at any time to re-verify the stored credential. Temway marks it active or error based on the result and surfaces the error message if it failed.
• Delete a connection to revoke Temway’s access. Deleting the connection does not delete any templates already pushed to your ESP — those remain in your provider account.

Pushing an email to your ESP

Once a connection exists, pushing an email creates an editable template (or draft email, for HubSpot) in your ESP.

The push flow

1. Render the email. A push uses a specific, completed render of your email — the same render you’d download or test-send. The render must be an email-target render (the inbox-ready HTML), not a web preview.
2. Push. Choose the connection and push. Temway starts the push right away — you don’t wait in the builder.
3. Temway creates the template. Using your stored (encrypted) credential, Temway writes the rendered HTML into your ESP as a new template.
4. Done. The new template appears in your ESP, named after your email (you can override the name at push time).

Each push references an explicit render, so the HTML your ESP receives is exactly the version you approved — never a “latest” render that might change underneath you.

What lands in your ESP

• Mailchimp — a new template under Templates → Code Your Own, ready to use in a campaign.
• Klaviyo — a new code template in Content → Templates, with the code editor open for tweaks.
• HubSpot — a draft marketing email carrying your HTML. Open it in HubSpot, adjust if needed, and publish or schedule from there.
• Campaign Monitor — a new template under the client you selected. Because Campaign Monitor can’t import inline HTML directly, Temway temporarily publishes the HTML so Campaign Monitor can fetch it during the push, then the template is yours.
• SendGrid — a new dynamic template under Templates, with your HTML as the first active version. The subject line defaults to your email’s name (editable in SendGrid).
• Brevo — a new transactional template under Campaigns → Templates, with your sender pre-filled.
• Postmark — a new standard template under Templates, with the subject line defaulting to your email’s name.
• Mailgun — a new template under the sending domain Temway resolved at connect time, with your HTML as the initial version.
• Mailjet — a new template under Campaigns → My Templates, with your HTML attached as the content.
• Omnisend — a new template under Messages → Templates, imported with your HTML ready for campaigns.
• MailerLite — a new draft campaign under Campaigns, carrying your HTML ready to review and schedule. (Requires a verified sender on the account — see the note above.)
• ActiveCampaign — a new template under Design → Templates, ready to attach to a campaign or automation.
• GetResponse — a new draft newsletter under your campaigns, carrying your HTML ready to review and schedule.
• MailerSend — a new template under Templates, ready to attach to transactional and marketing sends.
• Moosend — a new draft campaign under Campaigns, carrying your HTML ready to review and schedule.
• Kit — a new draft broadcast under Broadcasts, carrying your HTML ready to review and schedule.
• Dotdigital — a new campaign under Campaigns, carrying your HTML ready to review.
• Mailtrap — a new HTML template under Email Templates, ready to use in a campaign or test.
• Elastic Email — a new template under Templates, ready to use in a campaign.
• iContact — a new message under the client folder and campaign Temway resolved at connect, ready to review and schedule.

You can push the same email multiple times — each push creates a new template in your ESP rather than overwriting a previous one.

Security

Temway treats ESP credentials with the same care as authentication secrets.

• Encrypted at rest. Credentials are encrypted with AES-256-GCM before they’re stored. Only ciphertext is ever saved — never plaintext.
• Write-only. Credentials are never shown again after you save them — not in the UI, not in logs. Only a non-sensitive account label (for example, your Mailchimp account name) is displayed.
• Decrypted only at push time. The credential is decrypted only for the moment a push needs it, then discarded.

Next steps

• Prefer the manual route? See Export and HTML to copy rendered HTML into any ESP.
• Every publish is snapshotted in version history — push a previous version by restoring it first.
• Compare what each plan includes in Billing and Plans.