TL;DR: There is no URL to paste. A Slack admin installs the Noded for Slack app and allows its connected MCP server once; then each person opens a direct message with Slackbot, clicks Apps → + → Noded, and signs in with their Noded account. No client ID or secret - Slack registers itself with Noded automatically. Reads are read-only. Every write (an email, a message, a note, a CRM record, a workflow run) becomes a recommendation in Noded that you approve or dismiss.
What you need
- A Noded account with data connected. Slackbot can only find what Noded has synced. Connect at least one source (Gmail, Slack, a calendar, a call recorder, or a CRM) in the Noded app first.
- The same email in Slack and Noded. Slackbot signs you in to Noded with the email on your Slack profile, and Noded matches you to your account by that address. If they differ, ask your Noded admin to update one of them before you start.
- The AI-powered Slackbot. Adding apps to Slackbot is only available on Slack plans with Slack AI. The sign to look for is an Apps button in the Slackbot message composer; if it is missing, ask your Slack admin whether Slack AI is enabled for the workspace. See Slack’s Slackbot MCP client documentation for the current details.
- The Noded for Slack app, installed and approved. Slackbot only uses MCP servers that an installed Slack app declares, and Noded’s is declared by the Noded for Slack app (it appears in Slack simply as Noded). A Slack admin installs it and allows its connected MCP server once; the steps are below.
You do not need the server URL, a client ID, or a secret. Slack discovers Noded’s sign-in service from the app’s declaration and registers itself automatically, the same way Claude and ChatGPT do.
Who can set this up?
| Role | What they do |
|---|---|
| Slack workspace or org admin | Installs the Noded for Slack app and allows its connected MCP server, once per workspace (or once per organization on Enterprise Grid). Until this is done, Noded does not appear in Slackbot’s Apps list for anyone. Slack shows the admin the Noded domain before they approve, and they can revoke access for the whole workspace at any time. |
| Each person | Adds Noded to their own Slackbot and signs in, once. Slack keeps a token per person, so everyone sees only their own Noded data. Slackbot allows up to five connected apps per person. |
| Noded admin | Makes sure everyone who will connect has a Noded account under the same email as their Slack profile. Nothing to configure on the Noded side beyond that. |
In short: an admin spends five minutes on the app once, and after that every person self-serves over a coffee. If your workspace already runs Noded for Slack, the admin step is a single checkbox.
Using another assistant? See the guides for Claude, ChatGPT, Gemini, and Microsoft Copilot Studio.
Install Noded for Slack and allow the MCP server (admin, once)
Skip to step 3 if the Noded for Slack app is already installed in your workspace.
1️⃣ Open the installation link. Your Noded contact gives you an installation link for the Noded for Slack app; if you do not have one, ask us. Slack lists the permissions the app requests - reading messages in channels it is invited to, posting messages, reading profiles so Noded can match people to their accounts, link previews, canvases, and searching public channels for context. Nothing in a private channel is read unless the app is invited to it.
2️⃣ Click Allow. The app appears in your workspace’s Apps list. On Enterprise Grid, install at the organization level so Slackbot can use it in every workspace.
3️⃣ Allow the connected MCP server. In Slack’s admin settings, open Integrations → Installed apps and select Noded. Under Connected MCP Servers, tick Allow next to Noded. Slack shows the Noded domain on this screen; that is what you are approving. Until it is allowed, Noded does not appear in Slackbot for anyone.
That is the whole admin step. No URL, scopes, or credentials to enter: Slack reads Noded’s sign-in configuration from the app’s declaration and registers itself as a client automatically.
Connect Noded in Slackbot (each person, once)
1️⃣ Open a direct message with Slackbot. Press Cmd+K (Ctrl+K on Windows), type Slackbot and pick it, or find it under Agents & tools → All agents in the sidebar.
2️⃣ Add the app. Click Apps in the message composer toolbar (the row with the formatting buttons), then +, and choose Noded. If Noded is not in the list, your admin has not completed the step above. If there is no Apps button at all, your workspace does not have the AI-powered Slackbot yet.
3️⃣ Sign in to Noded. A Noded sign-in window opens. Use the same email address as your Noded account, then approve the requested access. The consent screen lists read access to your customer context and the ability to create recommendations for you to review.
4️⃣ Check the tools. Back in Slack, ask Slackbot: “What tools are available from Noded?” You should see searching your knowledge, drafting emails and messages, drafting notes, running workflows, creating records, and searching connected apps.
5️⃣ Test with a read. Ask: “Using Noded, what can Noded do?” Slackbot calls Noded and lists the built-in actions plus the searches, workflows, and record types installed for your account. Then try “Using Noded, when did we last talk to Acme, and is anyone waiting on a reply from us?”
Say “using Noded”
Slackbot can answer from several sources, so mention Noded in the request when you want Noded’s knowledge: “Using Noded, …” or “Ask Noded to …”. If Slackbot answers from general knowledge or from Slack alone, that is usually the fix.
Approving tool calls
The first time Slackbot wants to use a Noded tool it asks you, with three choices: Allow once runs it this time only, Always allow stops asking for that tool, and Deny blocks it. Always allow is safe for Noded: every tool that writes anything creates a recommendation for you to review in Noded, so nothing is sent, saved, created, or run by the tool call itself. You can change these choices later from the same Apps menu in Slackbot.
What Slackbot can do with Noded
Noded exposes one server with a small set of capability groups. You never need the tool names; describe what you want and Slackbot picks the right one.
| Group | What it does | Example prompt |
|---|---|---|
| Find people and accounts | Resolves a name or company to the right contact or account, lists related people (buying committee, who else is involved), and reads your saved folders such as My Accounts. | “Using Noded, who else at Acme has been on our calls?” |
| Read activity | Emails, chat messages, meetings and transcriptions, notes, tasks, and saved CRM or support records - filtered by person, account, date, direction, or status. Semantic search finds themes when exact filters are not enough. | “Using Noded, what did we last discuss with Acme?” |
| Check engagement | Per-account activity across every channel in one call, and unanswered emails - who is waiting on you, and who has gone quiet. | “Ask Noded what’s open with Jane at Acme.” |
| Search connected apps | Read-only live lookups in the apps you have connected (Salesforce, HubSpot, Zendesk, Jira, Linear, and others) using the searches installed for your account. | “Find open Zendesk tickets for Acme in Noded.” |
| Draft and act | Draft an email, a Slack or Teams message, or a note; create a record in a connected system (a Jira issue, a Salesforce case, a HubSpot record); or run one of your installed workflows. Each one arrives in Noded as a recommendation to review. | “Ask Noded to draft a follow-up email to Jane at Acme about next steps.” |
| Dates | Helpers for the current time, relative dates, and date arithmetic so questions such as “in the last 10 days” resolve correctly. | “Using Noded, how many days until the Acme renewal?” |
The exact list of searches, workflows, and record types is specific to your account. It depends on which apps you have connected in Noded and which queries and functions your team has installed. Ask “What can Noded do?” at any time to see the current list. The complete tool-by-tool list of what the server exposes, with the permission and review rules behind each one, is in the MCP server reference.
How the review step works
Noded separates reading from writing. All the read tools are read-only. Every write goes through a recommendation:
1️⃣ Slackbot proposes. When you ask for an email, a message, a note, a record, or a workflow run, Slackbot composes the proposal and asks Noded to create a recommendation. Nothing is sent, saved, created, or run at this point.
2️⃣ You review it in Noded. Slackbot replies with a link to the recommendation. Open it, or open Noded and look under Recommendations: the recipients, the subject and body, the record fields, or the workflow inputs are all there, and you can edit the text before you decide. If the draft relates to a Slack conversation the Noded app is part of, it also appears in that thread as a card with the same buttons.
3️⃣ Approve or dismiss. Approve accepts the recommendation with your edits, and Noded carries it out through the connected system. Dismiss discards it. Workflow runs notify you in Noded when they finish, and in Slack if you have Noded notifications turned on.
This is the one place Slackbot differs from the other assistants: the review happens in Noded (or on a Noded card in the Slack thread), not inside the Slackbot conversation itself. The same recommendations are visible to a teammate with access, so they can review them too.
Slackbot or the Noded app in Slack?
Noded in Slackbot is separate from the Noded app’s own messages tab and @mentions in Slack. Both work with the same Noded account and the same permissions; use whichever fits the moment. Slackbot is handy when you are already asking Slackbot other things and want Noded’s knowledge in the same conversation. The Noded app is the fuller surface - answers stream in with their sources, recommendation cards can be completed in the thread, links to Noded unfurl, and its Ask Noded and Post a Noded overview steps can be added to any Slack workflow. Ask a question in one and the recommendations it produces show up in the other.
Permissions and data handling
- Noded runs as you. Slackbot sees only what your Noded user can see. Tenant boundaries and sharing permissions are the same as in the Noded app.
- Sign-in is OAuth 2.1 with PKCE, brokered by Slack. Slack never holds your Noded password and neither does Slackbot. The token is scoped to reading your customer context and creating recommendations, and it is stored in Slack’s credential store for you alone.
- Admins stay in control. Your Slack admin sees the Noded domain before approving the server and can revoke access for the whole workspace from the same Installed apps screen.
- Disconnect at any time. Open the Apps menu in Slackbot, find Noded and remove it. Your Noded account is not affected; only Slackbot’s access to it ends. Reconnect any time with the steps above.
- Nothing new is stored in Slack by Noded. Query results are returned to the Slackbot conversation you are in and are governed by your Slack plan’s data policy.
Troubleshooting
- Noded is not in Slackbot’s Apps list. Your Slack admin has not installed the Noded for Slack app, or has not allowed its connected MCP server under Integrations → Installed apps. Both are needed.
- There is no Apps button in the Slackbot composer. Your workspace does not have the AI-powered Slackbot. Ask your Slack admin whether Slack AI is enabled.
- Sign-in fails or says the account was not found. The email on your Slack profile does not match a Noded account. Ask your Noded admin to create the account or update the email, then remove Noded from Slackbot’s Apps menu and add it again.
- Slackbot answers without using Noded. Say “using Noded” or “ask Noded” in the request.
- Slackbot finds nothing for an account you know is active. Check that the source (email, calendar, Slack, call recorder, CRM) is connected in Noded and has finished its first sync.
- Slackbot says the tool timed out. Slack allows 60 seconds per tool call. Try again; if it keeps happening for one request, ask the same question in the Noded app and tell us which request it was.
- A draft is missing from Noded. Check Recommendations in Noded, including dismissed items. If it is not there, tell us the time of the request.
FAQ
Do I need an admin to set this up?
Yes, once. A Slack admin installs the Noded for Slack app and allows its connected MCP server. After that, every person adds Noded to their own Slackbot and signs in to their own Noded account. See who can set this up.
Do I need to paste a server URL, client ID, or secret?
No. Slackbot only uses MCP servers that an installed Slack app declares, and the Noded for Slack app declares Noded’s. Slack reads Noded’s sign-in configuration from that declaration and registers itself automatically (dynamic client registration), so there is nothing to type. Claude, ChatGPT, Microsoft Copilot Studio and the Gemini CLI register the same way; only Gemini Enterprise needs a client ID and secret from Noded.
Can Slackbot send an email or create a record through Noded without asking me?
No. Every write becomes a recommendation in Noded. Nothing is sent, saved, created, or run until you approve it there - which is also why “Always allow” is safe when Slackbot asks about a Noded tool.
What data can Slackbot see?
Only the data the signed-in Noded user can already see in Noded, under the same tenant and sharing permissions.
Do I also need to connect Slack inside Noded?
Not for Slackbot. Slackbot signs you in to Noded directly. Connecting Slack under Apps in the Noded app is what powers the Noded app’s own answers in Slack, recommendation cards and link previews, and what lets Noded read the Slack threads you track - so most teams do both.
Does the same Noded server work with Claude, ChatGPT, Gemini, and Microsoft Copilot?
Yes. It is the same server behind the Claude, ChatGPT, Gemini, and Microsoft Copilot Studio guides; Slackbot is simply the one host where the Slack app carries the address for you. See our guide to MCP for customer teams for the wider picture.