Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Intercom Internal Knowledge (BYOK) icon

Intercom Internal Knowledge (BYOK)

Read your Intercom internal articles and the external pages imported for AI answers (titles, locales, dates, links; no bodies) with your own access token (US region)

Unify Dynamics LLC

Tools5read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderIntercom Internal Knowledgeunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which internal articles does our Intercom team have?
Tools called
list_internal_articles
When was internal article 39 last updated in Intercom?
Tools called
get_internal_article
Search our Intercom internal articles in folder 12
Tools called
search_internal_articles
Which external pages feed our Intercom AI answers?
Tools called
list_external_pages
When was external page 19 last ingested by Intercom?
Tools called
get_external_page

About

Intercom Internal Knowledge (BYOK) lets an AI assistant read your own Intercom Internal Knowledge data through the Intercom Internal Knowledge API with a key you supply (Intercom access token (US-hosted workspace)). Read-only: 5 tools (list_internal_articles, get_internal_article, search_internal_articles, list_external_pages, get_external_page). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.intercom.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Intercom Internal Knowledge. Intercom Internal Knowledge and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Intercom Internal Knowledge API (api.intercom.io) with a BYOK key; documentation: https://developers.intercom.com/docs/references/rest-api/api.intercom.io/internal-articles/listinternalarticles. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

5 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data5 tools
  • List internal articlesList the workspace's internal articles (team-only knowledge) with title, locale, owner and author ids and dates.
  • Get internal articleGet one internal article by id: title, locale, owner and author ids and dates (body left out).
  • Search internal articlesSearch internal articles, optionally inside one folder.
  • List external pagesList external pages imported into Intercom for AI answers, with title, source link, locale, which AI features may use each page and when it was…
  • Get external pageGet one imported external page by id: title, source link, locale, AI availability flags and ingest dates (HTML left out).

Information

PublisherUnify Dynamics LLC
CategoryWork & productivity
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-intercom-internal-knowledge.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 5 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-intercom-internal-knowledge.connectorbay.com/mcp
RESTPOST https://byok-intercom-internal-knowledge.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-intercom-internal-knowledge.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Intercom access token (US-hosted workspace) in the X-Upstream-Key header (get one at developers.intercom.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Intercom Internal Knowledge connector: questions and answers

What is the Intercom Internal Knowledge connector?

Intercom Internal Knowledge (BYOK) lets an AI assistant read your own Intercom Internal Knowledge data through the Intercom Internal Knowledge API… It is a hosted MCP server with 5 tools such as List internal articles, Get internal article, Search internal articles, List external pages, Get external page, published by Unify Dynamics LLC. It is independent and not affiliated with Intercom Internal Knowledge.

How do I connect Intercom Internal Knowledge to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-intercom-internal-knowledge.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-intercom-internal-knowledge.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-intercom-internal-knowledge.json.

Do I need a Intercom Internal Knowledge account or API key?

Yes: this is a bring-your-own-key connector. Create a Intercom access token (US-hosted workspace) at https://developers.intercom.com/docs/build-an-integration/learn-more/authentication and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Intercom Internal Knowledge read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Intercom Internal Knowledge connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Brella (BYOK)

Read your Brella event-networking data: events, schedule sessions, tracks, sponsors, ticket types, announcements and event, ticket-sales and session analytics with your own organization token

Live · MCP + REST12 tools

Brevo (BYOK)

Read your Brevo account, contacts, lists, segments, email campaigns and their statistics, senders and templates with BYOK

Live · MCP + REST8 tools

Brevo Setup (BYOK)

Read your Brevo sending domain authentication status, dedicated IPs, webhooks, contact attribute definitions, folders and consent groups with your own API key (no contacts)

Live · MCP + REST8 tools

Brevo SMS and WhatsApp (BYOK)

Read your Brevo SMS campaigns, WhatsApp campaigns and templates, WhatsApp account status and transactional SMS aggregate reports with your own API key (no recipients or message text)

Live · MCP + REST9 tools

Buffer (BYOK)

Read your Buffer organizations, connected social channels, sent, scheduled and draft posts, tags and post performance metrics through the GraphQL API with your own API key

Live · MCP + REST10 tools

Buildium (BYOK)

Read your Buildium rental properties, units, leases, tenants, balances, work orders, tasks, vendors, owners and bills with your own API key

Live · MCP + REST12 tools

Documentation

Back to top

