Connect Mailcheer to your tools, with or without code
Your site sends its email through Mailcheer, your forms bring your contacts in, and Mailcheer tells your software what happened. Three connections you set up by copying a few fields, and an API for those who code.
Three directions, three connections
Software connects to Mailcheer in one of these three directions. Each has its own connection, and none waits on a vendor's approval: they speak languages your tools already know.
- 1SMTP relayYour tool sends its email through MailcheerFour fields to copy.See the connection ↓
- 2Inbound addressYour tool brings contacts inOne address to paste, fields picked with a click.See the connection ↓
- 3WebhooksMailcheer notifies your toolOne address to paste, events to tick.See the connection ↓
Ready to connect:HubSpotPipedriveMaken8nNode.js SDKPython SDK
SMTP relay
Your site sends through Mailcheer
WordPress, WooCommerce, PrestaShop, Odoo, Dolibarr, a CRM: any software that can send over SMTP. Under Settings → Integrations, one button creates your credentials — a key that can only send — and you copy four fields into your tool. As soon as the first message arrives, the screen shows “Connected”, with the time.
Every message then goes through the same checks as an API send: verified sending domain, suppression list, monthly quota. A rejection reaches your software with the API's own sentence and an SMTP code from the right family — 4xx when a retry will do, 5xx when something needs fixing. Images embedded in the message show in place.
SMTP ports and encryption · SMTP error codes
Step by step:WordPressWooCommercePrestaShopOdooDolibarr
- SMTP server
smtp.mailcheer.com- Port
587 (STARTTLS) or 465 (TLS)- Username
mailcheer- Password
mch_live_••••••••••••your key, shown only once
Connected — last email received over SMTP: today at 10:42
Inbound address
Your forms bring your contacts in
Typeform, Tally, Webflow, Stripe, Calendly, Shopify, or any tool that can call a webhook URL. You create an inbound address, paste it into the tool, send a test: Mailcheer shows what it received, and you pick with a click which field is the email address, the first name, the last name, the tags — and which automation welcomes the person.
Six formats are recognized on sight, and their mapping arrives pre-filled: all that's left is to check it. Double opt‑in is the default, and an unsubscribed address never comes back this way: it is the API's path, with the same safeguards.
- marie@example.comEmail address
- MarieFirst name
- Saturday workshopTags
- Double opt‑in
- Yes — confirmation email
- Automation to trigger
- Welcome
The safeguards
The SMTP relay, the inbound address, the API and the MCP server all run through the same code: verified domain, suppression list, monthly quota, double opt‑in. No connection gets around the rules.
Webhooks
Mailcheer notifies your software
You paste your service's address, tick the events it cares about, and Mailcheer calls it each time one of them happens. There are eleven.
Your emails
email.sentsent (API email)email.failednot sent, with the reasonemail.delivereddeliveredemail.openedopenedemail.clickedlink clickedemail.bouncedbouncedemail.complainedmarked as spam
Replies
email.receivedthe recipient replied
Your subscribers
subscriber.createdsubscriber addedsubscriber.unsubscribedsubscriber left
Your quota
quota.threshold_reachedquota at 50, 80, 95 or 100%
Every call is signed (HMAC-SHA256). If it fails, Mailcheer makes up to five attempts, spaced from thirty seconds to an hour apart; a failed delivery can then be replayed in one click. The “Send a test” button checks the connection before the first real event.
Replies come back too
When a recipient replies to an email sent through the API, the reply lands in your workspace's Replies screen, and in your software through email.received. All it takes is one DNS record on reply.<your domain>, which leaves your mailbox untouched.
Your CRM
Your HubSpot and Pipedrive contacts come into your list
Under Settings → Integrations, you authorize Mailcheer in HubSpot or in Pipedrive, then choose who comes in: all contacts, a HubSpot list or a Pipedrive filter, with their first name, last name and tags. From then on, changed records are read again as soon as the CRM reports them, and every fifteen minutes at the latest.
Nobody is assumed to have consented. Only contacts who said yes where your CRM records it — a HubSpot subscription type, Pipedrive's marketing status, a property of your own — go straight into your list; the others get a confirmation email or stay out, your choice. A contact who opted out of email in the CRM is unsubscribed here.
Mailcheer changes no record in your CRM, unless you ask it to report unsubscribes.
Only contacts who gave consent go straight into your list. Tell Mailcheer where your CRM records it.
HubSpot subscription type: Newsletter
Contacts without consent
Unsubscribes
Unsubscribe them from the subscription type chosen above
Import finished:812 subscribed301 awaiting confirmation127 left out
Automation
In Make and n8n
One API key is all it takes to connect Mailcheer: a trigger listens to all eleven events, and actions send an email, create or update a subscriber, add or remove tags, unsubscribe or erase a person, create and send a campaign — with the same checks as the API.
Make
The Mailcheer app installs from this link. Whatever its modules don't cover, “Make an API call” reaches with the same connection.
Install in Make ↗n8n
The
The node on npm ↗n8n-nodes-mailcheercommunity node, installed by name on a self-hosted n8n. An n8n AI agent can use it as a tool.
For those who code
The API and its SDKs, test mode, the MCP server
A REST API whose send fields match Resend's: migrating means changing the base URL and the key. Tags, batch subscriber imports, erasing a person on request (GDPR) — and for each key, its rights, a monthly cap and the language of its responses.
An official SDK per language: typed responses and errors, retries that never send twice, webhook signatures verified in one line.
Test mode: an mch_test_ key checks every send exactly like a real one, sends nothing and leaves your quota untouched. Simulated bounces and complaints reach your webhooks, flagged test.
The MCP server gives Claude Code, Codex and Cursor the same rights: nineteen tools, one command to connect.
curl https://mailcheer.com/api/v1/emails \
-H "Authorization: Bearer mch_test_…" \
-H "Content-Type: application/json" \
-d '{
"from": "hello@yourdomain.com",
"to": "bounced@simulator.mailcheer.com",
"subject": "Your invoice",
"html": "<p>…</p>"
}'202 AcceptedMailcheer-Mode: test
Two seconds later, your webhook receives:
{
"id": "evt_…",
"type": "email.bounced",
"created_at": "…",
"test": true,
"data": {
"email": "bounced@simulator.mailcheer.com",
"reason": "Permanent",
…
}
}And without connecting anything
- File importA CSV exported from any tool. Address, first name and last name are recognized on their own, and the import reports back: imported, duplicates, invalid.
- The hosted formA sign-up page under your name, for your email signature, your bio or behind a QR code. No website needed.
- Your site's subscription endpointAn address to use as the target of an HTML
<form>: it accepts a regular form submit as well as JSON, applies the form's tags and sends the confirmation email.
Frequently asked questions
Do I need to know how to code?
Not for the three connections, nor for your CRM. The SMTP relay takes four copied fields, the inbound address takes one pasted address and a few clicks to pick the fields, webhooks take one pasted address and a few ticked events; HubSpot and Pipedrive connect from their own authorization screen. The API, the SDKs and the MCP server are for those who code.
Which port should I use for the SMTP relay?
587 with STARTTLS, or 465 with TLS from the first byte: both work. The relay refuses any send without credentials, and only accepts credentials once the connection is encrypted.
Do my site's emails count toward my quota?
Yes. An email sent through the SMTP relay is a send like any other: it counts toward your plan's monthly quota and goes through the same checks as an API send.
If an unsubscribed person fills in a form again, do they come back to my list?
No. The inbound address takes the same path as the API, which never brings back an address that unsubscribed or marked a message as spam.
Get started
Create an account, verify your sending domain, then connect whatever you need. 3,000 emails a month free, no credit card.