SMS campaigns, the e-mail library and automation authoring in the API and MCP, login codes from your own domain

✉️ E-mails

• Improved Login codes and receipts from your own domain. When your sending domain is verified, the login code and login link for your member area, the password-change code and the receipts your customers get are sent from that domain instead of Zanfia's address. If the domain stops working (for example after a DNS change), the message still goes out from Zanfia's address with your address as the reply-to, so no customer is left without a code.
• Fixed Sending-domain verification completes. Verifying a sending domain no longer fails at the last step. If you clicked Verify recently and the domain stayed on "pending" despite correct DNS records, click it again.

🔌 API and MCP

• API SMS campaigns. Create, schedule, send and delete SMS campaigns and read their stats through the Workspace API and the MCP tools. Learn more
• API E-mail library. The system e-mails you edit under Your site → Emails can be listed, read, updated, previewed and test-sent through the API and MCP. Learn more
• API Customer tags and consent in bulk. Create, rename and delete tags, assign or remove them on many customers at once, and change the e-mail or SMS consent of a list of customers in one call. Learn more
• API Automation authoring. Create an automation, replace its draft, publish it (with the list of graph problems when it cannot be published), duplicate it and delete it. The same operations are available as MCP tools, so an AI agent can build an automation for you end to end. Learn more
• Fixed Partial updates of community events. Updating a community calendar event through the API, MCP or the assistant with only some of its fields (for example just the title or just the link) now works; before, only a request carrying both dates went through. An invalid date range answers with a clear validation error.
• Fixed Clear answer on gated features. Creating or sending an e-mail campaign through the API in a workspace where campaigns are not yet enabled answers with a "feature not available" error instead of a server error.