June 2026

Everything that changed in NoClick in June 2026.

Limit an agent tool to specific resources

When you allowlist an operation on a tool-provider node, you can now pin it to specific resource IDs. Expand Limit to specific... under an operation and pick which documents, sheets, or other records the agent may act on. When a create operation makes a new resource, its ID is added to the matching scope for you, so the agent can immediately read back what it just created.

Trigger workflows from Discord

Connect Discord by signing in and installing the NoClick bot into your server, with no keys to copy. You can then start a workflow when an app event happens: your bot is added to or removed from a server, a premium entitlement is created, updated, or deleted, or a slash command is run. Wire the trigger into an AI agent, or add the Discord node as an agent tool provider so the agent can run Discord actions for you.

Agents reply to email

Wire the inbound email trigger to an agent and the agent can reply in the same thread, securely scoped to that conversation. A new send email node delivers notifications to your inbox, formatted from markdown, with a one-click disable link.

Improvements and fixes1
  • Connect triggers and tools to an agent straight from the chat sidebar and the agent's config panel.

Use your integrations as agent tools

Wire any integration node into an AI agent and the agent can call its operations directly, like creating a Linear issue or sending a Slack message. You choose exactly which operations the agent is allowed to use, and every tool call shows up live in chat and in run replays.

Triggers fire straight into agents

Wire a trigger (Telegram, Slack, email, or an alarm) into an agent and the incoming event becomes the agent's message, with conversations threaded per channel. Pair it with send operations to build a reply bot entirely on the canvas.

Improvements and fixes1
  • Mount GitHub repositories into a coding agent's sandbox, with git and the gh CLI already authenticated.