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 Shopify node can now work with your store's blog. List Blogs finds the blog to write to, List Blog Articles and Get Blog Article by Id read what is there, and Create Blog Article, Update Blog Article, and Delete Blog Article change it. An article carries a title, an HTML body, an author, tags, a summary, a featured image with its alt text, and whether it is Published or Hidden, so an agent can draft a post and leave it hidden for you to review.

Reading and writing blog content is a new permission, so reconnect your Shopify account before using these operations.

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.

Type @ in an agent chat and a list of the conversation's workspace files appears. Pick one and its full path is inserted into your message, so you can point the agent at a file without typing the path out. Arrow keys move through the list, Enter or Tab accepts the highlighted file, and Esc closes it.

You can also delete files now. Each row in the Files menu has a trash button that asks you to confirm on the row itself before the file is removed from the workspace.

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.

You can now upload files into a workspace yourself, so the agent finds them there on its next turn. In an agent chat, use the upload button in the Files menu header, and the files land in that conversation's workspace. In a filesystem node's config panel, use Upload in the file browser, and they land in that node's volume.

Instagram has a second connection type, Login, which signs you in with an Instagram professional account. Nothing has to be linked to a Facebook Page, and there are no keys to copy. The System user token and Page access token options are unchanged.

Hashtag search, product tagging, and business discovery only exist on the Facebook route, so on a Login connection those six operations stop with a message telling you to connect through Facebook instead.

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.

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.

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.

The Honeycomb node brings your observability data into workflows, with 88 operations across events, datasets and columns, boards, queries, markers, triggers, SLOs and burn alerts, and the v2 management API. Connect with a Honeycomb API key or a management key, and pick the US or EU region.

• Two triggers start a workflow when Honeycomb alerts: On Trigger Fired and On Burn Alert. NoClick registers the webhook recipient for you, and can attach it to an existing trigger or burn alert.
• Dropdowns load your real datasets, boards, columns, markers, SLOs, and recipients, so you pick by name instead of pasting IDs.

A photo, voice note, or document sent to a WhatsApp-triggered agent now arrives as a link the agent can download, along with the file type and name. The message caption comes through as the text. Media used to reach the agent as a placeholder with nothing behind it.

• Files up to 25 MB are saved to your workflow's resources at the moment the message arrives, so the link keeps working for the whole run.
• Larger files, and files the provider no longer holds, are reported to the agent as media it could not retrieve, so it can ask the sender to resend instead of guessing.
• Nodes wired downstream of the WhatsApp trigger read the same link from the trigger output.