Help · Settings
Imports, integrations and your assistant
Settings has three pages for things outside the app: Imports, Integrations and MCP AI assistant. Each is a different kind of connection, which is why each has its own page.
Integrations
Settings → Integrations is where outside services that connect to your store will appear. An integration is a service that connects and keeps connecting — a reviews app, a loyalty program, another tool you already use — so that what it learns about a person reaches this store while you are using both.
There is none yet. The page says so, and it is worth a look only when you want to know what is there; as we build them, each one appears on it with what it would read and what it would do with it. Nothing on that page connects anything today, and nothing is hidden behind a setting you have not found.
Two things you may be looking for are not integrations, and each has a Settings row of its own. The import from the email tool you are leaving runs once and then you disconnect — that is the next section. Your MCP AI assistant is your own tool rather than a service connected to your store, and it has a section further down.
Importing from another email tool
Settings has a page where you import your work from the email tool you are leaving. One such tool is supported today, and the page is named after it. It is not an integration — nothing keeps connecting afterwards — which is why it has a page of its own, and why most stores visit it once and never again.
The page is in four parts, top to bottom, in the order you live them: your account there (the key, which account it opens, and where you disconnect), the import (one press, and the eight steps it runs), what arrived (your people, and what we could do with them), and reports (a record of every run, kept for good). Its own help page walks all four through.
The migration imports your profiles and what that tool recorded about their consent, your profile event history and your lists. Your segments, your email templates and your automations are imported one step at a time — every segment together, then every template, then every automation.
It is a migration, not a sync. You import everything once, you can import what has changed again while you are still sending from both, and then you disconnect. Nothing you import is ever written back the other way: the connection only reads.
Only your store's owner can connect an account, start a migration, import changes, or disconnect, and only the owner can see the key's last four characters. Everyone else on your team can see that a connection exists, watch it run, and read every report it produces.
It has a page of its own, because there is more to say about it than fits here — particularly about what arrives ready to email and what arrives held.
MCP AI assistant
Settings → MCP AI assistant is where you connect your own AI assistant to this store. It can read the store and write drafts for you, and it can never send anything: it drafts, you send.
Once it is connected it can write an email, a campaign, an automation or a segment as a draft. It can never send, schedule, publish, enable a message, cancel, delete, export your people, or change consent or a setting: it drafts, you send. An assistant has exactly the permissions of the team member who connected it and never more, so a viewer's assistant only reads. You can end any connection of your own from that page, and an owner or a manager can end anybody's. A connection also ends on its own after 30 days without being used. Connect your MCP AI assistant is the page for it.