Changelog

A memory is now an object of its own, with a name, that any number of agents can read: what every agent of your company should know, or what one agent learned that another needs. Attach it with memories=; it's read-only unless attached with writable(). Each agent still keeps a memory of its own.

company = noclick.Memory.from_name("company", create_if_missing=True)
company.save("tone", "Warm, brief, no jargon.", description="How we write")

support = noclick.Agent.from_name("support", create_if_missing=True,
                                  instructions="Answer billing questions.", memories=[company])

The noclick npm package now covers everything the Python package does, reading the same responses: an agent's A2A card, a channel's budget and halt reason, ExecResult.ok, ToolResult.approveUrl, usage(), and more. Methods take Python's names in camelCase, so an example from either guide reads the same.

Every code block in the guide now comes in both languages. Choose Python or TypeScript in the menu in the top bar, or in a block's header, and every block on every page follows, install commands included. The reference reads in either language too, with the same pages and anchors: Python or TypeScript.

Your assistant's email address used to take only your own mail. It now takes anyone's, so people and other agents can write to it. Mail from someone else never lands in your own thread with it: each sender's mail gets a conversation of its own.

Set what your account may spend in each billing period in Settings → Plan and billing. Once the period's spend reaches it, every call that costs money fails with noclick.SpendCapExceeded, its scope "account", until the period resets. What you already have keeps renewing (numbers, domains, storage), and apps keep serving pages until the period reaches twice the cap. Only the account's owner sets or raises it.

Every account has its own invite link, under your balance in the sidebar. When someone you invite starts using NoClick, $2 is added to your balance.

Code in an app's backend can now call the whole SDK and message your agents, signed in as its deployment, with no key to keep. It reads and writes only what it made itself, never another app's resources. Each app has a monthly budget, budget_usd_per_month ($10 unless you set another): once it's used, the app keeps serving pages and reading its data, while its paid calls fail with noclick.SpendCapExceeded.

Settings → Usage lists what your account was actually charged, in dollars, with a plain name for each charge, and drills down to what used it: which agent, app, number or automation.

Deleting an app, database, bucket, dict, queue, repo, volume, inbox or agent now moves it to the trash, where it stays restorable for 30 days. A write that can be taken back records how, so its operation can be undone. Only purging is permanent.

item = noclick.Database.from_name("orders").delete()
print(item.kind, item.name, item.purge_after)   # database orders 2026-11-14 ...

item.restore()   # back under its name, every table and row with it

Deployment.check loads pages of a deployment in a browser and reports each one's status, load time, console errors and a screenshot. Give an app check_paths and a promote is checked where it serves before production switches: a failed check leaves production as it was. Every promote bookmarks the app's databases first, so undoing it restores them too.

checked = preview.check(["/", "/book"]).wait()
for page in checked.paths:
    print(page.path, page.status, page.problem)

An app whose preview_resources is branch gives each preview branch its own copy of the databases, buckets, dicts and queues its code names, made at the branch's first write. Until then its reads reach production, read-only, so a branch that only reads makes nothing. Inside an app, Database.from_name finds the app's own database for the environment it runs in.

An app's runtime is auto by default: each deployment reads the commit it builds and runs where it says. A wrangler config, a JavaScript framework or plain files run on the edge; a Dockerfile, or a server in another language, runs in a container. Set edge or container to pin it.

An agent's push is checked before it lands: the default branch only fast-forwards and can't be deleted. A branch an agent rewrites or deletes is kept for 30 days; list them with Repo.backups and make one a branch again with Repo.restore_backup.

app.sign_in commits sign-in code into an app's repo, with its users in the app's own database. Google, Apple and Microsoft now sign people in through NoClick, so they work as soon as the operation ends, with no client to register at the provider. GitHub still uses your own client.

app = noclick.Project.from_name("booking")
setup = app.sign_in.enable(providers=["email", "google", "apple"]).wait()
print(setup.managed_providers)   # ['google', 'apple']

Make an inbox at a domain you bought through NoClick and its mail records are set up at once; on a domain you connected, the inbox goes on a subdomain. Mail to the address reaches the agent you name.

support = noclick.Agent.from_name("support-bot")
inbox = noclick.Inbox.create(local_part="help", domain="mail.acme.test", agent=support)
print(inbox.address)   # help@mail.acme.test

What you text NoClick's WhatsApp and iMessage numbers, or say when you call, goes to NoClick's assistant. answer_with sends it to an agent of yours instead: a text's reply goes back on the app you texted on, and on a call the reply is read aloud.

