September 2026

Every connected account now carries its own approval rules, and they apply to everything that uses it: your agents, your coordinator, and any MCP client. Open Settings → Credentials and click the shield on a connection to reach its Tool permissions page.

A locked action runs nothing until you say so. The call waits, the exact arguments it would send are shown to you, and you approve or decline it.

• The Use without approval row sets everything at once. Read-only lets reading actions run and locks the rest, All lets every action run, and None locks everything, including actions the service adds later. Search the list to lock one action on its own.
• Requests arrive under Needs you on the Dashboard, where you can read the arguments and decide without leaving the page.
• Approving admits one call with exactly those arguments, and it has 30 minutes to run. Different arguments, a second attempt, or a change to the rules each need a fresh approval. An untouched request expires after 24 hours.
• Agents and MCP clients can add restrictions but never remove one. Unlocking happens only on the permissions page, signed in as the connection's owner.
• Operations you allowlist on a tool provider node now carry a lock in the node settings, so you can see and change what needs approval without leaving the workflow.

The Twilio node gained two call operations, so a number you already own can carry a voice agent.

• On Incoming Call is a trigger. Pick the Phone Number that should ring, write a Greeting, and NoClick points that number's voice webhook at your workflow. The agent wired to the trigger answers and holds the conversation live.
• Place an Agent Call is a tool an agent calls itself. Give it a From Number, a To number, and a Goal in plain words. It returns straight away while the call runs.
• A finished call comes back as a message in the agent's chat, with the transcript and how long the call lasted. An outbound call reports back to the agent that placed it, in the conversation it was placed from, so a workflow no longer needs an On Incoming Call node to hear about a call it made.
• Both operations need an Account SID and Auth Token credential, because an API key cannot verify the webhooks Twilio signs. One number rings one agent, and a second workflow that tries to claim it is told which workflow holds it.

Every account now has a coordinator: one assistant that sees the whole account rather than a single workflow. It reads your workflows and runs, hands builds and fixes to the AI builder, passes work to agents you already have, and connects accounts for you.

• It watches failed runs. When a workflow fails, the coordinator looks into it: it asks the builder to diagnose and fix, pauses a workflow that is clearly finished with, or tells you when only you can fix it. A run that failed for want of credits never wakes it, because the credits alert already covers that.
• Memories is a new card on the Dashboard. It holds what the coordinator has learned about you and your work, as entries you can read, edit, write yourself, and delete. Each one is filed as About you, Preferences, Project context, or Reference.
• Preferences live there too, rather than in a settings page. Tell the coordinator to stop triaging a workflow, or which channel to reach you on, and it keeps that as a memory.
• It reaches you where you last wrote to it, on WhatsApp or by email. It has its own inbound address on noclick.app, so you can mail it and it answers on the same thread.
• It makes images and video on request. Video generation is available on the Plus and Pro plans.
• Your agents can message it as well, so an agent that hits something it cannot fix has somewhere to send it.

The sign-in page and the in-app sign-in panel now offer Continue with phone. Type your number, tap Text me a code, and enter the code to sign in. A number NoClick has not seen before makes an account, so the same form covers signing up. The number field has a searchable country picker, adds the calling code to digits typed without one, and formats the number as you type.

The number you message NoClick from on WhatsApp signs you in to the same account, so a chat you started on your phone and the workflows you open in the browser are one account rather than two.

• Phone is now a section in Settings for every account. Add a number, prove it with the code we text you, and WhatsApp messages and calls from it reach your account. Codes expire after ten minutes. Each row says whether the number was Verified with a code or Linked on WhatsApp.
• An account can link up to five numbers, and a number belongs to one account at a time. Unlink frees a number for another account to claim, and a number that is the only way into an account cannot be unlinked until the account has an email address.
• A chat that started on WhatsApp with no account behind it can be connected to an account you already have, from inside the chat. Ask to connect the email you sign in with, and NoClick emails that address a six digit code for you to send back. The code expires after fifteen minutes and is spent after five wrong tries, and nothing moves until it matches, so naming an address you do not hold reaches nothing. On a match, your workflows, connected accounts, and the chat itself move to the account with that email. Where no account has that address, the phone account takes the email so you can sign in with it too.

Instagram has a new On Mention trigger. It runs your workflow when your connected account is @mentioned in a comment or in the caption of a public post or Reel, including on someone else's post. Both kinds are included by default, and nothing is polled: Instagram pushes each event as it happens.

The event arrives with the text, the author, and links to the media, so you can wire it straight into an HTTP Request step and send it to your own backend. It tells you which kind of mention it was, and marks an author or a media link as unavailable when Meta does not supply one, rather than leaving you to guess. Each event carries an event_id you can use to skip duplicates. Private posts and Story mentions are not covered.

• On Mention uses the Facebook login connection, which is offered again when you connect Instagram. Mentions on other people's posts reach NoClick through the Facebook Page linked to your Instagram account, so that trigger needs the Page where On Comment and On Message still use the Login connection. An existing mention trigger on a Login connection keeps working for mentions on your own posts, and its Status field now tells you to reconnect it for mentions elsewhere.
• Connecting Instagram through Facebook finds Pages that belong to a business portfolio. NoClick now asks for the business permissions those Pages require, so an account with full portfolio access is no longer told that no Instagram business account was found. You are asked to approve the extra permissions the next time you connect.
• Connecting through Facebook reads your whole list of Pages. Accounts with enough Pages to span more than one page of results used to be told nothing was found when the Instagram account sat further down the list.
• A failed Instagram connection says which of three things went wrong: Facebook granted no Pages at all, it returned a Page with no Instagram account linked, or a Page could not be read. Each message names what to change and which Pages were involved, so you can fix the grant instead of retrying the same sign-in.

