APIImprovedFixed
One-to-one customer e-mails in the API and MCP, a much faster Transactions list
E-mails to a single customer can be drafted and sent through the Workspace API and MCP, workspace settings and signup form options are writable there too, and the Transactions list opens several times faster on large accounts.
💸 Sales
- Improved Faster Transactions list. On accounts with thousands of orders the Transactions page opened slowly because the totals were computed order by order. The totals are now computed in a much lighter way and alongside the page itself, so the list opens several times faster with the same numbers.
- Fixed Polish payment methods run in the right workspace. A purchase paid with PayU, Tpay, Przelewy24, Paynow or PayPal is handled in the workspace that owns the product, so that workspace's automations and notifications run. The end of a timed access period is reported to the same workspace.
⚙️ Automations
- Fixed Runs start promptly during large sends. Under heavy load (for example a big campaign firing many events at once) an automation run could wait up to two minutes before it started. Runs now start right away.
🔌 API and MCP
- API One-to-one customer e-mails. List your outbox, and for a given customer list, draft, edit, delete and send e-mails through the Workspace API and the MCP tools. Sending confirms first in MCP, and a failed hand-off keeps the draft so you can send it again. Learn more
- Fixed A customer e-mail is never delivered twice. Two sends of the same draft at the same moment, or a retry after a hiccup, deliver one message. A draft you edit can still be sent again.
- API Automation graph on read. Ask for
?include=graphon a single automation to get its draft and published graphs plus whether it has unpublished changes, so a script can read, edit, save the draft and publish. Learn more - API Workspace settings. Read and update the workspace timezone, automatic transcription of uploads and the transcription language through the API and MCP.
- API Signup form options. Opt-in mode, tags, the redirect after signup, the per-form confirmation e-mail and the phone field with its SMS consent text can be set through the API and MCP. SMS consent is refused without the phone field, the same rule as in the dashboard. Learn more
- API "Next step" after purchase in MCP. The thank-you page's next step (the card shown after a purchase) can be set with the after-purchase MCP tool, with the same limits as in the dashboard.
🤖 Assistant
- Improved SMS consent through the assistant. Ask the assistant to change the SMS consent of a customer or a list of customers; it prepares the change and applies it after your approval.