owner = noclick.Human.owner()
owner.answer_with(assistant)

Repo.commits lists a branch's history, newest first, and each commit's page in Resources shows its changes, file by file.

From a domain's page in Resources, pick one of your websites to serve there. Each name says where it stands: registering, DNS, certificate, then live. A purchase that fails frees the names it was going to serve.

Workflow.create with instructions has NoClick's builder make the automation, as it does in the app. Change it the same way, by describing the change, and run, pause and publish it from your code.

brief = noclick.Workflow.create(
    "Morning brief",
    instructions="Every weekday at 8, email me today's calendar and the unread emails that need a reply.",
)
result = brief.latest_build.wait(timeout=900)
print(result.summary)

Searching for phone numbers is open to every account. Buying one, like anything paid up front, needs $5 in your balance on any plan, in place of the Member plan. A quote, a purchase's first step, says so before anything is bought, with an offer of funds to add.

Numbers are sold in every country our carrier covers, each priced by its own search. A country that asks who holds a number takes the holder's address with the purchase. One that asks for documents takes them as uploads, and the carrier's review can take a few days, so buy returns a PhoneNumberOrder rather than the number.

holder = noclick.NumberHolder(name="Dana Ruiz", street="Keizersgracht 1", city="Amsterdam",
                              postal_code="1015 CJ", country="NL", phone="+31612345670")
noclick.PhoneNumber.buy(pick, max_monthly_usd=5, address=holder)

Every account, on every plan, can now make keys and call the API, the SDKs and the MCP server. Start with Getting started.

The SDK is one package in each language, noclick on PyPI and npm, for the whole platform. The bridge custom components use in NoClick interfaces is part of it, as noclick/embed; components inside an interface keep importing @noclick/sdk.

pip install noclick

Every connected account now carries its own approval rules, and they apply to everything that uses it: your agents, your coordinator, and any MCP client. Open Settings → Credentials and click the shield on a connection to reach its Tool permissions page.

A locked action runs nothing until you say so. The call waits, the exact arguments it would send are shown to you, and you approve or decline it.

• The Use without approval row sets everything at once. Read-only lets reading actions run and locks the rest, All lets every action run, and None locks everything, including actions the service adds later. Search the list to lock one action on its own.
• Requests arrive under Needs you on the Dashboard, where you can read the arguments and decide without leaving the page.
• Approving admits one call with exactly those arguments, and it has 30 minutes to run. Different arguments, a second attempt, or a change to the rules each need a fresh approval. An untouched request expires after 24 hours.
• Agents and MCP clients can add restrictions but never remove one. Unlocking happens only on the permissions page, signed in as the connection's owner.
• Operations you allowlist on a tool provider node now carry a lock in the node settings, so you can see and change what needs approval without leaving the workflow.

The Twilio node gained two call operations, so a number you already own can carry a voice agent.

• On Incoming Call is a trigger. Pick the Phone Number that should ring, write a Greeting, and NoClick points that number's voice webhook at your workflow. The agent wired to the trigger answers and holds the conversation live.
• Place an Agent Call is a tool an agent calls itself. Give it a From Number, a To number, and a Goal in plain words. It returns straight away while the call runs.
• A finished call comes back as a message in the agent's chat, with the transcript and how long the call lasted. An outbound call reports back to the agent that placed it, in the conversation it was placed from, so a workflow no longer needs an On Incoming Call node to hear about a call it made.
• Both operations need an Account SID and Auth Token credential, because an API key cannot verify the webhooks Twilio signs. One number rings one agent, and a second workflow that tries to claim it is told which workflow holds it.

Every account now has a coordinator: one assistant that sees the whole account rather than a single workflow. It reads your workflows and runs, hands builds and fixes to the AI builder, passes work to agents you already have, and connects accounts for you.

• It watches failed runs. When a workflow fails, the coordinator looks into it: it asks the builder to diagnose and fix, pauses a workflow that is clearly finished with, or tells you when only you can fix it. A run that failed for want of credits never wakes it, because the credits alert already covers that.
• Memories is a new card on the Dashboard. It holds what the coordinator has learned about you and your work, as entries you can read, edit, write yourself, and delete. Each one is filed as About you, Preferences, Project context, or Reference.
• Preferences live there too, rather than in a settings page. Tell the coordinator to stop triaging a workflow, or which channel to reach you on, and it keeps that as a memory.
• It reaches you where you last wrote to it, on WhatsApp or by email. It has its own inbound address on noclick.app, so you can mail it and it answers on the same thread.
• It makes images and video on request. Video generation is available on the Plus and Pro plans.
• Your agents can message it as well, so an agent that hits something it cannot fix has somewhere to send it.

