October 27, 2026

#What's new

• New event editor on the event page itself. Before, creating an event meant filling a long form in a window. Now New Event creates a draft and opens the event page, the same one members see, and each part is edited in place: cover and card image (with Adjust framing), name, date, location, description, organizers and speakers, tickets, registration questions, certificate, recording, Who can see it and check-in. The draft saves itself and belongs to the team only: members don't see it, it doesn't enter the Feed and it notifies no one. The To publish list shows what is missing, Preview shows the page as members will see it, and Publish asks whether to send the e-mail notice and puts every ticket on sale. On a published event, Edit event turns on the same mode, with Save changes. Drafts live in the list's Drafts tab. See Events.
• Badges in Engagement. In Administration › Engagement, the Badges tab (owner and admin) creates seals with an image, name, description and Public or Private. A badge arrives by hand (Give to…, up to 100 people, or on the profile), on course completion (Badge on completion, on the course's Completion tab), on event check-in (Badge on check-in) or by workflow, and the same person never gets the same badge twice. The recipient is notified in the bell and by e-mail, in the new Achievements category, on by default. See Badges.
• The profile shows engagement. Each member's profile shows the points, the level and the Achievements tab, with badges and certificates. Private badges only show for their holder and for the owner and admins; certificates, for the person and the team, until they choose The whole community. See The profile shows engagement.
• Adjust points on the profile and in the ranking. Before, giving someone points took a workflow. Now the owner and the admin click Adjust points, on the profile or in the ranking row's menu, with the points and the reason, which the person sees in their history. See Gamification.
• Multiple-choice field. A new custom field, Multiple choice, with 2 to 50 options and, optionally, a minimum and maximum: on sign-up, on the profile and on the record. A Choice can become multiple choice even with answers. The member list gets a filter per field ("Interests contains any of: Linux, Cloud"), the import accepts Linux; Cloud in one cell and offers to add missing options, the workflows' Profile field condition gets contains any of, contains all of and does not contain, and the campaign variable comes out "Linux, Cloud". See Custom fields.
• Plan quotas. Each plan has its own quotas: AI (60 to 500 transcription minutes and 1,000 to 6,000 uses a month), SMS (from Growth up), WhatsApp (300 on Business, 500 on Scale), converted video minutes, campaign recipients (1,500 to 30,000 a month), workflow e-mails (40 to 350 a day) and storage (5 to 250 GB). On a monthly plan they renew on the 1st; on an annual plan, what's left adds up until renewal. At the limit, the video plays the original file, the AI buttons say so, the campaign tells how many fit and storage refuses only new uploads. Transactional e-mails are never limited. See Plan and extensions.
• WhatsApp with platform messages. Every WhatsApp message goes out in an approved template, with a button that opens the right page of the community, and Memberfy sends on its own the payment confirmed or declined, the ticket, the event reminders (24 hours before, starting and live, with the map for in-person events), the proposal decision, the 1:1, the feedback and the HR to-dos. The community turns off what it doesn't want, and each person picks theirs in My Account › Notices. WhatsApp is on the Business and Scale plans. See Platform messages.
• SMS and WhatsApp notices. The community turns SMS and WhatsApp on in Administration › Settings › E-mails and notifications, with a required daily cap, the month's usage against the plan's quota and a test to your own phone. Service notices go out (the event reminder, the PDI and 1:1 reminders, and the new Send SMS and Send WhatsApp workflow blocks) to phones in every country (for now, SMS to the United States is left out), never between 9 p.m. and 8 a.m. in the recipient's time zone, with at most 5 workflow messages per person per day in each channel (adjustable from 1 to 20), and only to people who consented at sign-up, login or import (only people the import creates) and verified their phone with a code. Each person picks channel and category in My Account › Notices; the SMS link removes them from this community only, and replying STOP stops the whole channel. See SMS and WhatsApp notices.
• AI blocks in Workflows: Claude and ChatGPT. A workflow step asks the AI for a text or a JSON: a personal welcome, a ticket triage, a form summary. The call uses the community's own API key, kept in Variables and keys, and the AI limits card holds the spending per call, per run and per day. The history shows the model, the tokens and the duration, never the key, the prompt or the answer. See AI blocks.
• New actions in Workflows. Publish a post, Issue a certificate, Recognize, Block in the chat, Schedule a 1:1 and Add a PDI action, which shows in the plan as "Created by the workflow …". And the admin now uses the same actions as the owner in workflows. Through the assistant, the AI limits and adjusting someone's points too. See Platform actions.

#Improvements

• Report a problem in the app. In the sidebar, below My account, a form to tell the Memberfy team what went wrong, with what you were doing and, if you like, a screenshot. The report arrives with the page and the app version, and you get a reference number. See Account and profile.
• Simulate and email me. A workflow simulation sends you the e-mails the person would get, with [Test] in the subject, without counting as a send. See Simulate, test and estimate.
• A deleted group's name can be used again. See Groups and org chart.
• The site covers the custom domain and the new Workflows. Before, the Memberfy site didn't say how to connect your brand's domain. Now it explains that it sits next to the memberfy.net address, on any plan, and the pricing page lists webhook calls, Variables and keys, platform actions, calling another workflow and the run history, with fixed IPs from Business up. See Custom domain and Workflows.
• Help in the site menu and Workflows on the platform page. The site menu gained a Help item, before Pricing, that opens this Help Center in your language, on phones and in the footer too. And the platform page gained a Workflows section: triggers, waits and conditions, Call webhook, platform actions, the run history and the assistant building the automation.
• Workflows in the site's Platform menu. The Platform menu on the site gained a Workflows item that goes straight to the section, on desktop and on phones.
• Campaigns on the platform page and in the site menu. The platform page gained a Campaigns section, and the Platform menu an item that goes straight to it: the e-mail library and sends, the block editor and test send, audience and scheduling, opens and clicks, automatic and default e-mails, opt-out by category, the sending reputation guard and the assistant building the campaign. See E-mail campaigns.
• The Help Center shows how to give points by hand and segment by field. The articles said this was not possible yet. Now they explain the Workflows way: the Adjust points step in a Manual workflow, with Run now for people or an audience, and the Profile field condition with Send e-mail or a tag to segment the campaign. See Gamification and Custom fields.
• A clearer New key in Variables and keys. The dialog says what a key is for and that nobody sees the value again; the Name adjusts as you type and shows how to write it in the block ({{env.CRM_TOKEN}}), the Value has a show and hide button, and Can only be sent to is optional: empty, the key can be used with any address. See Variables and keys.
• The Messages bar is back. When collapsed, the chat is again the Messages bar in the corner of the screen.
• Settings reorganized: one menu by topic, search and a page for each topic. Each page saves on its own, and old links keep working. See Community settings.
• Custom domain: a prominent warning to turn off the DNS proxy. When you add the domain and next to the record, the screen explains how to leave the cloud gray on Cloudflare or turn off proxy, CDN or acceleration with other providers. See Custom domain.
• Storage follows the plan. Before, going over the limit only warned. Now, at the plan's limit, new uploads of videos and files are refused with a notice, and nothing already stored goes offline. See Plan and extensions.
• New security controls.

#Fixes

• The event's Private option now really hides the event. Before, choosing Private saved the event as subscribers-only, and it kept showing up for anyone with a plan. Now Private keeps the event to the team only, and the subscribers option shows its right name, Subscribers. See Who sees the event.
• The Field condition with an operator now works correctly. Before, in workflows, the Profile field rule with an operator (and the Variable rule on a profile field) compared an empty value and didn't take the right path. Now it reads the field's current value. See Workflows.
• An option removed from a choice. Before, whoever had picked a removed option kept showing the old value. Now the option leaves the profile, the filters and the variables, and comes back if the option does. See Custom fields.
• Custom domain: with the DNS fixed, Check now tries to issue the certificate again on its own. Before, a certificate that failed with the proxy on stayed stuck even after the proxy was turned off. See Custom domain.

#For developers

#API

• Event drafts (contract change): POST /api/events now creates a draft and only requires spaceId; publish: true keeps the previous behavior. New routes PATCH /api/events/{id} (only the fields sent, with updatedAt or If-Unmodified-Since; 409 if another save came first) and POST /api/events/{id}/publish (notifyByEmail; 422 with what is missing). GET /api/events takes status (DRAFT, all) for the team; the event carries status, publishedAt, updatedAt, readiness and the images' focal points. visibility takes private. The event.created webhook now fires on publishing. See Creation order.
• New SMS and WhatsApp routes: GET and PUT /api/sms/settings and /api/whatsapp/settings (turning on needs dailyCap), POST /api/sms/test and /api/whatsapp/test, GET /api/whatsapp/templates, POST /api/sms/segments, POST /api/members/me/phone-verification and .../confirm, GET and PUT /api/members/me/notice-preferences, GET /api/members/me/contact-consents, GET /api/members/{memberId}/contact-consents and GET /api/contact-consent/texts. Sign-up and login accept smsConsent; the import, the smsConsent target with smsConsentAttestation. Workflows get the sendSms and sendWhatsapp blocks. See Order of creation.
• Badges: GET and POST /api/badges, POST /api/badges/image, GET, PATCH and DELETE /api/badges/{id}, GET /api/badges/{id}/holders, POST /api/badges/{id}/grants (up to 100), GET and POST /api/members/{memberId}/badges and DELETE /api/members/{memberId}/badges/{badgeId}; completionBadgeId on the course and checkInBadgeId on the event; engagement in GET /api/members/{id} and certificatesVisibility in PUT /api/members/me. Webhook events badge.awarded and badge.revoked; in workflows, the badge.award and badge.revoke actions and the badge.awarded and badge.revoked triggers. Contract change: badges in the ranking (GET /api/gamification/leaderboard and GET /api/gamification) is now [{ id, name, imageUrl }].
• Multiple choice: the MULTI_SELECT type in /api/member-fields, with minSelections and maxSelections; the value is the list of the options' value; GET /api/members?fieldFilter[<key>]=a,b; in the import, unknownOptions in the summary. A choice whose option was removed now reads null.
• Quotas: GET /api/entitlements/community gains video.transcodeMinutes and campaigns.recipients, and each meter gains period, available and resetsAt; GET /api/campaigns/quota gains recipients. A campaign over the recipients: 429 quota_recipients; an upload over storage: 409 storageLimitReached.
• SMS and WhatsApp: personDailyCap in /api/sms/settings; moments, upgradeRequired and blockedCountries in the settings; whatsapp.moments and whatsapp.marketing in /api/members/me/notice-preferences; the sendWhatsapp block is now { template, variables, link }; the import takes whatsappConsent. Turning WhatsApp on outside Business and Scale: 403 whatsapp.notOnPlan.

#MCP: technical details

• Event drafts: the new publish_event tool (team) publishes a draft and asks to confirm when it sends the e-mail notice, with how many people get it; with notify_by_email: false, it publishes at once. create_event creates the draft and publishes it at the end (as_draft: true stops at the draft; if something is missing, the draft stays and publish_missing says what); start becomes optional. update_event saves only the fields sent, with updated_at, and explains when another save came first. list_events takes status (DRAFT, all) for the team. visibility takes private. 877 tools. See Tools · Events.
• 14 new tools, 868 in total: get_sms_settings, update_sms_settings, send_sms_test (asks to confirm), count_sms_segments, get_whatsapp_settings, update_whatsapp_settings, list_whatsapp_templates, send_whatsapp_test (asks to confirm), get_my_notice_preferences, update_my_notice_preferences, list_my_contact_consents, request_phone_verification, confirm_phone_verification and list_member_contact_consents. The workflow guide describes sendSms and sendWhatsapp and gets 8 recipes (56). See Tools.
• 8 new tools, 876 in total: list_badges, get_badge, create_badge, update_badge, delete_badge (asks to confirm), award_badge (up to 100 people, with dry_run), revoke_badge (asks to confirm) and list_member_badges. create_course/update_course take completion_badge, create_event/update_event, check_in_badge; get_member carries engagement, and update_me, certificates_visibility. The ready-made recipe Give a badge (award_badges, 21 in total). See Tools · Content and engagement.
• create_member_field and update_member_field take multi_select, min_selections and max_selections; update_member_field_values takes the list of options; list_members filters with field_filter; the import shows unknown_options.
• update_sms_settings takes person_daily_cap; get_whatsapp_settings and update_whatsapp_settings handle moments; update_my_notice_preferences takes whatsapp.moments and whatsapp.marketing. The workflow guide builds sendWhatsapp with template, fields and the button's page, and the workflow recipes go up to 61.