Skip to main content
Book a demo
ProductsServicesMaps and data
“Placepoint is our main platform for property information. In practice, we only use Placepoint now.”
Petter CedellGroup Director of Property Investments, Selvaag Bolig
“We see a clear efficiency gain with Placepoint, as much of the information we need on ownership, ownership structures, zoning purposes and encumbrances is gathered in one place. Several of us in the organisation use the tool daily and get a lot out of it.”
Kristian AkslandPartner, CMS Kluge

Why Placepoint

The company

“We have 25 salespeople using Placepoint every day to generate leads and find tenants.”
Henning BjørnsgårdHead of Sales and Development, EIR
“We use Placepoint daily for credit work. Among other things, we can identify ownership concentration in business parks.”
Lars Kristian TveterSenior Relationship Manager, Danske Bank

Connect the Agent to other systems

This page explains what you need for each connection, where to find the values at the vendor, and how to add the connection in Placepoint Fusion. What the Agent does with the connections is described under Connections to other systems.

Before you start​

  • Only an administrator in the organisation can add or remove a connection. Other users can see who the administrators are under Agent in Settings.
  • Everyone in the organisation who has the Agent uses the connection with the access of the account that connected it. Use a separate user or service account with read-only access where the vendor offers it, so the Agent only sees what it should.
  • The Agent reads through the connections. Where the vendor has tools that change data, we have turned them off, or the vendor asks for confirmation before anything is changed.
  • Keys and tokens are stored encrypted. To remove a connection, select Disconnect on the same page.

How to add a connection​

  1. Open Settings and select Agent.
  2. Under Connections, select Add connection.
  3. Select the system under Connection, and give the connection a name under Name. Users see this name in the Agent.
  4. Complete the setup in one of two ways, depending on the system:
    • Log in at the vendor. Select Connect with and the vendor's name. You log in and approve at the vendor, then return to Settings. Nothing is saved until the vendor has confirmed.
    • Keys from the vendor. Paste the values into the fields, select Test the connection, then Connect.
  5. When you see “Connected. Agent can use the connection from the next question.”, the connection is ready.
ConnectionHow to connect
Fenistra, FDVweb, EG Facilit, Xledger, Scrive, Signicat, Visma.net, CoreKeys from the vendor
SagaServer URL and API key
Notion, Tripletex, HubSpot, SuperOffice, Fazile, PropelyLog in at the vendor
Custom connectionServer URL and bearer token

Fenistra​

You need two values from Fenistra:

  • API subscription key: created when you register a user in Fenistra's developer portal. The link to the portal is on Fenistra's Integrations and API page.
  • Licence GUID: identifies your licence. If you do not have it, ask Fenistra for it through their contact page.

Neither value expires.

FDVweb​

You need an API client ID and an API client secret from FDVweb, and your FDVweb subdomain: the name before .fdvweb.no in the address you log in at. You get the client ID and secret from your account manager at FDVweb. See Integrations and the contact page at FDVweb.

EG Facilit​

You need an API client ID and an API client secret that EG creates for your FDVU (facility management) installation. Ask EG Facilit for an API client at support@facilit.no. The services the client gives access to are listed in the API documentation for FDVU.

Xledger​

You need an API token with read-only access:

  1. An administrator in Xledger logs in and opens www.xledger.net/f/api-tokens.
  2. Create a new token for Placepoint, and give it read-only access.
  3. Copy the token and paste it into Settings.

Send questions about tokens to Xledger support.

Scrive​

You need the personal access credentials from a Scrive account: Client identifier, Client secret, Token identifier and Token secret.

  1. Log in to Scrive and go to Settings, then Integration Settings.
  2. Create Personal access credentials. If they already exist, you must delete them and create new ones.
  3. Paste the four values, and enter https://scrive.com under Scrive server. For the test environment, use https://api-testbed.scrive.com.

Each Scrive user has one set of credentials, so consider using a separate user for Placepoint. See Authentication and the API documentation at Scrive.

Signicat​

