Changelog
What changed in NoClick: the SDK, the API and the app, newest first.
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.
Workflows holding an HTTP Request, RSS, or MCP Server node that runs without a credential no longer refuse to activate with "connect an account". Those nodes support an optional credential, and readiness now treats them as ready without one. Nodes that genuinely require an account, such as an Instagram OAuth connection, are still enforced.
Improvements and fixes1
A node the AI builder removed could come back on the canvas and in the saved workflow, and then ride into the next prompt. Builder removals are now remembered the same way your own deletions are, so a save that arrives out of order cannot restore them.
Improvements and fixes1
Scanning a WhatsApp QR code no longer warns that the connection you just made is missing. The node's Credentials tab judged the new connection against the credential list it had loaded before the scan, so for the moment it took the refreshed list to arrive it reported the attached credential as one that no longer exists or is not accessible. Nothing was wrong with the connection, and the warning cleared on its own.
Improvements and fixes1
A link for answering the builder's questions stays valid on every step. When one link asked for two connections of the same service, the second question's connection request replaced the first one's, so going back to Step 1 of 2 reported Credential request not found. Questions for the same service now share one request, so a single sign-in answers all of them, and links sent before this repair themselves the next time they are opened.
Improvements and fixes2
API keys work again under Settings → Developer. Creating, listing, and revoking a key failed with an authorization error, because the app and the API sit on different domains and the request was not carrying your sign-in. The page also shows the error when a request fails, rather than appearing to do nothing.
Requests to NoClick's API are faster, and a request that takes longer than five seconds no longer fails with a proxy error. That includes the fallback connection your browser uses when it cannot open a websocket, which was being cut off after about ten seconds.
An agent fed by a trigger does not need a Message
Message is where you write an agent's standing instructions, and it is still required when nothing feeds the agent. When a trigger is wired into the agent, the event that arrives is the turn, so Message can be left empty and the node is no longer marked incomplete for it. Running such an agent by hand, with no event and no standing instructions, fails with an error saying so rather than running on nothing.
Improvements and fixes3
The AI builder can see which accounts are already connected when you ask it to edit or autofill. The snapshot it works from used to leave out each node's attached account, along with whether the node was disabled or holding a test output, so it could ask you to connect something you had already connected.
A WhatsApp disconnection email waits for the link to stay down. A restart at the provider flaps every connection for well under a minute, and you used to be told to re-scan a link that was about to come back, which adds a second device link to the phone. NoClick now waits out a short blip before it checks, and if the connection recovers after an email went out, a follow-up tells you it healed itself and not to re-scan.
A turn lost because its sandbox was replaced is now recorded as a failed run with the reason, instead of sitting in history looking delivered.
A missing value stops the step
A required field holding a reference like {{ $('trigger').chat_id }} used to be passed on as an empty value when the referenced output had no such key. The step reported success and nothing arrived. That field now fails the step, and the error names the field, the reference, and the keys the referenced node's output actually has, so you can fix it without opening the run.
- The error reads
Required field 'to' is empty, followed by what went wrong: the referenced node has no key by that name, and the list of keys it does have. A key that exists but holds null is reported as null, which reads differently and usually means a different fix. - A reference read during a manual run of a trigger that waits for events says there is no live event in this run, and that firing the workflow for real is how to test that path.
- Optional fields are unchanged. A reference that resolves to nothing there leaves the field at its default, as before.
- Sending a WhatsApp message to an empty recipient stops with a message naming the chat id to reference instead, rather than being accepted and never delivered.
Improvements and fixes1
The builder can add an Alarm or Filesystem node when you ask for one. Neither was in the list of nodes it could see, so asking it to let an agent schedule its own wake-ups used to get the answer that no such node exists.
Improvements and fixes4
Pressing Run on an integration node that is wired as a tool provider no longer fails with an error about a missing action. The button is off, and says the node provides tools and its actions run when the agent or your MCP client calls them. Run the agent instead. Asking NoClick to run that node from an MCP client gets the same explanation back.
A step inside a loop that fails is recorded as failed. Some failures were read as successes, so the loop carried on with the failed step's output and stored it as that item's result.
A loop stops when your credits run out, including loops nested inside another loop, instead of working through the rest of the items and failing each one.
The nodes on a loop's After Loop handle run once. A loop nested inside another loop could run them a second time.
Improvements and fixes1
When a connection really has dropped, the message on the node's Credentials tab now says how to repair that connection: re-scan the QR code for a WhatsApp credential, or add NoClick's bot back to the server for a Discord one. It used to give WhatsApp instructions whatever the connection was.
Improvements and fixes4
The What came in section of a run's results shows the message the agent turn actually took in. A turn from a chat agent could show something else there: a note left behind by an earlier manual run, or a message from a different conversation. When several messages feed one turn, the section marks the one it shows as the latest of them, and Inputs consumed carries the rest.
A manual run of a trigger that waits for an incoming event now reads as one line saying nothing was delivered. The explanation used to appear as a message, as though someone had sent it.
Also ran counts only the nodes that ran. A node the run read data from without running it, such as a file upload left disconnected on the canvas, no longer appears there.
An agent turn that never comes back shows in your run history as a failed run, with an error saying the turn was lost and that sending another message retries it. Those turns used to leave no run behind at all.