September 2026

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.

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.

Taking a published app down now finishes the job before the app leaves your list: the API key is revoked, the files are deleted, and the CDN cache is cleared. If any of that does not complete, the app stays listed so you can try again instead of vanishing while the page is still reachable.

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.

An Instagram On Mention trigger reports who wrote the comment. When Meta's notification carried only IDs, NoClick read the comment back to fill in the rest but did not ask for its author, so data.author came back empty and author_available was false even when the commenter's username was there to be read. Mentions in captions were unaffected, and a mention Meta supplies no author for still reports author_available as false.

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.

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.

Opening NoClick from a Shopify store that has not finished installing now shows a Connect your Shopify store page with a Continue Shopify setup button, which opens Shopify's approval step in the same browser tab. It used to start that step inside the frame in your Shopify admin, which Shopify blocks.

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.

Connecting Instagram completes again. The connect window now reports success only once the connection is saved, an authorization that Instagram cut off from the page that opened it still lands, and cancelling and clicking Connect again starts a fresh attempt. New connections use Instagram's own sign-in, and Instagram accounts you connected through Facebook keep working as they are.

Create Comment Thread and Create Reply on Canva designs post your text again. Both were stopping with an error about a missing message field.

A new PostHog connection asks for everything the node uses: reading groups, reading and writing organization members, and writing session recordings. PostHog was dropping those permissions because NoClick declared them under a name PostHog does not read. Reconnect a PostHog credential you connected earlier to pick them up.

The Instagram and LinkedIn scraping steps fail the same way. A scrape that fails, is cut short, or returns records the node cannot read stops the run and names the reason, rather than handing an empty list to the next step.

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.

Agents that run on a saved model credential work again. Since the previous release, an agent using an OpenRouter key or a Codex, Claude Code, or OpenCode sign-in failed at the start of every run with an error about its credential type.

Publish Photo Post waits for Instagram to finish fetching your image before it publishes. Publishing could fail with a message saying the media was not available, because a photo container is not ready the moment Instagram hands back its ID. Reels already waited this way.

Signing in with Instagram's Login option finishes and saves the connection, and NoClick can refresh it later. Connecting could stop with nothing saved.

An Instagram Login connection is treated as one everywhere it is used, including when an AI agent calls an Instagram operation as a tool. Its token could be sent to Facebook's API instead, which rejects it.

Sending an agent a second message while it is still working no longer leaves it stuck as working. When the agent takes several messages into one turn, the reply is matched to the messages it actually read, and Inputs consumed in the run's results lists them.

Both CLI dropdowns show plain model ids again. The Codex labels had picked up Codex's one-line model descriptions, which the picker printed a second time under each row and the closed field repeated as a sentence.

A Discord Bot Install credential whose bot is still in your server reads as connected again. Working Discord connections were being labeled Disconnected in the credential picker and flagged on the node's Credentials tab, with WhatsApp re-scan instructions under them. A Discord connection the bot really has been removed from is still reported.

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.

A Discord On Channel Message or On Bot Mention trigger scoped to one channel now fires for messages posted in the threads opened in that channel. Discord delivers a thread message under the thread's own id, so a reply inside a thread the agent had started was measured against the channel id and dropped. Leaving Channel empty was the only way to hear those replies.

Uninstalling NoClick from a Shopify store marks that store's connection as disconnected instead of leaving it looking healthy. Installing again from the Shopify App Store reconnects the same connection, and the permissions NoClick records are the ones Shopify actually granted.

The After Cursor field on Shopify's GraphQL product, order, customer, and collection queries works. Those queries also return the page information Shopify sends back, so you can page through more results than one call returns.

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.

A Slack or WhatsApp agent that stopped reacting to messages works again. NoClick caps how many runs one channel or chat can start in a five minute window, so a reply loop with another bot cannot run away, and that counter could stop resetting. Once it did, every later message in that conversation was accepted and then dropped, with no run in Logs to show for it. The counter now rolls over as intended, and one that is already stuck clears itself on the next message.

The working indicator in an agent chat stops when the answer does. A finished turn could keep the agent showing as working under a reply that had already arrived in full, and it stayed that way until you reloaded the page.