The sign-in page and the in-app sign-in panel now offer Continue with phone. Type your number, tap Text me a code, and enter the code to sign in. A number NoClick has not seen before makes an account, so the same form covers signing up. The number field has a searchable country picker, adds the calling code to digits typed without one, and formats the number as you type.

The number you message NoClick from on WhatsApp signs you in to the same account, so a chat you started on your phone and the workflows you open in the browser are one account rather than two.

• Phone is now a section in Settings for every account. Add a number, prove it with the code we text you, and WhatsApp messages and calls from it reach your account. Codes expire after ten minutes. Each row says whether the number was Verified with a code or Linked on WhatsApp.
• An account can link up to five numbers, and a number belongs to one account at a time. Unlink frees a number for another account to claim, and a number that is the only way into an account cannot be unlinked until the account has an email address.
• A chat that started on WhatsApp with no account behind it can be connected to an account you already have, from inside the chat. Ask to connect the email you sign in with, and NoClick emails that address a six digit code for you to send back. The code expires after fifteen minutes and is spent after five wrong tries, and nothing moves until it matches, so naming an address you do not hold reaches nothing. On a match, your workflows, connected accounts, and the chat itself move to the account with that email. Where no account has that address, the phone account takes the email so you can sign in with it too.

Pick Direct Post Video or Direct Post Photo and the node settings now show a Post to TikTok panel: the connected creator's name, a preview of the media and caption, and the posting options TikTok currently allows on that account. Visibility is never filled in for you, comments, Duet and Stitch stay off until you turn them on, and an interaction the creator has turned off in TikTok cannot be enabled from here.

Every run re-checks those options against the account before it posts, so a visibility or an interaction the account no longer allows fails the run instead of publishing something more widely visible than you chose.

• Commercial content has its own controls. Disclose commercial content reveals Promote your own brand and Paid partnership with another brand, at least one of which has to be chosen, and a paid partnership cannot be posted privately. The workflow will not run while those settings contradict each other, and the panel links the TikTok policies you are agreeing to. AI-generated content marks a post as AI generated.
• The node output now carries published and publish_status alongside status, because TikTok accepts a post before it finishes processing it. If it is still processing, pass the returned publish_id to Check Video Publish Status rather than running Direct Post again, which posts a second time.
• Video you attach to the node is uploaded to TikTok directly, so it no longer needs a public address. Hosted video and photo URLs still have to be HTTPS on a domain verified for your TikTok developer app.
• Connecting another TikTok account now always shows TikTok's own consent screen. An already signed-in session used to be approved silently, which could reconnect the same creator when you meant to add a different one.

Pasting an API key used to save whatever you typed. A key with a stray line break, a web address pasted into a token field, or a key the service does not accept all saved looking connected, and you found out at the first run. NoClick now tidies the value and asks the provider about it before storing anything.

When the provider answers, the form shows what it said about your account rather than a tick: your own boards, sites, or workbooks, or Connected as and the account name. When the provider refuses, nothing is saved, and you get its own words along with what that usually means, such as an address serving a sign-in page instead of an API, or a key that reads as truncated or revoked. When NoClick cannot reach the provider at all, the credential saves and says Saved, not verified rather than claiming to be working.

• Problems are reported under the field they belong to. A web address pasted into a key field, placeholder text left in, and a value the service's own rules reject each name the field, and clear as you edit it.
• Credential forms now show the setup instructions and the per-field help for the service. Both were already written for each service and neither was displayed.
• A credential that proved itself when you connected it is remembered as Verified, with the account it connected as, so a node's Credentials tab says more than that something is attached.
• Tableau accepts your site address as it appears in your browser. Paste the whole URL into Server URL and NoClick fills in Site Content URL from it. The Cloud Manager console address is refused when you save, because it never serves the API, and the message names what to use instead.
• The same check runs wherever a key is entered: on a node, in Settings → Credentials, during Setup, and on a link someone sent you to connect an account for their workflow.

Instagram has a new On Mention trigger. It runs your workflow when your connected account is @mentioned in a comment or in the caption of a public post or Reel, including on someone else's post. Both kinds are included by default, and nothing is polled: Instagram pushes each event as it happens.