Intercom Internal Knowledge (BYOK) — connector documentation

  • MCP endpoint: https://byok-intercom-internal-knowledge.connectorbay.com/mcp
  • REST API: POST https://byok-intercom-internal-knowledge.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-intercom-internal-knowledge.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Intercom Internal Knowledge Intercom access token (US-hosted workspace), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-intercom-internal-knowledge.connectorbay.com/health · Tool schemas: https://byok-intercom-internal-knowledge.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-intercom-internal-knowledge · agent@connectorbay.com

What Intercom Internal Knowledge (BYOK) is for

Intercom Internal Knowledge (BYOK) lets an AI assistant read your own Intercom Internal Knowledge data through the Intercom Internal Knowledge API with a key you supply (Intercom access token (US-hosted workspace)). Read-only: 5 tools (list_internal_articles, get_internal_article, search_internal_articles, list_external_pages, get_external_page). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.intercom.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Intercom Internal Knowledge. Intercom Internal Knowledge and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which internal articles does our Intercom team have?"
  • "When was internal article 39 last updated in Intercom?"
  • "Search our Intercom internal articles in folder 12"
  • "Which external pages feed our Intercom AI answers?"
  • "When was external page 19 last ingested by Intercom?"

What it does

  • list_internal_articles: List the workspace's internal articles (team-only knowledge) with title, locale, owner and author ids and dates. Article bodies are not returned.
  • get_internal_article: Get one internal article by id: title, locale, owner and author ids and dates (body left out).
  • search_internal_articles: Search internal articles, optionally inside one folder. Returns the matching articles as Intercom stores them (wrapped under data.internal_articles); long bodies may be shortened.
  • list_external_pages: List external pages imported into Intercom for AI answers, with title, source link, locale, which AI features may use each page and when it was last ingested. Page HTML is not returned.
  • get_external_page: Get one imported external page by id: title, source link, locale, AI availability flags and ingest dates (HTML left out).

BYOK key

You bring your own Intercom Internal Knowledge Intercom access token (US-hosted workspace) (https://developers.intercom.com/docs/build-an-integration/learn-more/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.intercom.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Intercom Internal Knowledge API (api.intercom.io) with a BYOK key; documentation: https://developers.intercom.com/docs/references/rest-api/api.intercom.io/internal-articles/listinternalarticles. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Intercom Internal Knowledge. Intercom Internal Knowledge and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Intercom Internal Knowledge account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Intercom Internal Knowledge (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Intercom Internal Knowledge (BYOK) is. Intercom Internal Knowledge (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Intercom Internal Knowledge data: Read your Intercom internal articles and the external pages imported for AI answers (titles, locales, dates, links; no bodies) with your own access token (US region). You bring your own Intercom Internal Knowledge Intercom access token (US-hosted workspace); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Intercom Internal Knowledge call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.intercom.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Intercom Internal Knowledge rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Intercom Internal Knowledge receives. The request we make on your behalf, including the key and the arguments, under Intercom Internal Knowledge's own terms and privacy policy. Intercom Internal Knowledge acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Intercom Internal Knowledge gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Intercom Internal Knowledge data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Intercom Internal Knowledge (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Intercom Internal Knowledge at any time to end all access.

Children. Intercom Internal Knowledge (BYOK) is a general-audience service operated by the adult using the assistant, under Intercom Internal Knowledge's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Intercom Internal Knowledge (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Intercom Internal Knowledge (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Intercom Internal Knowledge (BYOK) provides: Read your Intercom internal articles and the external pages imported for AI answers (titles, locales, dates, links; no bodies) with your own access token (US region). It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Intercom Internal Knowledge credentials and only access data you are allowed to access. Intercom Internal Knowledge's terms apply to your use of Intercom Internal Knowledge; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Intercom Internal Knowledge. Intercom Internal Knowledge and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Intercom Internal Knowledge returns, lightly trimmed; it may be incomplete, delayed or changed by Intercom Internal Knowledge. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Intercom Internal Knowledge account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Intercom Internal Knowledge's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Intercom Internal Knowledge may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Intercom Internal Knowledge key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Intercom Internal Knowledge takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-intercom-internal-knowledge

Intercom Internal Knowledge (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Intercom Internal Knowledge (BYOK) never asks for them.

Get Intercom Internal Knowledge (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Intercom Internal Knowledge Intercom access token (US-hosted workspace). Create one at https://developers.intercom.com/docs/build-an-integration/learn-more/authentication, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Intercom Internal Knowledge. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Intercom Internal Knowledge.