August 2026

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