The event arrives with the text, the author, and links to the media, so you can wire it straight into an HTTP Request step and send it to your own backend. It tells you which kind of mention it was, and marks an author or a media link as unavailable when Meta does not supply one, rather than leaving you to guess. Each event carries an event_id you can use to skip duplicates. Private posts and Story mentions are not covered.

• On Mention uses the Facebook login connection, which is offered again when you connect Instagram. Mentions on other people's posts reach NoClick through the Facebook Page linked to your Instagram account, so that trigger needs the Page where On Comment and On Message still use the Login connection. An existing mention trigger on a Login connection keeps working for mentions on your own posts, and its Status field now tells you to reconnect it for mentions elsewhere.
• Connecting Instagram through Facebook finds Pages that belong to a business portfolio. NoClick now asks for the business permissions those Pages require, so an account with full portfolio access is no longer told that no Instagram business account was found. You are asked to approve the extra permissions the next time you connect.
• Connecting through Facebook reads your whole list of Pages. Accounts with enough Pages to span more than one page of results used to be told nothing was found when the Instagram account sat further down the list.
• A failed Instagram connection says which of three things went wrong: Facebook granted no Pages at all, it returned a Page with no Instagram account linked, or a Page could not be read. Each message names what to change and which Pages were involved, so you can fix the grant instead of retrying the same sign-in.

A voice note sent to an agent on WhatsApp, Telegram, or Discord used to arrive as a link the agent could not listen to, so the best it could do was ask the sender to type it out. Audio that arrives with a message is now transcribed, and the transcript becomes part of the turn the agent reads, so it answers what was actually said. A document that arrives the same way has its text pulled out at no cost, and photos and videos keep their link.

• This covers WhatsApp, Telegram, Discord, attachments on an inbound email, and files you upload in the agent chat. Telegram attachments are also saved to the workflow's resources as the message arrives, so a voice note plays in the run and chat views instead of showing an ID you cannot open.
• Files shared in a Slack message reach the agent too, up to three per message and 25 MB each. Slack keeps its file links private to the workspace, so NoClick saves a copy to the workflow's resources and gives the agent a link it can fetch.
• The transcript appears under the audio player in the agent's chat and in the run view, so you can check what the agent heard.
• Transcription is on by default and can be turned off per agent: Transcribe Voice Messages under Advanced in the node's settings, or Voice transcription under Capabilities in the agent chat's Settings. With it off, the agent is told that a voice message arrived and can ask the sender for text.
• Transcription costs credits like other AI usage. Audio is transcribed up to 20 MB and 10 minutes, at most three audio files per message. Anything larger, longer, or in a format the transcriber does not accept becomes a note telling the agent to ask the sender for text instead. A Test Run transcribes nothing, because the media it stages is made up.

The Setup tab now ends with a check on the workflow itself. It reports one of six states: setup unfinished, configured but unverified, registered and waiting for a real input, a reporting deadline armed, a real input received, or nothing automatic wired at all. When an input has arrived it names the node, when it arrived, and what the run did with it, and a Refresh button rechecks without reloading the page. It also says outright that a Test Run is simulated and that a send the provider accepted is not proof it was delivered.

• A trigger registers only once the path it starts can run. A trigger whose workflow is still missing an account, an agent's instructions, or a required field no longer shows as live while nothing could have run. Fix what is missing and the trigger registers itself the next time the workflow saves.
• A WhatsApp trigger that could not register says why, for example that the saved phone link is disconnected and needs reconnecting, and the message clears once a later attempt succeeds.
• A trigger run that carried no event stops there. A push trigger you run by hand reports that it is waiting for a message and no longer hands an agent an empty turn to spend credits on. Branches that do not depend on that trigger still run.

Message is where you write an agent's standing instructions, and it is still required when nothing feeds the agent. When a trigger is wired into the agent, the event that arrives is the turn, so Message can be left empty and the node is no longer marked incomplete for it. Running such an agent by hand, with no event and no standing instructions, fails with an error saying so rather than running on nothing.

Moving an agent between Claude Code, Codex, OpenCode, OpenClaw, and Hermes used to end the thread it was on. Your next message started a new conversation with the recent turns pasted in as background. The conversation now moves into the harness you picked and carries on: the same thread, with each tool call still paired to what it returned, so the agent resumes where it left off rather than reading a summary of it.