You need an API client ID and an API client secret from an API client in Signicat Dashboard:

  1. Go to Settings, then API clients, and select Add client.
  2. Give the client the scope signicat-api.
  3. Create a secret under the client's details. It is shown only once, so copy it straight away.

See Quick start guide for Signicat APIs.

Visma.net​

You need a Client ID and a Client secret for an application in Visma Developer Portal, and the company's tenant ID in Visma.

  1. Register an application of the type service integration in Visma Developer Portal, with the scope vismanet_erp_service_api:read. This gives read-only access.
  2. A Visma administrator in the company approves the application for the company. Without approval, Visma does not accept the tenant ID.
  3. Paste the client ID, secret and the company's tenant ID.

See Service Integrations and Application registration at Visma.

Notion​

Select Connect with Notion, log in and approve. The Agent reads the same pages as the account that connects. On the Enterprise plan, the Notion administrator can control which MCP clients are allowed. See Connect AI tools with Notion MCP.

Tripletex​

  1. An administrator in Tripletex activates Tripletex MCP Beta under My subscription. Without this, the login fails.
  2. Select Connect with Tripletex, log in and approve.

The Agent gets access to what the connecting account has access to. See Tripletex MCP and AI and MCP at Tripletex.

HubSpot​

Select Connect with HubSpot, log in and approve. A Super Admin in HubSpot can connect straight away. Other users need a Super Admin to approve first.

  • The Agent reads what the connecting user can read, and changes nothing.
  • With Sensitive Data turned on in HubSpot, activities such as calls, emails, meetings, notes and tasks are not available, and neither are conversations from the inbox.
  • If HubSpot adds new objects to the connection, connect again to give access to them.

See HubSpot MCP Server.

SuperOffice​

Select Connect with SuperOffice and log in with your SuperOffice account. No API key is needed. The Agent reads, and this requires SuperOffice CRM Suite Plus or higher. See MCP Connect at SuperOffice.

Fazile​

Select Connect with Fazile, log in and approve. The Agent gets access to what the connecting account has access to. See Integration and API at Fazile.

Propely​

Select Connect with Propely, log in and approve. Propely's MCP is included for all active Propely users and gives read-only access. See Propely MCP.

Saga​

  1. In Saga, go to Settings, then API key management.
  2. Copy MCP Server Endpoint. Each firm has its own address, in the form https://<firma>.sagalegal.io/api/mcp.
  3. Create an API key.
  4. Paste the address under Server URL and the key under API key from Saga.

The Agent reads what the owner of the key can read, and does not start any workflows. See Developer setup at Saga.

Core​

Core from Broker AS requires an API agreement between the chain and Broker AS. You need:

  • API client ID and API client secret for the API client that Broker AS gives you in the API agreement.
  • Core environment: the name before .webtopsolutions.com in the address you use.

Ask Broker AS for an API agreement at api@broker.no. The chain management approves what the client can read. See API access Core at Broker AS.

Custom connection​

A custom connection is an MCP server that your organisation runs itself. You need the server's address under Server URL (it must start with https) and a Bearer token. Select Test the connection before you save. When the test succeeds, you see how many tools the server has.

The connection is marked “Not verified by Placepoint”, because it receives everything the conversation touches. Only connect to servers you control yourselves. See Connect to remote MCP Servers.

When the connection does not work​

MessageWhat to do
“Could not connect.”Check the values. Technical detail shows the server's own reason.
“The server did not accept this URL and login information.”Check the address and the key, and try again.
“This URL cannot be used for this connection.”Copy the address exactly as the vendor shows it.
“The vendor did not approve the connection.”You cancelled, or the account lacks permissions at the vendor.
“The connection was not completed.”Try again within ten minutes of starting.

If you are still stuck, contact us and tell us which connection it concerns and which message you see.

Sist oppdatert
These pages are generated automatically and may contain errors.This applies to screenshots and videos in particular. See About these help pages. Let us know through "Did you find what you were looking for?" at the bottom of the page, the chat at bottom right or support@placepoint.no.