Skip to content

Mailing campaigns (Zoho Campaigns) ​

Zoho Campaigns sends mailings to lists: press releases, newsletters. It keeps the lists, handles unsubscribes and bounces, and reports opens and clicks. The mass-mail tool (ZeptoMail) is for one-off messages to a pasted list of people who expect them; ZeptoMail's terms do not allow bulk marketing mail, so anything sent to a list goes through Campaigns.

Agents work with Campaigns through two skills: zoho-list (create and fill a list) and zoho-campaign (write, upload and test a campaign).

Account ​

  • Organisation Ongehoord on the EU data centre (campaigns.zoho.eu).
  • Sender: Onderzoeksgroep Ongehoord <mail@ongehoord.nl>, replies to mail@ongehoord.nl. Zoho only sends from a verified address: Settings → Sender Addresses, then the confirmation link in that mailbox.
  • Lists: Test for trial sends (internal addresses only), Pers for the press. A list's description says who is on it and why they get mail.
  • Test addresses: Settings → Test emails. A test send reaches at most 5.
  • Topic: every campaign falls under the default topic Marketing.

Domain authentication ​

The DNS for ongehoord.nl is at Cloudflare. Campaigns mail passes SPF and DKIM through these records:

TypeNameValue
TXT (SPF)ongehoord.nlv=spf1 include:zohomail.eu include:zcsend.net -all
TXT (DKIM)as shown in Zohoas shown in Zoho

The DKIM record comes from Settings → Domain Authentication → ongehoord.nl → Set up. Publish it in Cloudflare, check it resolves (dig +short TXT <name> @1.1.1.1), then press Verify in Zoho.

A name carries one SPF record: a new sender adds an include: to the existing one. The other senders use their own subdomains and need nothing here: ZeptoMail (bounce-zem) and Resend (send). DMARC (_dmarc) is on p=none, monitoring only; move it to p=quarantine once the reports show Campaigns mail passing.

The setup is complete when listSenders shows mail@ongehoord.nl with is_verified: true and is_domain_authenticated: true.

Working with the MCP ​

The zoho and cloudflare MCP servers are in the global OpenCode config (~/.config/opencode/opencode.json); sign in to each with /mcps. Every Zoho call runs inside execute as tools.zoho.ZohoCampaigns_….

  • Response shape. The record is at r.data.data; paging is in r.data.meta.pagination. Pass next_cursor back as query_params.after.
  • ZlibError fetching … is an intermittent transport error that can arrive after Zoho has applied the call. Read the result back (list, get) before retrying; a blind retry of a create makes a duplicate or fails on the unique name.
  • No file access in execute. To upload a local HTML file, serve its folder with python3 -m http.server 8765 --bind 127.0.0.1 --directory <dir> as a background command, fetch it inside execute, and stop the server afterwards.
  • createCampaign drops preheader. Set it with updateCampaign straight after.
  • createCampaign accepts any sender_email, verified or not; the send fails later. Check listSenders first.
  • bulkAddContacts ignores an unknown list_ids entry without an error: the contacts are created outside any list. Take the list id from a read, and check the list afterwards.
  • Footer merge tags: $[LI:UNSUBSCRIBE]$ (every list mailing needs it), $[LI:VIEWINBROWSER]$, $[HF:ORGADDRESS]$ (the address in Zoho's organisation settings). listMergeTags lists the rest.
  • Review. Zoho reviews a new organisation's first campaigns (is_review_needed on the campaign), so the first launch can wait before it goes out.