• Any of the five CLI agents can hand a conversation to any of the others. The built-in LLM agent keeps its history in NoClick rather than in a session store of its own, so switching between it and a CLI agent still carries the recent turns across as context, about 4,000 characters of them, trimmed from the oldest end.
• Picking a thread in History now only opens it. It used to set the agent's Model to whatever that thread last ran on, changing the model you were about to run without telling you. The model stays the one you picked, and your next message runs it on the thread you opened.
• History rows no longer carry a tag naming the harness a thread ran on.
• The first message after a harness switch starts a new sandbox, so it takes longer than a follow-up. Messages after it are back to warm-sandbox speed.

A trigger wired into an agent used to hand it everything the service sent. A Slack message arrived as the whole delivery around it: verification tokens, authorization blocks, and a second copy of the text in Slack's own block format. The agent now reads a short account of what happened instead: the service and the kind of event, who it came from and where, the content itself, and the IDs it needs to reply in the right place.

• The triggers agents are usually wired to each write their own account of an event: Slack, Discord, Telegram, WhatsApp, inbound email, Gmail, Outlook, GitHub, GitLab, Linear, Jira, Notion, Trello, Asana, ClickUp, monday, Google Calendar, Forms, Sheets and Drive, Typeform, HubSpot, Shopify, Zendesk, Intercom, Stripe, Calendly, PagerDuty, Sentry, PostHog, Datadog, Honeycomb, Mailgun, Resend, Loops, schedules, and plain webhooks. Any other trigger gets the general shaping: the delivery wrapper opened, empty and internal fields dropped, and the rest held to a readable size.
• In the agent's chat, a turn that a trigger started is shown as the message that started it, laid out the way that app lays it out, under a caption naming the app, the node's label if you gave it one, and the trigger, for example Slack · Support channel · On app mention. Where a message view does not fit, such as a schedule tick, the account the agent read is shown with the event itself behind an Event payload toggle.
• The thread takes its name from the event, so the history list reads as the channel or the sender the message came from. Your standing instructions stay in the Message field, rather than appearing in the chat as a message you never sent.

A required field holding a reference like {{ $('trigger').chat_id }} used to be passed on as an empty value when the referenced output had no such key. The step reported success and nothing arrived. That field now fails the step, and the error names the field, the reference, and the keys the referenced node's output actually has, so you can fix it without opening the run.

• The error reads Required field 'to' is empty, followed by what went wrong: the referenced node has no key by that name, and the list of keys it does have. A key that exists but holds null is reported as null, which reads differently and usually means a different fix.
• A reference read during a manual run of a trigger that waits for events says there is no live event in this run, and that firing the workflow for real is how to test that path.
• Optional fields are unchanged. A reference that resolves to nothing there leaves the field at its default, as before.
• Sending a WhatsApp message to an empty recipient stops with a message naming the chat id to reference instead, rather than being accepted and never delivered.

Slack sends channel events only to apps that are members of the channel. A trigger on a channel NoClick was never invited to used to read Active and never fire. Registration now checks, and the trigger's Status field carries the verdict. When the app is not in the channel, the status turns amber and says so, with a Join #channel button next to it on a public channel. A private channel names the invite to run instead, since only a person can add an app to one.

• The node is marked incomplete on the canvas, counted by the incomplete pill at the bottom left, and named in the Setup tab. It never holds up a run you start yourself, because a manual run does not wait for Slack to deliver anything.
• Your Dashboard lists it under Needs you as not receiving events, with that same fix as the button on the row and Open trigger next to it. Open trigger now opens the workflow with the trigger selected and its settings showing.
• Ask the AI builder why a workflow is not running and it reads the same verdict, so it answers that the trigger is registered but not receiving events rather than calling it active.
• A check that cannot reach Slack changes nothing. A trigger is never called broken on a failed check.

Get Subreddit Posts reads Reddit directly now. Each post comes back with its full text and HTML, permalink, creation and edit times, score, total comment count, flair, media links, and the community's URL, description, and member count. It still needs no connected Reddit account, and it still runs on your credits.

• Set Fetch Comments to Yes for a sample of comments and their nested replies, sized by Comments per Post (1 to 100, 10 by default). num_comments stays the total Reddit reports for the post, and comment_count counts what actually came back.
• Time Period applies to top and controversial sorting on every read. Content Detail and Proxy Mode are gone, and steps you already saved keep running on the new reader.
• A read that fails or comes back incomplete fails the step, instead of reporting success with nothing in it.

