Connect an AI assistant to your CRM

Forbind AI exposes your CRM to an external AI assistant over MCP, the standard connectors use. The assistant can then work with your records directly, in its own chat window, rather than you copying things back and forth.

Connecting Claude:

1. 1Open Forbind AI and start the Claude connection. Vi kopierede din MCP-URL til udklipsholderen.
2. 2I Claude klikker du på "Tilføj brugerdefineret forbindelse" og indsætter URL'en.
3. 3Godkend adgang, når du sendes tilbage hertil — din app vises derefter under Tilsluttede apps nedenfor.

Each connected app is then listed with Tilsluttet and Sidst brugt {{time}}, and can be disconnected from there. Manuel opsætning gives you the URL to paste into any other client that speaks MCP.

What it can do is decided by the permissions granted when the app was connected — the same scopes as an API key, so an assistant can be read-only if that is what you want: Nøglen blev oprettet, da nogen forbandt en ekstern app, og tilladelserne er dem, vedkommende godkendte dengang. Ændrer du dem her, ændrer du, hvad appen må, uden at spørge igen. See Create and manage API keys.

Start read-only. An assistant that can answer "which deals slipped this month" is immediately useful and cannot break anything. Grant write access once you trust what it does with the read access.

Getting reliable answers: ask the assistant to find the customer or deal first, then read that record's notes. Text search returns a limited set of matches; a company name missing from a note does not mean the customer has no notes. Notes from another record must never be treated as that customer's history. Summaries include plain text, note type and the author's name when the author is available in your workspace.

Lists start with compact pages. The assistant can open a record for its full details, request selected fields, and follow the next page until there are no more records. Order history can also be paged through. Invalid inputs identify the field to correct; an unavailable record is reported separately. Counts and totals by seller can be calculated on the server. Money totals require a single currency and permission to see those amounts.

The connection can read support cases, including their conversations when requested. A service job or project mentioned in a note still needs to be opened in DealJourney; the connection advertises which parent types it can read and which it can summarize. Import field discovery is paged and can be limited to the entity and fields you need; duplicate previews accept rows with company or contact matching details before any import is executed.

Reading retention reports: the first-subscription cohort and its starting MRR include subscriptions waiting for approval. Retained customers and MRR require an active subscription. A low initial percentage can therefore include pending approvals and does not by itself prove churn. These reports use current statuses and prices with subscription start/end dates, rather than reconstructing every historical change. MRR is converted to the workspace's base currency using current exchange rates; missing rates are reported as excluded amounts.

Everything it does is logged, and much of it can be undone: See what an external AI assistant did. Check that page in the first week — it is the fastest way to see what an assistant actually does versus what you assumed.

This is not Dealy. Dealy is built into DealJourney and answers inside the app: Dealy, the assistant. This connection is for using your CRM from an assistant you already work in.

Treat the connection like a key. Anyone who can drive that assistant can drive your CRM through it, within its scopes. Disconnect apps you no longer use, and check Sidst brugt {{time}} occasionally.