August 2026
Everything that changed in NoClick in August 2026.
Improvements and fixes1
Reconnecting NoClick to ChatGPT works again. ChatGPT changes its callback address between connector versions, and that stopped every re-authorization.
Your webhook can return whatever you want
A Webhook trigger set to When Last Node Finishes used to hand the caller NoClick's own record of the last node's run, with your data buried inside it. Now the last node decides the response. Return an object with a status, an optional headers map, and an optional body, and the caller gets exactly that: a JSON body is sent as JSON, a string body is served as a web page unless your headers say otherwise, and a status with no body works for redirects.
A Serverless Function node that returns a plain string serves it as an HTML page, so a workflow can answer a request with a real REST payload or a real page. Nodes that return anything else keep the previous response.
Improvements and fixes1
A tool call to your hosted MCP server that fails now comes back to the client as an error, carrying the message the service gave and the HTTP status. Failures used to arrive looking like successful results, so a connected assistant kept guessing instead of reporting the problem.
Improvements and fixes1
Errors now say what actually went wrong. When a page failed, the error screen reported a fault in itself rather than the underlying problem, which also left connecting an MCP client while signed out showing "Unexpected Server Error" instead of taking you to the sign-in page.
Improvements and fixes1
Expressions written in another automation tool's syntax are now rejected when the AI builder or an MCP client saves them, with a message showing the NoClick form. Accessors like
$input,$node[...], and.item.jsonafter$('node')used to save without complaint and then fail every run.