September 2026

Scanning a WhatsApp QR code no longer warns that the connection you just made is missing. The node's Credentials tab judged the new connection against the credential list it had loaded before the scan, so for the moment it took the refreshed list to arrive it reported the attached credential as one that no longer exists or is not accessible. Nothing was wrong with the connection, and the warning cleared on its own.

An Instagram On Mention trigger reports who wrote the comment. When Meta's notification carried only IDs, NoClick read the comment back to fill in the rest but did not ask for its author, so data.author came back empty and author_available was false even when the commenter's username was there to be read. Mentions in captions were unaffected, and a mention Meta supplies no author for still reports author_available as false.

Opening NoClick from a Shopify store that has not finished installing now shows a Connect your Shopify store page with a Continue Shopify setup button, which opens Shopify's approval step in the same browser tab. It used to start that step inside the frame in your Shopify admin, which Shopify blocks.

A WhatsApp disconnection email waits for the link to stay down. A restart at the provider flaps every connection for well under a minute, and you used to be told to re-scan a link that was about to come back, which adds a second device link to the phone. NoClick now waits out a short blip before it checks, and if the connection recovers after an email went out, a follow-up tells you it healed itself and not to re-scan.

Connecting Instagram completes again. The connect window now reports success only once the connection is saved, an authorization that Instagram cut off from the page that opened it still lands, and cancelling and clicking Connect again starts a fresh attempt. New connections use Instagram's own sign-in, and Instagram accounts you connected through Facebook keep working as they are.

Create Comment Thread and Create Reply on Canva designs post your text again. Both were stopping with an error about a missing message field.

A new PostHog connection asks for everything the node uses: reading groups, reading and writing organization members, and writing session recordings. PostHog was dropping those permissions because NoClick declared them under a name PostHog does not read. Reconnect a PostHog credential you connected earlier to pick them up.

The Instagram and LinkedIn scraping steps fail the same way. A scrape that fails, is cut short, or returns records the node cannot read stops the run and names the reason, rather than handing an empty list to the next step.

Publish Photo Post waits for Instagram to finish fetching your image before it publishes. Publishing could fail with a message saying the media was not available, because a photo container is not ready the moment Instagram hands back its ID. Reels already waited this way.

Signing in with Instagram's Login option finishes and saves the connection, and NoClick can refresh it later. Connecting could stop with nothing saved.

An Instagram Login connection is treated as one everywhere it is used, including when an AI agent calls an Instagram operation as a tool. Its token could be sent to Facebook's API instead, which rejects it.

A Discord Bot Install credential whose bot is still in your server reads as connected again. Working Discord connections were being labeled Disconnected in the credential picker and flagged on the node's Credentials tab, with WhatsApp re-scan instructions under them. A Discord connection the bot really has been removed from is still reported.

When a connection really has dropped, the message on the node's Credentials tab now says how to repair that connection: re-scan the QR code for a WhatsApp credential, or add NoClick's bot back to the server for a Discord one. It used to give WhatsApp instructions whatever the connection was.

A Discord On Channel Message or On Bot Mention trigger scoped to one channel now fires for messages posted in the threads opened in that channel. Discord delivers a thread message under the thread's own id, so a reply inside a thread the agent had started was measured against the channel id and dropped. Leaving Channel empty was the only way to hear those replies.

Uninstalling NoClick from a Shopify store marks that store's connection as disconnected instead of leaving it looking healthy. Installing again from the Shopify App Store reconnects the same connection, and the permissions NoClick records are the ones Shopify actually granted.

The After Cursor field on Shopify's GraphQL product, order, customer, and collection queries works. Those queries also return the page information Shopify sends back, so you can page through more results than one call returns.

A Slack or WhatsApp agent that stopped reacting to messages works again. NoClick caps how many runs one channel or chat can start in a five minute window, so a reply loop with another bot cannot run away, and that counter could stop resetting. Once it did, every later message in that conversation was accepted and then dropped, with no run in Logs to show for it. The counter now rolls over as intended, and one that is already stuck clears itself on the next message.