September 2026
Everything that changed in NoClick in September 2026.
Live calls on your own Twilio number
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.
Improvements and fixes3
Signing in with a phone number from the site navigation now lands you on the Dashboard instead of reloading the page you started from. The code step counts down with Resend code in 0:30 and then offers Resend code, and a send the provider refuses as too soon says how long to wait instead of showing a generic error.
Accounts with no email address, which is what a first WhatsApp message creates, now work end to end. Connection links sent to them open, organization invites and shares behave correctly, checkout and top-ups work, and names show in the navigation bar, the organization switcher, and the chat sidebar rather than appearing blank. Tools that need an email address, such as agent email updates, are no longer offered on an account that has none, and the Send Email node explains how to connect an address instead of failing with an internal error.
The WhatsApp message that tells you the builder is waiting now names what it needs, for example "2 account connections and one answer", instead of repeating the question as a label.
Sign in with your phone number
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.
Improvements and fixes1
An agent listening on a WhatsApp QR connection is now told who wrote each message, not just the chat ID. The turn carries the sender's WhatsApp display name and, where it differs from the chat ID, their phone number, so a standing instruction about a particular person matches. The reply address is unchanged.
Agents read the voice notes and files that arrive with a message
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.