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.

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 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.

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.

• Dropdowns load again. Choosing a Page in Facebook, an ad account in Meta, or one of your posts in Threads failed with "Failed to load options", which left pasting the ID by hand as the only way through.
• Facebook actions that work on a Page, including posts, comments, reactions, insights, Messenger, and webhook subscriptions, now use that Page's own access token. They previously failed with an error about needing a Page access token even when the account had the right permissions.
• Four Facebook actions that could never run were removed: Create Album, Block User, Get Call-To-Actions, and Get Page Tabs. The node keeps 64 actions, including all 11 triggers. A saved workflow still set to one of them will stop with a configuration error.
• When a Meta action fails, the error now carries the reason Meta gives for it, plus the field it objected to and the trace id. An ad that cannot be created because the account has no payment method used to report only "Invalid parameter".
• Localized Items Batch runs again in Meta. The item type it requires is now its own Item Type field rather than something you had to know to add under Additional Fields.
• List Leadgen Forms runs again in Meta. It now fetches the Page's own access token first, which is what that call needs.

Connecting a Zoom account works again. NoClick was sending the list of permissions it wanted to Zoom's consent screen, which Zoom rejects for this app. Permissions now come from the Zoom app itself, so the consent screen loads and the connection completes.

We also removed 416 Zoom actions that could never run: 286 needed Zoom account admin permissions this integration does not hold, and 118 pointed at Zoom endpoints that do not exist. The node keeps 1,224 actions, including all 96 triggers. A saved workflow still set to a removed action now stops with a configuration error naming the problem, where before it failed with an error from Zoom.

Connecting Cloudflare by signing in failed with a message about an invalid scope. NoClick was asking for one permission Cloudflare does not define, and Cloudflare rejects the whole request at the first permission it does not recognize, so the connection never completed. That permission is gone and the sign-in finishes.

Connecting also asks for offline access now, which is what Cloudflare needs before it will issue the token that keeps a connection working past its first hour. Reconnect an existing Cloudflare credential to pick that up.

These operations returned a routing error on every run and now reach the right Cloudflare endpoint:

• The three Zaraz operations: Get Zaraz Config, Update Zaraz Config, and Publish Zaraz Config.
• All eight Secrets Store operations, covering both the stores and the secrets inside them.
• The four R2 custom domain operations: List, Create, Update, and Delete R2 Custom Domain.
• Get Vectorize Vectors By IDs and Delete Vectorize Vectors By IDs.
• Get Fonts Settings and Update Fonts Settings.
• Get Secondary DNS Config and Update Secondary DNS Config.
• Dismiss Attack Surface Issue.

Three more were reaching Cloudflare but sending a request it would not accept:

• Create Image Direct Upload Url sends a form upload, the only format Cloudflare Images takes for it.
• Create Ai Gateway and Update Ai Gateway send every field Cloudflare requires. Update reads the gateway first and changes only the fields you set, because Cloudflare replaces the whole gateway on each write.

Three operations are gone: Get Account Analytics, Get R2 Bucket Usage Summary, and Get Web Analytics Summary. Cloudflare serves that data only through an analytics API that refuses a credential you create by signing in, so they could not return anything. Cloudflare is now at 591 operations.

What NoClick asks for when you connect a service is now derived from what each operation actually calls, checked across every service that connects by sign-in. Operations that could only ever fail, because a permission they needed was never requested, now have it. Each integration's page lists the exact set NoClick requests.

A connection keeps only the permissions you granted when you made it, so reconnect the credential to pick up the new ones.

• Jira adds one permission that revives 52 operations across fields, screens, workflows, issue types, and other project configuration.
• GitHub adds the permissions behind its 15 gist operations and its organization reads, 25 operations in total.
• PagerDuty was requesting four permission names PagerDuty does not define. They are replaced with the real ones, alongside event rules and incident workflow instances, covering 22 operations.
• PostHog adds session recording writes, group reads, and organization member reads and writes. Airtable adds record comments, and Sentry adds team administration.
• Slack asks for more permissions too, including the one its On App Mention trigger needs. Tagging the bot in a channel could not start a run before, because the event permission was never requested.

Slack's 104 admin operations now carry an Enterprise Grid badge in the operation picker, and 7 Slack Connect operations an Admin install badge. Slack refuses to install an app that asks for those permissions on an ordinary workspace, so they run on a Bot Token credential from your own Slack app rather than on the sign-in flow. The badge appears when you pick the operation, instead of the operation failing on its first run.

Two operations that a connection you make yourself can never be granted are gone: LinkedIn's Get Post and List User Posts, which need a permission LinkedIn grants to approved partners only, and Dropbox's Permanently Delete File, which is limited to Dropbox Business apps.

145 Cloudflare operations were selectable in the picker but had nothing behind them, so every run returned "Unknown action". They now call the Cloudflare API: addressing and BYOIP prefixes, Intel and Security Center, Workers AI, Log Explorer and Logpull, Magic Transit, Radar AI, Calls and Realtime, Analytics Engine SQL, URL Scanner, Bot Management, and R2 event notifications.

Operations that need a plan you may not have are labeled in the picker: 45 are marked Enterprise, 7 Paid, and 3 Beta.

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 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.