August 2026

Opening NoClick from the admin of a store that installed it from the Shopify App Store now shows a NoClick page inside Shopify. It names the store, shows the connection as Connected and Ready for workflows, and has an Open NoClick workspace button for building and running the workflows themselves.

You can now install NoClick on a Shopify store starting from Shopify. Shopify asks you to approve the store permissions first, then you sign in to NoClick, and the store lands in your account as a connected Shopify credential named after the shop. It is ready to attach to any Shopify node, so you do not have to connect the store a second time from the node's config panel. Installing again on the same store updates that connection rather than creating a second one.

An account that installed NoClick this way stays on the Free plan. Paid plans and recurring credit top-ups are not offered through that channel, so Settings → Billing shows a Free Plan card explaining this instead of the upgrade options, and the upgrade prompts elsewhere in the app say the same. Everything else works as it does on any Free account, including the 25 monthly credits and the 5 workflow limit.

The Schedule node's picker now reads as one sentence you can edit in place: "Every 30 minutes · all day · every day · all year". Click all day to set a from and to time, click every day to pick the weekdays it runs on, and click all year to limit it to a range of dates in the month, a range of months, or both. Stacked limits all have to match, so "every 30 minutes, from 9:00 AM to 6:00 PM, on weekdays, from the 1st to the 15th, from March to October" runs exactly that and nothing else.

The words in the sentence adapt to the frequency you picked. Second, minute, and hour schedules take all three limits, a daily schedule takes the day and date limits, and weekly and monthly schedules take the months. Switching frequency drops the limits the new one cannot carry. Every limit clears back in place from the same popover, and the summary line under the picker restates the whole schedule in plain language.

Run times, time windows, and day boundaries are now evaluated directly in the timezone you pick on the node. A 9:00 AM schedule fires at 9:00 AM local time year round instead of moving by an hour when the clocks change.

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 agent on a workflow now has a Linux sandbox with a shell, whether or not you have wired a filesystem node to it. The sandbox starts the first time the agent actually runs a command, so an agent that only ever answers in chat never starts one. In a chat, the agent's /workspace folder is kept per conversation and survives across runs.

A test run answers shell commands with made-up output like every other tool call, so a rehearsal never starts a real sandbox.

The AI builder can look things up for itself while it builds too. Paste an API URL or a sample payload and it can fetch the URL and inspect the real response instead of wiring a node blind. It has no access to your connected accounts while it does this.

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.

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.

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.

Every page under noclick.com/agents now has a Setup section under the hero that walks the whole path before you commit to it: choose whether the agent runs On your computer or In the cloud, pick what it can do in each app, then sign in to each app once.

The last step follows your choice. On your computer ends on the exact command that connects your coding agent to NoClick, shown with a placeholder link because setup mints the real one. In the cloud ends on signing in to the coding agent NoClick runs for you.

The Agent Templates gallery now opens on a search box and a set of filters. Search by job, outcome, app, or node, then narrow by category (Sales, Support, Marketing, Operations, or Engineering), by the apps and nodes a template uses, or by the trigger that starts it.

Every card previews the template's real canvas, drawn from its saved nodes and connections, so you can see the shape of a workflow before opening it. Show more templates loads the catalog in batches, and a search always covers all of it.

Click Test in an agent's chat header to run it against a staged event. Your real agent runs on your real model and prompt, but every tool call it makes is answered with made-up data, so nothing reaches your accounts and nothing is sent. The screen says so up front, and every answered call carries a simulated pill.

Gmail, Slack, WhatsApp, and Telegram triggers ship written situations to test against, and every other trigger gets an editable sample. You can rewrite the staged message in place, keep several named runs per agent, and share a finished run as a read only page anyone can open.

The canvas has a permanent Setup tab (shortcut S) that reads your workflow and lists what it still needs: accounts to connect, variables to fill, actions to pick, which agent runs it, and a Test Run at the end. Two nodes for the same service ask for one account, not two, and connecting once covers both.

Setup ends on something you can act on. For a workflow that hosts an MCP server, that is the connect step for your coding agent with a live check that flips to Connected the moment your client calls in. For everything else, it is a Test Run.

Declare values once under Settings > Variables and reference them from any node config as {{vars.name}}. A bound field shows the resolved value and edits write back to the variable, so you change it in one place.

Mark a variable per user and its value is cleared whenever someone copies your workflow, which turns it into a question their Setup asks. That is how a template can ask a new owner for their repository or their channel instead of quietly running against yours.

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.

When the AI builder asks you to choose between options and more than one can apply, the choices are now checkboxes under a Select all that apply hint instead of letting you pick a single option. Tick as many as you need and the builder receives them all.

Questions where only one answer makes sense still show round options and take one pick, so the form tells you which kind you are answering.

A chat bubble now sits in the bottom right of the app and of noclick.com, so you can ask a question without leaving what you are working on. When you are signed in, the conversation carries your email and plan, so we can see which account we are looking at.

• The bubble stays off the pages your own users see: shared agent links, builder input links, public workflow and share pages, credential request links, and embedded canvas previews.
• The Get Started checklist that used to sit in that corner of the canvas is gone, along with the tour that came with it. The walkthroughs for inviting a teammate, publishing, and the agent chat are unchanged.

Asking in Discord still works the same way.

Triggers that poll on a schedule, like Google Forms On Form Response, Google Sheets On New Row, and Gmail Poll for New Emails, now start watching as soon as their configuration is complete and treat anything that arrives after that as new. Before, the schedule could be created before the trigger had its required fields, which produced a failed run every interval while you were still filling in the panel, and the first poll after that counted everything already there, including the test entry you had just submitted, as history.

• The schedule is created only once the trigger's required fields are filled in, so ticks during setup no longer appear as failed runs in the Logs tab.
• A turn where the AI builder or the MCP server fills in the last required field now registers the trigger, so "your trigger is set up" means it is listening.
• Pointing a trigger at a different form, sheet, or mailbox starts a fresh baseline for the new resource instead of firing for everything already in it. Edits that do not change what the trigger watches, including the ones the AI builder makes while finishing a workflow, no longer reset what it has already seen.
• Running the workflow yourself delivers newly polled items to an AI agent wired to the trigger, the same as a scheduled run. A poll that finds nothing new still runs nothing downstream, manual runs included.
• Changing a node away from its trigger operation removes its schedule, and a trigger whose registration never landed is repaired on its own within a day.

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.