A scheduled workflow that kept failing the same way used to mint another failed run on every tick, for as long as the schedule ran. NoClick now pauses it: when the last five runs from that schedule have all failed with an identical error, spread over at least 30 minutes, the trigger node is switched off and the schedule stops.

• You get one email naming the workflow, the paused trigger, the error, and when it was paused. Paused schedules is its own toggle in Settings → Notifications, and you get at most one of these per trigger per day.
• The paused trigger appears on your Dashboard under Needs you and on the Triggers card, named and marked as paused with the error next to it. A trigger you switched off yourself stays hidden, as before.
• Fix what the error names, then enable the trigger node again to resume the schedule. If the same failure comes back, the schedule pauses again on the first repeat.
• Running out of credits never pauses a schedule. Topping up resumes the runs on its own.
• A short provider outage does not reach the bar: the failures have to be identical and sustained for half an hour.

The Instagram node has two new triggers, On Comment and On Message. A comment someone leaves on the connected account's posts, or a direct message they send it, starts a run as it arrives. Both need the Login connection, and Instagram pushes each event to NoClick signed, so nothing is polled.

Leave the filters blank to listen across the whole account, set Media ID on On Comment to watch one post, or Sender ID on On Message to hear one sender. Comments the account wrote itself and echoes of messages it sent are skipped, so a reply your workflow posts cannot start it again. Running either step by hand reports that no event was delivered, because events reach the workflow through the trigger.

The connect status for a workflow that hosts an MCP server now answers two questions separately instead of showing one spinner for both. A Link ready line names how many tools the link serves right now, with a few of them by name, read straight from your workflow with no client involved. Under it, the client line reads Waiting for your agent to connect until a client calls in, then Connected with the client's name, how many tools it was served, and which ones it can call.

• The waiting line names what makes that client connect. Most clients only write the config when you run their add command and open the connection when a session starts, so the usual fix is to start or restart the client rather than to wait.
• After 45 seconds the panel offers that client's own check command, such as claude mcp list or opencode mcp list. Those commands list the servers and connect at the same time, so running one turns the status green.
• The status also sits on the node. The Connect externally header of an MCP Server node reads Connected, with the client and the tool count, for anyone who opens the workflow later, so you do not have to run the Setup finale again to check.
• When NoClick cannot read handshakes for a moment, the panel says it cannot check rather than reporting that nothing has connected. The link keeps serving either way.
• The client setup guides are re-verified. Claude's custom connectors live under Customize → Connectors, Zed connects to a remote URL without a bridge, and VS Code adds the server with code --add-mcp.

The Feed tab in the top navigation becomes Dashboard: one page for what is happening across your workspace, with a card for each area and a full page behind every card. Needs you replaces the approvals queue and now also carries questions the AI builder parked, edits an agent proposed to its own workflow, accounts someone still has to connect, connections that stopped working, and triggers that failed to register. You answer each one where it sits, with the same fields and pickers the workflow itself would show you.

The other cards are Runs, Agents, Upcoming, Files, Credentials, Triggers, Credits, and Notifications. Press G then D to open the Dashboard, or G then I to land on Needs you.

• Runs charts the last 14 days and lists your workflows by run count, with failures called out. Click a row to open that workflow, or a single run to see its results.
• Files gathers workflow uploads, agent workspaces, and the builder's scratch folder in one place, previews images, video, audio, and datasets without leaving the page, and lets you upload or delete wherever you have write access.
• Agents shows sandboxes that are up now and each agent's latest turns, with the message that came in, the messages the agent sent, and every tool call it made.
• The section you drilled into is remembered while you visit other tabs. The back button, browser Back, or Esc leaves it.

The Discord node has two new triggers, On Channel Message and On Bot Mention, and a message reaches your workflow within seconds of being posted. Connect Discord with the Discord Bot Install credential so NoClick's bot is in your server, then leave Channel empty to listen to the whole server or pick one channel. Ignore bot messages is on by default, so posts from other bots and webhooks do not wake the agent. Each channel and thread is its own conversation.

• A Discord message in run results reads as a message: who wrote it, the channel and server by name, mentions as names, and attachments by filename. A slash command reads as its invocation.
• A Test Run on a Discord-triggered agent ships a written Channel question situation, so the rehearsal looks like a real Discord message instead of a generic sample.
• An On Slash Command trigger fires only for the server its connection was installed into. A connection made with your own bot token still covers every server that bot is in.
• A Discord connection reads as disconnected once the bot is removed from its server, in the credential picker, in workflow validation, and to an agent asking about its own workflow, with reconnecting named as the fix.