Sync Mailkick emails to Customer.io automations, broadcasts, and transactional messages
Connect Customer.io to update one or more message destinations with the HTML you build in Mailkick. Syncing updates the message content; it does not send the message.
Prerequisites
A workspace role with access to Settings → Integrations: Owner, Admin, or Editor.
A Customer.io App API Key.
Your Customer.io region: US or EU.
An Email block in your Customer.io automation. It can be empty or use an existing editor.
Step 1: Connect your workspace
In Customer.io, generate or copy an App API Key from your workspace’s API key settings.
In Mailkick, open Settings → Integrations and select Customer.io.
Paste the key and select Region (US or EU).
Fill in Site ID if you need it; otherwise leave it empty.
Click Save changes.
Step 2: Choose a destination
Add an Email block to your automation in Customer.io, or create a broadcast draft.
In Mailkick, save your email and open Export → Customer.io.
In the Customer.io panel, choose Automations or Broadcasts. Search by name or ID, then open an automation to see its emails.
Select the email or broadcast draft. Mailkick saves its destination and shows its name and status. Use Automations in the back button to return to your previous search.
Stopped and archived automations are excluded. Draft and running automations remain available. Results load in pages, and Mailkick fetches email blocks only for the automation you open.You do not need to open an editor, save placeholder content, or copy a URL. Mailkick updates classic Code emails directly and keeps their existing editor. Emails already managed through Design Studio continue to use the Design Studio API.
Replacing existing content requires confirmation. If Customer.io refuses a direct update because the content uses an unsupported editor, Mailkick asks for a separate confirmation before switching it to the Code editor in Design Studio. Mailkick saves the previous HTML and settings, but the backup cannot restore the old drag-and-drop structure.
You can also copy your email’s URL from Customer.io and use Paste a link instead. Mailkick recognizes current and older composer links, automation email blocks, linked Design Studio editor URLs, and broadcast pages with a single email variant. It checks the destination through your connected workspace before saving it and shows the email’s name.A standalone Design Studio URL may not identify its automation or broadcast. If Mailkick has no verified binding for that email, choose the destination using search. Automation overview pages without an email selection are not email destinations.
Step 3: Add more destinations
Click + Add destination below the selected email to select another automation email or broadcast. The Broadcasts tab includes one-time sends and API-triggered broadcasts. Sent, sending, scheduled, and multiple-variant one-time broadcasts appear under Unavailable broadcasts, with the reason they cannot be selected. A/B tests and translations require a separate export process because Design Studio links the entire broadcast.To use an existing URL, click Paste a link instead in the selector or the Destination actions menu. Transactional destinations still use this URL option and Customer.io’s Code editor.
You can also paste several Customer.io URLs into the destination panel, outside a text field. Mailkick checks all links before adding the batch, then removes duplicate destinations. If a link cannot be verified, the batch is not saved.
Step 4: Sync the email
Click Publish email. When there are several eligible destinations, the button shows how many will be updated.
Draft and other eligible destinations receive the email HTML.
Destinations marked Sent, Sending, Scheduled, Stopped, or Missing are skipped.
If every destination is skipped, there is nothing to sync and the button is disabled.
A failed destination shows its error on its card. Check the result for each destination when a sync is only partially successful.
Emails set to Do not send can be selected and synced. Their sending setting stays unchanged.Connected destinations sync in one click when Mailkick recognizes their current version. If the remote version is unknown or was changed in Customer.io, Mailkick asks Overwrite? before replacing it. The Emails page uses the same confirmation for individual and bulk sync. Switching an unsupported editor to Design Studio requires separate approval. Approval expires after five minutes and cannot be reused after the source or destination changes.Mailkick reads back classic email HTML and verifies an exact match, along with the existing delivery settings. Plain insertion layouts and bare HTML document envelopes are preserved. Layouts that add content, styles, or other design markup must be changed to a blank layout in Customer.io before syncing. Design Studio emails additionally pass Customer.io render and validation checks. Custom sender or reply-to values without an identity, CC settings, and managed emails with translations are refused when Design Studio cannot preserve them safely.Check and publish lets you check a destination again even when Mailkick shows it as up to date.
Use the Mailkick MCP
The MCP uses the same integration and permissions as Export:
search_customerio_actions uses the same automation browsing as Export: set kind: workflows and view: campaigns to find an automation, then use view: emails with its campaign_id to list its emails. Set kind: broadcasts for broadcasts. Omitting view keeps the existing flat email search. Follow the next cursor with identical filters, and never select results with disabled_reason.
update_email_metadata saves the selected destination in campaign_links.
sync_email with provider: customerio publishes the latest saved email. Set dry_run: true to inspect the destinations first.
If sync returns confirmation_required, the assistant must show you the destinations and reasons, obtain your approval, then retry with the returned token. A later conversion request requires separate approval. When several destinations are selected, synced_count reports any already updated destinations. These tools do not activate automations or send emails.
Troubleshooting
Issue
What to check
No destination is configured
Select an email in the Automations or Broadcasts list in Export → Customer.io.
The URL is not recognized
Copy the link while the email is open, or choose its destination using search. A standalone Design Studio link may not identify where the email is used.
The layout changes after sync
Automation and broadcast publication is blocked if Customer.io changes the HTML. For transactional messages, use the Code editor.
Region validation fails
Select US or EU in Settings → Integrations → Customer.io.
Nothing can be synced
Check destination statuses. Sent, sending, stopped, and missing destinations are excluded.
Authentication fails
Check the App API Key and the region selected in Mailkick.