This guide is for marketers, agencies and developers who already use the Mailercloud connector and want to get more out of it: chaining steps, working precisely with IDs, and combining Mailercloud with other tools in the same chat.
Use IDs once you have them. Every list, campaign, template, segment and contact has an ID, shown in the assistant's answers. "Use list HwauaS" is never ambiguous; "the newsletter list" can be.
Ask for a dry run. Add "dry run first" to any create or update request. You see exactly what would be saved, and nothing changes.
Expect previews for risky steps. Sending, scheduling, deleting, blocking addresses, removing tags, pausing webhooks and replacing segment rules always show a preview first. Reply yes in your next message to go ahead. Approve each preview yourself; don't tell the assistant to skip them.
Read results back. After a change, ask the assistant to fetch the item again ("show me the segment now") to confirm it saved as you meant.
You can ask for a whole job in one message. The assistant does the steps in order and stops for your approval where needed.
Re-engage inactive subscribers
"Make a segment of contacts on the Newsletter list who haven't opened any of the last five campaigns. Then draft a win-back campaign to that segment with the subject 'Still want to hear from us?', one button to https://www.example-shop.com/preferences, and our address in the footer. Audit the draft and send me a test."
Repeat a winning campaign
"Find my best campaign of the last 90 days by click rate. Make a new draft from the same template for the Customers list, with a fresh subject line. Show me three subject options first."
Weekly report
"Compare the campaigns sent this week with last week: opens, clicks, unsubscribes and bounces. Show a table, flag anything worse than usual, and suggest one test for next week."
Segments can combine rules with "match all" or "match any", across one or more lists or your whole audience. Rules can use:
Tags: tagged or not tagged, with any or all of the tags you name.
Campaign activity: opened, clicked, not opened or not clicked, for example in the last month or in the last five campaigns.
Contact details: built-in fields such as country, city or job title (equal to, contains, is known, and so on), and mailbox provider such as Gmail.
To change one part of a segment, say only that part: "switch the VIP segment to match any" keeps its rules and lists as they are. Changing the rules replaces all of them, so the assistant shows the old and new rules before saving. Segments on your own custom fields are made in Mailercloud under Audience > Segments for now.
The assistant can change one block of a saved drag-and-drop email (a template or a draft campaign, including ones you built yourself in the editor) without touching the rest.
"List the blocks in my Diwali draft." You get each row and block with its text, buttons and images.
"Change the second button's link to https://www.example-shop.com/new, and replace the hero image with https://cdn.example.com/hero.png. Preview first."
Approve the preview, then open the email in Mailercloud to check it.
Images must be at a public https address. The assistant can upload one from a public link into your Mailercloud images; for a file on your computer, upload it in the editor's Image block.
Where | Write it like |
Campaigns and templates |
|
Transactional and personalised API sends |
|
An empty field prints nothing, so avoid a merge tag on its own in a heading. The assistant checks this and other content rules (real links, alt text, postal address, unsubscribe link, size under 102 KB) before saving.
If you use Mailercloud's API Platform, the assistant can send one-off emails through it, for example an order update or a personalised note to a short list of recipients with their own values.
"Send a personalised email from [email protected] to these three customers, with subject 'Your order {{order_id}} has shipped' and their order numbers: …"
You see the recipients, sender and content before anything is sent. The sender must be on a verified domain. For regular marketing to a list, use a campaign instead.
Webhooks send Mailercloud events (such as opens, clicks, unsubscribes or new contacts) to your own system or to tools like Zapier and Make.
"Create a webhook that sends unsubscribes to https://hooks.example.com/mc, then send a test event."
"List my webhooks and pause the one that's failing."
Your AI app can use several connectors in one chat. Some useful pairs:
Google Sheets or Drive: "Read the sign-ups in my 'Webinar leads' sheet and add them to the Webinar list, tagged webinar-oct."
Slack: "Summarise this week's campaign results and post them to #marketing."
Your CRM or store: "Find customers who bought in the last 30 days and tag them as recent-buyers in Mailercloud."
Web research (Perplexity, ChatGPT or Claude search): "Look up this month's holidays in the UK and suggest a campaign calendar, then draft the first one."
Only add contacts who agreed to hear from you. When you move data between tools, check the preview before you approve.
Give the goal, the audience and the deadline: "for the Customers list, before Friday".
Ask for a table when comparing several campaigns or contacts.
Say "don't change anything yet" when you only want analysis.
Keep large jobs in batches: for thousands of contacts, use Import in Mailercloud.
If the assistant guesses wrong, correct it with the exact ID.
Automations can be viewed from chat but are built in Mailercloud.
Senders, reply addresses and webforms are added in Mailercloud; the assistant can list them.
Billing, plan changes and account settings stay in Mailercloud.
New contacts and changes can take a few minutes to show up in lookups and lists.
The connector acts with the access of the API key you connected. Use a separate key per app, and delete a key to stop its access.
If you ask for something the connector can't do, the assistant can pass the request on to our team so we know what to add next. Need help? [email protected]
