> ## Documentation Index > Fetch the complete documentation index at: https://help.emaillove.com/llms.txt > Use this file to discover all available pages before exploring further. # Push to your email platform > Every email platform the Builder can push to, what each one asks for when you connect it, what a push creates, and the options in the push dialog. The Builder can push a finished email straight to 27 platforms. A push creates a template, campaign or draft in the platform, with the HTML written for it: its merge tags, unsubscribe links and condition code. For any other platform, download the HTML. See [Export and download](https://help.emaillove.com/builder/sending/export.md). ## Connect a platform 1. Go to **Integrations**. Only workspace owners and admins can open it. 2. Under **Email service providers**, click the platform. 3. Enter the details it asks for (see the table below). Each panel has a **Where to find these** link to the platform's own help. 4. Save. Saved keys are never shown again. To change one, enter a new one. Leaving the field blank keeps the old one. To connect a second account on the same platform, open the platform and click **Connect another account**. Give each account a name, so people can tell them apart in **Share**. You can connect platforms on any plan. Pushing is part of the Builder plan. ## Push an email 1. Open the email and click **Share**. 2. Under **Send to your ESP**, click the platform, or the account. 3. Check the options in the dialog and confirm. After a push, **Open in** the platform appears in **Share**. When you push the same email again, you choose whether to update what you pushed before or make a new one. Some platforms always make a new one (see the table). If the Builder can't tell whether a push went through, it says **Check your ESP before retrying**. ## Platforms ### Built-in platforms | Platform | What it asks for | Options when you push | | - | - | - | | **Braze** | **Braze instance** (for example US-01 or EU-01) and a **REST API key** with templates.email create, update and list. Add content\_blocks create and update to push content blocks. | **Export as** an email template or a content block. **Add translation tags**, and **Tag link addresses too**. | | **Iterable** | **Data center** (US or EU) and a server-side **API key** with email template permissions. Optional: from name, from email, reply-to email. | **Export as** an email template or a snippet. **Message type**. **Also send approved translations as locales**. | | **Adobe Marketo Engage** | **REST API endpoint** (the Munchkin ID also works), **Client ID** and **Client Secret**. Then a **Template folder**. | Optional: approve emails after each sync, make text and images editable in Marketo, copy images into Marketo. | | **Salesforce Marketing Cloud** | **Client ID**, **Client secret** and **REST base URI**, from SFMC Setup › Apps › Installed Packages. | **Add link aliases** and **Track link conversions**. | ### Connectors | Platform | What it asks for | What a push makes | Pushing again | | - | - | - | - | | **Acoustic** | Pod, client ID, client secret, refresh token, database ID, from name, from address, reply-to address. Optional folder path and visibility. | Mailing template | Updates it | | **ActiveCampaign** | API URL and API key | Template | Updates it | | **Airship** | App key, master secret and region (US or Europe) | Email template | Updates it | | **Blueshift** | User API key and region (US or EU) | Email template | Makes a new one | | **Brevo** | API key. Optional sender name and email. | Transactional template | Updates it | | **Customer.io** | App API key and region (US or EU) | Design Studio email. Choose **HTML email** or **Editable Design Studio components**. | Updates it | | **Emarsys** | API username and secret, email category ID, contact list ID, sender name and email | Email campaign | Makes a new one | | **HubSpot** | Private app access token (pat-…) | Coded template, in an "EmailLove" folder | Makes a new one | | **Klaviyo** | Private API key (pk\_…) | Template. Choose **HTML template** or **Editable text and images**. | Makes a new one | | **Mailchimp** | API key (ending in your data center, such as -us21) | Template | Makes a new one | | **MailerLite** | API token, sender name and email | Draft campaign | Updates it | | **MailerLite Classic** | API key, sender name and email | Draft campaign | Updates it | | **Mailjet** | API key and secret key | Template | Updates it | | **MoEngage** | Workspace ID, API key, data center, sender name, and the email of the person creating it. **Export as** an email template or a content block. | Custom template | Makes a new one | | **Netcore** | API key | Template | Makes a new one | | **OneSignal** | App ID and app API key | Email template | Makes a new one | | **Pardot** | Salesforce domain, business unit ID, consumer key and secret, Salesforce username, password and security token | Email template | Updates it | | **Postmark** | Server API token | Template | Updates it | | **Sailthru** | API key and shared secret | Template | Updates it | | **SendGrid** | API key and region (Global or EU) | Dynamic template | Updates it | | **SendX** | Team API key | Email template | Updates it | | **Stripo** | API authentication token. Optional template folder ID. | Editable template | Makes a new one | | **Zeta** | Site ID and REST API key. Optional template tags. | HTML template | Updates it | ## Import merge tags from your platform For some platforms, workspace owners can import the platform's merge tags into **Dynamic Content**: Iterable, Braze, Marketo, HubSpot, Mailchimp, SendGrid, Brevo, ActiveCampaign, Mailjet, MailerLite, MailerLite Classic, SendX, Blueshift and Acoustic. See [Conditions and merge tags](https://help.emaillove.com/builder/editor/conditions.md#merge-tags). ## Platforms you can't push to For Dotdigital, choose it under **For** in **Share**, then copy or download the HTML and paste it into Dotdigital. For any other platform, choose **HTML (fallbacks)**. ## Plans Pushing to a platform counts as an export. The Free plan has no exports. The Builder and Enterprise plans have unlimited pushes. See [Plans and billing](https://help.emaillove.com/builder/plans/overview.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.