August 2026

Shopify requires apps published on its App Store to use the GraphQL Admin API, so a store you connect with OAuth now runs the node's GraphQL operations and all 7 of its triggers. That covers the blog and article operations, the prebuilt queries for products, orders, customers, inventory, collections, and fulfillment orders, and Execute Custom Graphql Query and Execute Custom Graphql Mutation, which reach the rest of the Admin API within the permissions you approved.

The node's older operations still run on a store connected with an Access token, or with OAuth through your own Shopify app. Pick one of them on a store connected with NoClick's app and the operation stops and asks you to choose a GraphQL operation or connect your own app.

The six blog operations moved across as part of this, so List Blogs, List Blog Articles, Get Blog Article by Id, Create Blog Article, Update Blog Article, and Delete Blog Article now run on a store connected with OAuth.

Fourteen operations left the Shopify node: the five Price Rule operations, the three Discount Code operations, the five Gift Card operations, and Create Draft Order with Graphql. Each one needed a store permission NoClick does not ask for, so every call returned a permission error instead of doing anything. They no longer appear in the operation picker, and the node now lists 102 operations. A workflow still set to one of them needs a different approach.

The Store name field now takes your storefront's own domain, such as your-shop.com, or the admin address you copied from your browser. NoClick reads the store handle behind it, so you no longer have to know the my-store part of my-store.myshopify.com before you can connect. If no store can be found for what you entered, the error says where the handle appears in your Shopify admin URL.

The popup that opens when a run finishes now walks through the run in reading order instead of listing node outputs one at a time. What came in shows the event that started the run in its own app's frame, so a WhatsApp message looks like a WhatsApp message and an invoice looks like an invoice. What the agent did lists the agent's tool calls with the time each one took and the detail that matters on the row, such as the channel a message went to, and any row opens to show what it was Called with and what it Returned. What went out frames each message the agent sent the way its destination shows it. An agent that worked and chose to send nothing says so in its own words, and a failed run shows the error with a way to fix it instead of a verdict.

The run switcher at the top of the popup reads Latest run and opens your run history: each row has its status, what fired the run, how long it took, how many nodes ran, and the error on runs that failed. It stays reachable while a run's results are still loading and on a workflow that has never run, so history no longer dead-ends.

Every place you upload a file now shows a percentage and a progress bar instead of a spinner: interface blocks, form file fields, the agent chat composer, the filesystem node's file browser, the chat Files menu, and the media pickers in a node's config panel. An upload that fails says why on its own row.

A single file can be up to 100 MB everywhere, workspace uploads included.

In the Serverless Function node, an input named data is now just data in your JavaScript, the way it already was in Python. inputs.data still works, and your own const data = ... still takes precedence. Code the AI builder wrote against the documented input names used to stop with ReferenceError: 'data' is not defined.

The home page at noclick.com now shows three parts of NoClick working, in order: an agent handling messages from the apps you already use, the builder turning a prompt into a workflow, and the run record showing every tool call and result afterwards. Each one is the real interface, not a picture of it.

Below them is the list of what NoClick can do and one Start Free button.

Template pages are now built around the agent. Each one previews the real canvas, lists the services setup will ask you to connect and the questions it will ask, and shows the staged conversations the template ships so you can see the agent work before you take a copy. Click Use this agent and your copy opens straight into full screen setup. The gallery is now Agent Templates.

The agent chat in a workflow's Interface tab now lays itself out from the width it actually has, rather than the width of the window. When something else takes up the screen, like the builder drawer or a split view, the chat keeps its full width and Settings opens as a sheet over it instead of splitting the row.

• History, Files, Share, and Settings in the chat header collapse to icons when the header is too narrow for their labels.
• The History, Files, and model pickers open as full-width sheets on phones instead of cramped dropdowns.
• Tablets in portrait use the single-column tab layout, so the navbar and canvas are no longer squeezed into a sliver.

The Add trigger and Add tool palettes on an agent node now search each service's description, its aliases, and the actions it can perform, not just its name. Searching for "schedule", "timer", or "every day" finds the Schedule trigger, and "create issue" surfaces Linear, Jira, and GitHub.

Services also carry the same name here as on the canvas. Schedule used to be listed as "Trigger Cron" and X as "Twitter", and about a third of the catalog appeared under a name that did not match the one you see everywhere else. Once you pick a service, its list of triggers is searchable by keyword too.