July 2026
Everything that changed in NoClick in July 2026.
Improvements and fixes6
Undo can no longer empty your canvas. Pressing
Cmd+Zenough times used to walk a loaded workflow back to a blank graph and save it that way. Undo now stops at the workflow as it loaded. Undo and redo also stay out of text fields, soCmd+Zin the builder chat or a config field undoes your typing again.HubSpot workflow listing, website content search, file upload, and data imports work again. Upload File now imports from a URL you give it, and Create Data Import takes a File Url field pointing at the CSV to import.
HubSpot drops 2 more operations a connected account cannot run: Create Communication Channel, which HubSpot only allows to be read, and Refresh Access Token, which NoClick already does for you.
The AI builder no longer tells you a workflow with a live trigger and a missing credential "won't run". It runs on schedule and fails every time until you connect the account, and the builder now says so or offers to disable the trigger.
A workflow left named "Untitled" because its automatic naming failed now gets named on a later builder turn. A name you typed yourself is never overwritten.
The AI builder's check of custom interface components no longer reports an error in your code that came from its own checker, which used to send the builder into patch loops that removed working features.
HubSpot steps report failures instead of hiding them
A HubSpot operation that HubSpot rejected, for a permission you do not have or a record that does not exist, used to come back marked as a success with the real error buried inside the step's output. Those steps now fail, so the run stops at the problem and the error shows on the node. If a HubSpot workflow of yours looked like it was working, check its recent runs.
- HubSpot now asks for the permissions its operations actually need. The core CRM permissions stay required, and everything past them, such as HubDB, files, lists, sequences, marketing campaigns, and custom objects, is requested as optional, so the connection still installs on accounts whose HubSpot plan does not include them. Reconnect your HubSpot credential to grant the new permissions, since an existing connection keeps only what it was granted when you made it.
- HubSpot drops 16 operations that a connected HubSpot account cannot run: the four Webhook Subscription operations, three Calling Extension and two Video Extension operations, the five Social Post operations, List Social Media Channels, and Get Search Settings. The seven HubSpot triggers are unaffected.
- More HubSpot operations now work against a live account. The HubDB row and table operations, blog post and blog author creation, website page creation and updates, and the marketing events, files, audit logs, goals, sequences, business units, and website content listings all return data instead of erroring.
Slack, HubSpot, and Discord triggers register themselves
A Slack, HubSpot, or Discord trigger now starts listening as soon as it is part of your workflow, including when the AI builder added it. The subscription used to be created only when you opened the node's config panel, so a workflow you never opened looked ready and quietly missed its events. Existing workflows are repaired on their own within a day. The node's Status field says what it is listening to.
- Ask the AI builder or an agent about one of these triggers and it now tells you registration is automatic and there is no webhook URL to paste, instead of walking you through a manual setup that does not apply.
- A trigger whose Status field showed a registration error now clears it once the trigger is listening again, rather than keeping stale text.
Improvements and fixes2
The Upgrade to Plus and Upgrade to Pro buttons on the pricing page now open the purchase popup on your dashboard. They used to leave you on the dashboard with nothing open.
Opening the credits popup yourself, from the command palette or by clicking your credit balance, no longer claims you reached your credit limit. That message now appears only when a run actually ran out of credits.
Improvements and fixes3
Running out of NoClick credits no longer points you at your model provider. The message now says your NoClick balance is the one that ran out, and its Add credits button opens the credits popup right where the error is shown instead of loading a new page. Buttons that link to a provider's billing page are now limited to agent nodes, so another service whose own error text happens to mention credits no longer offers one.
A CLI coding agent's sandbox now stops once your credits are used up, rather than running on past a zero balance. You get the credit balance email naming the workflow it was working on. Starting a turn on a CLI agent now needs at least 1 credit, so a turn that does start has room to finish.
The Credentials tab no longer turns red on a node wired into an agent as a tool provider when none of the operations you allowed needs a credential.
Improvements and fixes1
The Run popup no longer offers interface blocks that start nothing, such as a standalone app or a display block, as places a run can start from. A block that feeds other nodes, like a form leading into Slack, is still offered. A workflow whose only entry point is an agent goes straight to the opening message screen again.
Improvements and fixes2
Changing an agent's model no longer empties the chat. The thread stays put until you send, and if the new model runs on a different harness or a different provider, the next message starts a fresh conversation that carries the earlier turns as context. Picking another model on the same provider continues the same thread and runs the model the picker shows.
Pipedrive drops six operations that could never work through a NoClick connection: the four Channels operations and the two video call provider links under System.
Improvements and fixes2
When the AI builder pauses to ask you a question, the workflow it has built so far is now saved right away. Your nodes stay on the canvas while you answer, and the builder continues from where it paused instead of rebuilding.
The first click on Add trigger or Add tool under an agent's message now opens the picker. It used to take two clicks.
Improvements and fixes1
Agents that chat on WhatsApp, Discord, Microsoft Teams, and other channels now reply to the right person and keep a separate memory per conversation. Replies that used to go nowhere now deliver.
Improvements and fixes4
Reopening a workflow's run results now shows the most recent run instead of an older one that was still in view.
The list of steps an agent took in a chat reply stays in place after you refresh the page or switch tabs.
An agent no longer runs when a step feeding into it has failed, so it stops instead of acting on missing or error data.
Real-time collaborative editing syncs reliably again.
Improvements and fixes4
Connecting an account now shows an error if the sign-in popup closes or fails, instead of leaving you on a spinner.
Public shared agent chats no longer show a spurious "still working on the previous message" error when you send a quick follow-up, and long conversations keep the message box in view instead of scrolling it away.
Agent replies read more cleanly: the run-results popup formats markdown instead of showing raw text, and messages that mention dollar amounts no longer render as math.
You can scroll up in the builder chat while a reply is streaming without being pulled back to the bottom.
Improvements and fixes1
Polling triggers now record a baseline the first time they run, so turning one on no longer floods your workflow with the existing backlog. Only activity after you enable the trigger starts a run.