# October 26, 2026 > Workflows get a new editor and become more complete, with triggers by block, Run now, Scheduled and Webhook received, variables between blocks, ending in success or error and sending postponed by quota. The community can get its own brand's domain, set up from the screen. Tickets for every event are in My Account, a channel can be muted, and several screens got simpler. Plus the Call webhook block with Variables and keys, platform actions, and a history that shows each step from the inside. - [Workflows: new editor and results](#workflows-new-editor-and-results) - [Run now, Scheduled and Webhook received](#run-now-scheduled-and-webhook-received) - [Call webhook and Variables and keys](#call-webhook-and-variables-and-keys) - [Run history from the inside](#run-history-from-the-inside) - [The assistant learns to automate](#the-assistant-learns-to-automate) - [Platform actions and Call workflow](#platform-actions-and-call-workflow) - [Custom domain](#custom-domain) - [My tickets](#my-tickets) - [Simpler screens](#simpler-screens) ## Workflows: new editor and results **What it is.** The [Workflows](/notificacoes/workflows) editor now takes up the whole screen, with the blocks by category in an accordion with search, each block's panel one click away, a context menu, keyboard shortcuts and a minimap. Each workflow has **one trigger**, chosen in the family's block (**Members**, **Purchases**, **Courses**…), and every path ends in **End: success** or **End: error**. Actions have an error exit, the list shows **Entered**, **Finished**, **Errors** and **Success**, and the owner and the admins get a notice when a workflow goes over 20% errors. **Why it matters.** Now you can tell whether each run went well and what to do when it did not. And messages get personal: the course name in the congratulations, the product and the amount in the thank-you for the purchase, with **Insert variable** in every text, including the e-mail. **Where it is.** **Administration › Workflows**. **How to start.** Open a workflow, click an e-mail block and use **Insert variable** to put `{{course.name}}` in the subject; connect the "ok" exit to **End: success**. **Also in this release:** - **Variables between blocks** and the **Variable** condition, with operators by type (text, number, date, list, yes/no). - The **Write to log** block, which shows up in **Logs › Workflows**. - **29 triggers** with each module's lifecycle (downloads, posts, events, courses, spaces and forms), **Someone comes back after N days away**, **First purchase only** and the **DM received**. - **Sending postponed by quota:** the frequency limit, the daily limit, the sending reputation and the suspension postpone the step instead of skipping it. - **On whose behalf:** the community chooses whether workflows send DMs, comment and react on behalf of **The whole team** or **Owner only**; no one needs to agree to it or approve texts anymore. - **Active workflows by plan:** 3 on Starter, 10 on Growth, 30 on Business and no limit on Scale. - The trigger for newcomers is now called **New community member**, and the condition takes several tags, space access and visit, and event registration and attendance. ## Run now, Scheduled and Webhook received **What it is.** Three new triggers: **Manual** (**Run now**, for chosen people or an audience, with the count and the confirmation first), **Scheduled** (every day, week or month, for an audience) and **Webhook received**, where another system (a CRM, a form, n8n) calls an address and starts the workflow for the person. On the *Someone has not signed in for N days* trigger, **Include who has already gone more than N days without visiting** also brings in people who were already inactive. See [Incoming webhook](/integracoes/webhook-de-entrada). ## Call webhook and Variables and keys **What it is.** The **Call webhook** block sends an HTTPS call to another system in the middle of a workflow (a CRM, a spreadsheet, n8n), with a maximum response time of 2 to 15 seconds and new attempts at 1, 5 and 15 minutes when the destination fails. Tokens live in **Variables and keys**, the community's vault: the value is stored encrypted, never comes back to the screen and only goes to the hosts you allow. **Why it matters.** What happens in the community reaches your other systems right away, with no spreadsheet in between, and the answer can decide the next step. **Where it is.** **Administration › Workflows › Variables and keys**, and the block under **Integrations**. **How to start.** In **Variables and keys**, accept the personal-data notice and create the `CRM_TOKEN` key with the CRM's host; in the workflow, add **Call webhook** and use `{{env.CRM_TOKEN}}` in a header. **Example.** A completed purchase calls the CRM with the name, e-mail and product; if the CRM answers with an error, the error exit sends a DM to the team. On the **Business** and **Scale** plans, calls go out from [fixed IPs](/api/ips-fixos#workflows-the-call-webhook-block), up to 10,000 a month, and the history shows where each one went out from. See [Call webhook](/notificacoes/workflows#call-webhook). ## Run history from the inside **What it is.** Each workflow's **History** now has the list of runs next to the detail, with filters by period, result and person. Each step shows what went in and what came out when it ran: the text sent, the e-mail's delivery, what the person had in a condition (*"Has: VIP"*), the status and duration of a webhook call. See [History](/notificacoes/workflows#history). ## The assistant learns to automate **What it is.** The assistant (Claude, ChatGPT) now knows Workflows from the inside: say the rule in your own words (*"whoever buys the course gets 7 days of access to the mentoring"*) and it builds the workflow, simulates it and turns it on after your ok. It also suggests the workflow that automates what you just did (a campaign, certificates, invitations). ## Platform actions and Call workflow **What it is.** Workflows now do what the team does on screen: each **platform action** is a block (**Change role**, **Adjust points**, **Register for event**, **Enroll in course**, **Give courtesy access**, **Send an in-app notice** and others), and the **Call workflow** block runs another workflow and uses what it returns. So a shared welcome lives in one workflow, called by many. **Where it is.** In the editor, under **People**, **Content**, **Messages** and **Flow**. **How to start.** In a purchase workflow, add **Give courtesy access**, pick the plan and **For how many days**, and connect the "ok" exit to **End: success**. A workflow never does more than whoever turns it on: an admin can see and simulate, but not change, a workflow with actions only the owner may do. See [Platform actions and other workflows](/notificacoes/workflows#platform-actions-and-other-workflows). ## Custom domain **What it is.** The community now opens at your brand's address (`community.papodesysadmin.org`) **and** at the Memberfy one (`papodesysadmin.memberfy.net`), at the same time, without redirecting. When the custom domain becomes **Active**, it becomes the **Primary** address: links, e-mails and search engines start using it. The security certificate is issued and renewed on its own, and the custom domain is included in every plan. **Why it matters.** Before, a custom domain meant asking the Memberfy team, and the **Domain** field in the settings only stored a text. Now the owner or an admin does it all from the screen and follows each step, and anyone who saved the old link keeps coming in. **Where it is.** **Settings › General**, in the **Custom domain** block (owner and admin). The **Domain** text field is gone. **How to start.** 1. In **Your domain**, type the address and click **Add domain**. 2. At your DNS provider, create the record the screen shows (**Type**, **Name** and **Target**, with **Copy**), DNS only, no proxy. 3. Follow **Waiting for DNS → Verifying → Certificate issued → Active**, or use **Check now**. You get an e-mail when it becomes active. **Example.** Papo de Sysadmin adds `community.papodesysadmin.org`, creates the `CNAME community` in Registro.br and, in about an hour, invitations already go out with the new address. To change later, **Change domain** keeps the old one up until the new one becomes active. Each error (wrong record, `A` record, proxy on, root domain, CAA, the 7-day deadline) shows up on the screen with what to do. See [Custom domain](/configuracoes/dominio-proprio). ## My tickets **What it is.** The **My tickets** tab, in **My Account**, brings together the tickets for every event: the upcoming ones, with the entry QR and code, and the past and canceled ones. See [Account and profile](/conceitos/conta-e-perfil). ## Simpler screens - **Events:** the management bar shows the sale's state (*"Sales open · 79 of 80 seats"*), ticket types are choice cards with a single button, and the checkout shows the amount on the button (**Pay R$ 40.00**). - **Channel:** **Mute channel**, who is in the conversation and search in the channel; deleting your own message has **Undo**. - **Undo instead of confirming** when removing a key result, a 1:1 agreement or your own channel message. - **Surveys:** the editor's bar has only the title, the state and the main action, and an identified survey whose introduction promises anonymity shows a warning with **Fix the text**. - **Upvote:** sorting and filtering in compact menus, and the topic's bar with **Edit** and **Change state**. - **Performance review:** the module has this name, and **Open the cycle** sits in the management bar, with the confirmation in a window. - **1:1:** logging only goes up to today; a future 1:1 is scheduled. - **Spaces:** a space's type does not change after it is created. - **Sending reputation:** the banner shows the community's own numbers against the limit. ## Improvements - **More webhook events:** there are 93, with each module's lifecycle, `member.returned` and `message.received`. See [Webhooks](/api/webhooks#the-events). - **A space you cannot access says why** and what the next step is. - **Access request on the website:** after you send the form, the page scrolls straight to the confirmation. - **A workflow never does more than whoever turns it on:** steps act with the role of whoever saved, turned on or ran the workflow, and a workflow with actions only the owner may do opens read-only for an admin. See [Which role the steps act with](/notificacoes/workflows#which-role-the-steps-act-with). - **Delete run and Clear history:** one finished run, or all of them up to a date, leave the history and the numbers; they still count for whoever enters **Only once**. See [History](/notificacoes/workflows#history). - **The menu updates right away:** a space or section created, edited or removed shows up in everyone's menu without reloading, and anyone inside a space that was removed or that they lost access to goes right away to the no-access screen. See [Visibility and access](/conceitos/visibilidade-e-acesso#what-people-without-access-see). - **Workflow editor:** a click on a block no longer marks the drawing as changed. - **New security controls.** - **A leaner Monetization:** the **General** tab of **Monetization** no longer has the *This month, by currency* block; the balance cards already show everything in the community's currency. See [Balance and statement](/pagamentos/saldo-e-extrato). - **Dates in your language's format:** dates and times show and are typed in the format of the language chosen in the app, no longer the browser's (in English, mm/dd/yyyy and 12 h). The calendar is still on the icon. - **Clearer Business Information:** submitting with something missing marks each field and scrolls the page to the first one; the partners block explains that you need to click **Add Partner**; and, after you submit, the **Next: payout details** button takes you to the payout account. See [Business Information](/pagamentos/informacao-comercial). - **Payout details without waiting:** you can send your payout details together with the Business Information, without waiting for the approval; both are reviewed together. See [Business Information](/pagamentos/informacao-comercial#step-by-step-payout-account). ## Fixes - The 1:1 history shows who canceled a meeting and the pair's last meeting. - The **Billing** page for community members now loads even when the community has not set up payouts yet (before, it kept loading forever); the card section still says that card payment is not available yet. - In Firefox, date fields (for example, the founding date in the billing information) accept a typed date again, and the calendar is still available from the icon. - The payout registration is no longer rejected when the revenue is typed with cents (*3000.00*) or when the address has no complement. ## For developers ### API - **Workflows:** `POST /api/workflows/{id}/run`, `/stop`, `GET /api/workflows/{id}/summary`, `/variables` and `POST /api/workflows/variables`, `GET` and `PUT /api/workflows/settings`; one trigger per design, `endSuccess` and `endError`, and design errors with the block (`singleTriggerOnly`, `pathWithoutEnd`, `variableUnavailable`). See [Workflows](/notificacoes/workflows#in-the-api). - **Incoming webhook:** `POST /api/workflow-hooks`, with the token in `X-Memberfy-Hook-Token` and the HMAC signature. See [Incoming webhook](/integracoes/webhook-de-entrada). - `GET /api/my/tickets` and channel muting. - **Workflows, part 2:** the `http`, `platformAction` and `runWorkflow` blocks, the `workflow.called` trigger, `platformActions` and `subWorkflow` in `GET /api/workflows/triggers`, the vault under `/api/vault`, `DELETE /api/workflows/runs/{runId}` and `POST /api/workflows/{id}/runs/clear`, and the errors `actionAboveRole`, `subWorkflowAboveRole` (422) and `workflows.actionsAboveRole` (403). The run detail brings the drawing's version and what each step received and returned. - **Team routes:** `POST /api/events/{id}/registrations`, `POST /api/courses/{id}/enrollments` (free items) and `POST /api/notifications/send` (up to 100 people). See [Creation order](/api/ordem-de-criacao). - **Custom domain:** `GET`, `PUT` and `DELETE /api/communities/custom-domain` and `POST /api/communities/custom-domain/check`. `PUT /api/communities/{id}` with another `domain` returns `400` (`param: "domain"`); `domain` is now the primary address, written only by Memberfy. See [Creation order](/api/ordem-de-criacao#custom-domain). - **Realtime:** the `menu.changed` topic in the `community` room. See [Realtime](/api/tempo-real#change-notices-invalidate). ### MCP: technical details - **Workflows:** `run_workflow`, `stop_workflow`, `get_workflow_summary`, `list_workflow_variables`, `preview_workflow_text`, `get_workflow_settings`, `update_workflow_settings` and the 5 incoming webhook tools. See [Tools · Community](/mcp/ferramentas-comunidade#workflows). - `mute_channel`, `unmute_channel` and `list_my_tickets`. - **Automation guide:** the `memberfy://guides/workflows` resource, `get_workflow_guide`, `suggest_workflow` (team, no confirmation), 39 recipes, the `workflow_playbook` menu recipe and `next_steps` that suggest the right recipe. - `delete_workflow_run` and `clear_workflow_runs` (owner and admin, with confirmation); `list_env`, `set_env` and `delete_env` (the value never comes back); `register_member_for_event`, `enroll_member_in_course` and `send_member_notice` (owner, admin and moderator, no confirmation). - **Custom domain:** `get_custom_domain`, `set_custom_domain`, `check_custom_domain` and `remove_custom_domain` (owner and admin; only removing asks to confirm), and the same four for the SuperAdmin on another community (`*_community_custom_domain`). The `next_steps` show the DNS record to create. See [Tools · Community](/mcp/ferramentas-comunidade#custom-domain). - The server now has **851 tools** and 20 recipes in the menu.