Integrations

Bring the knowledge in. Put it to work.

Bring in the Notion policy or the resolved Jira issue. Review the useful knowledge, then let your AI team and compatible external agents use the same sources.

Join the waitlistSee it in practice

Mac-only for now. Free during the beta (invite-only).

Three practical connection paths

Use company knowledge where the work needs it.

Choose a source connection, give a compatible agent scoped MCP access, or supply an excerpt from a tool without a native connector.

Native source connections

Bring the policy and the resolution into the same review.

  1. The existing sources

    Connect the Notion guidance and resolved Jira issue that explain how your team handled the access problem.

  2. Draft knowledge

    Them AI extracts proposed memory records from the source text for your team to review.

  3. A useful answer next time

    After approval, a teammate with access to those records can use the workaround and its source when the same question returns.

See how memory is reviewed
NotionJira
Them AI Prepared for review
Proposed guidance

Use the documented workaround while the service owner confirms whether the underlying issue is resolved.

Your team decides the next step

Notion imports readable pages shared with its integration. Jira imports work-item descriptions, resolved by default; imported knowledge starts as drafts.

Knowledge-only MCP access

Give your support agent a company answer it can cite.

  1. Choose what the agent can use

    Create a knowledge-only key for a compatible support agent and choose which approved records and shared skills it may retrieve.

  2. A source-backed answer

    The agent requests relevant policy records or a cited answer from Them AI while handling work in its own environment.

  3. Context without room writes

    The agent receives approved knowledge without permission to read room conversations, post, or invoke a teammate through that key.

Explore support-agent context
ClaudeMCP
Them AI Prepared for review
Retrieved context

The approved policy and its supporting source are available for the agent’s reply draft.

Your team decides the next step

Use a compatible client such as Claude Code with a bearer-key MCP connection. The key supplies company context, not access to your CRM.

Supplied notes and excerpts

Start with the order question you already have.

  1. The selected material

    Provide a sanitized ticket excerpt and the relevant order-status notes rather than an entire customer account.

  2. A prepared reply

    Your AI teammate uses approved guidance to draft the explanation and identify the live order checks still needed.

  3. A person checks and sends

    The support teammate verifies current details in the store and sends the final response through the help desk.

Explore ecommerce
ShopifyGorgias
Them AI Prepared for review
Next-step draft

Confirm whether inspection is complete before explaining the next refund step to the customer.

Your team decides the next step

Shopify and Gorgias are source-material examples, not native Them AI connections. A person provides the relevant notes or excerpts.

Inside Integrations

Two directions. Clear boundaries.

Bring knowledge in

Start with the source of the answer.

Bring in files and URLs, or connect Notion, Confluence, GitHub, Jira and Linear. Review contributed knowledge before treating it as company guidance.

File upload in the Them AI knowledge-source picker

Choose the source material for your company knowledge.01 / 03

Connect external agents

The same knowledge, beyond one app.

Use MCP to give a compatible agent its own key and access settings. A knowledge-only key retrieves approved context without reading room conversations or posting.

Setting up an external agent with knowledge-only access

An external connection with its own access settings.02 / 03

Review what comes back

Keep a person at the decision.

Choose retrieval and posting access when creating a key. Review contributed work separately before it becomes approved memory or a skill.

The review status and owner of a draft company record

New company guidance starts with human review.03 / 03

Explore the full task

Engineering

Explain a retry path

Sources, review and next steps Customer support

A subscription billing handoff

Sources, review and next steps Consulting

Workshop to design brief

Sources, review and next steps

A few things worth knowing.

Are Slack and Teams room bridges available?
Not yet. Planned bridges would let one Them AI room connect to several Slack or Teams destinations, with sharing choices for each connection.
Does Them AI update Salesforce or store orders?
Not directly. Bring relevant CRM or order notes into Them AI to prepare the work, then check current details and make the final update in your existing tool. MCP connects compatible external agents to company knowledge, not to a CRM or store account.
What is MCP?
Model Context Protocol is a way for compatible AI tools to request context from another service. Them AI uses it to provide approved memory and shared skills through a connection with its own key and access settings.
Can I restrict an external agent’s access?
Yes. Give each connection its own key and retrieval scope. A client-scoped feed retrieves that client’s approved knowledge plus approved shared company records, excluding other clients. Choose knowledge-only access when the agent does not need room tools.
What changes with workspace access?
A workspace-access key can use room tools within its permitted scope, including reading conversations that have not been approved as company memory. Room access is separate from approval of memory and skills.

Bring one real workflow

Try it on work your team already does.

Choose one recurring question, bring the source material, and name the person who will review the answer. Start there, then decide what is worth repeating.

Mac-only for now. Free during the beta (invite-only). Have a workflow in mind? Plan a pilot with us.