A voice note sent to an agent on WhatsApp, Telegram, or Discord used to arrive as a link the agent could not listen to, so the best it could do was ask the sender to type it out. Audio that arrives with a message is now transcribed, and the transcript becomes part of the turn the agent reads, so it answers what was actually said. A document that arrives the same way has its text pulled out at no cost, and photos and videos keep their link.

• This covers WhatsApp, Telegram, Discord, attachments on an inbound email, and files you upload in the agent chat. Telegram attachments are also saved to the workflow's resources as the message arrives, so a voice note plays in the run and chat views instead of showing an ID you cannot open.
• Files shared in a Slack message reach the agent too, up to three per message and 25 MB each. Slack keeps its file links private to the workspace, so NoClick saves a copy to the workflow's resources and gives the agent a link it can fetch.
• The transcript appears under the audio player in the agent's chat and in the run view, so you can check what the agent heard.
• Transcription is on by default and can be turned off per agent: Transcribe Voice Messages under Advanced in the node's settings, or Voice transcription under Capabilities in the agent chat's Settings. With it off, the agent is told that a voice message arrived and can ask the sender for text.
• Transcription costs credits like other AI usage. Audio is transcribed up to 20 MB and 10 minutes, at most three audio files per message. Anything larger, longer, or in a format the transcriber does not accept becomes a note telling the agent to ask the sender for text instead. A Test Run transcribes nothing, because the media it stages is made up.

The Setup tab now ends with a check on the workflow itself. It reports one of six states: setup unfinished, configured but unverified, registered and waiting for a real input, a reporting deadline armed, a real input received, or nothing automatic wired at all. When an input has arrived it names the node, when it arrived, and what the run did with it, and a Refresh button rechecks without reloading the page. It also says outright that a Test Run is simulated and that a send the provider accepted is not proof it was delivered.

• A trigger registers only once the path it starts can run. A trigger whose workflow is still missing an account, an agent's instructions, or a required field no longer shows as live while nothing could have run. Fix what is missing and the trigger registers itself the next time the workflow saves.
• A WhatsApp trigger that could not register says why, for example that the saved phone link is disconnected and needs reconnecting, and the message clears once a later attempt succeeds.
• A trigger run that carried no event stops there. A push trigger you run by hand reports that it is waiting for a message and no longer hands an agent an empty turn to spend credits on. Branches that do not depend on that trigger still run.

A scheduled workflow that kept failing the same way used to mint another failed run on every tick, for as long as the schedule ran. NoClick now pauses it: when the last five runs from that schedule have all failed with an identical error, spread over at least 30 minutes, the trigger node is switched off and the schedule stops.

• You get one email naming the workflow, the paused trigger, the error, and when it was paused. Paused schedules is its own toggle in Settings → Notifications, and you get at most one of these per trigger per day.
• The paused trigger appears on your Dashboard under Needs you and on the Triggers card, named and marked as paused with the error next to it. A trigger you switched off yourself stays hidden, as before.
• Fix what the error names, then enable the trigger node again to resume the schedule. If the same failure comes back, the schedule pauses again on the first repeat.
• Running out of credits never pauses a schedule. Topping up resumes the runs on its own.
• A short provider outage does not reach the bar: the failures have to be identical and sustained for half an hour.

The Instagram node has two new triggers, On Comment and On Message. A comment someone leaves on the connected account's posts, or a direct message they send it, starts a run as it arrives. Both need the Login connection, and Instagram pushes each event to NoClick signed, so nothing is polled.

Leave the filters blank to listen across the whole account, set Media ID on On Comment to watch one post, or Sender ID on On Message to hear one sender. Comments the account wrote itself and echoes of messages it sent are skipped, so a reply your workflow posts cannot start it again. Running either step by hand reports that no event was delivered, because events reach the workflow through the trigger.

The Feed tab in the top navigation becomes Dashboard: one page for what is happening across your workspace, with a card for each area and a full page behind every card. Needs you replaces the approvals queue and now also carries questions the AI builder parked, edits an agent proposed to its own workflow, accounts someone still has to connect, connections that stopped working, and triggers that failed to register. You answer each one where it sits, with the same fields and pickers the workflow itself would show you.

The other cards are Runs, Agents, Upcoming, Files, Credentials, Triggers, Credits, and Notifications. Press G then D to open the Dashboard, or G then I to land on Needs you.

• Runs charts the last 14 days and lists your workflows by run count, with failures called out. Click a row to open that workflow, or a single run to see its results.
• Files gathers workflow uploads, agent workspaces, and the builder's scratch folder in one place, previews images, video, audio, and datasets without leaving the page, and lets you upload or delete wherever you have write access.
• Agents shows sandboxes that are up now and each agent's latest turns, with the message that came in, the messages the agent sent, and every tool call it made.
• The section you drilled into is remembered while you visit other tabs. The back button, browser Back, or Esc leaves it.

The Discord node has two new triggers, On Channel Message and On Bot Mention, and a message reaches your workflow within seconds of being posted. Connect Discord with the Discord Bot Install credential so NoClick's bot is in your server, then leave Channel empty to listen to the whole server or pick one channel. Ignore bot messages is on by default, so posts from other bots and webhooks do not wake the agent. Each channel and thread is its own conversation.

• A Discord message in run results reads as a message: who wrote it, the channel and server by name, mentions as names, and attachments by filename. A slash command reads as its invocation.
• A Test Run on a Discord-triggered agent ships a written Channel question situation, so the rehearsal looks like a real Discord message instead of a generic sample.
• An On Slash Command trigger fires only for the server its connection was installed into. A connection made with your own bot token still covers every server that bot is in.
• A Discord connection reads as disconnected once the bot is removed from its server, in the credential picker, in workflow validation, and to an agent asking about its own workflow, with reconnecting named as the fix.