Integrations
The Integrations page under Settings lists the external systems your team can connect to Strise. It shows the state of each one, and it is where you connect them. It has two sections:
- Business systems: CRMs that share companies with your Strise portfolio, such as HubSpot and Pipedrive.
- Data sources: the data Strise uses for your team. Some comes under your team's own contract, such as Orbis or SPAR. The rest comes under Strise's own agreements, such as company data from Brønnøysundregistrene or news from Opoint.
Each data source is named after the data it provides, with a label naming who provides it. Expand an entry to find a link to its documentation. Data sources are grouped by market (Norway, Sweden, Denmark, Finland, United Kingdom, Global), then Screening and Other.
Where to find it
Open Settings → Connections → Integrations. You see the tab if you have the View integrations permission, which the Team Admin role carries. Connecting, changing and disconnecting also need the Edit integrations and Delete integrations permissions, which Team Admin carries too. A user who can view integrations but not edit them sees the states and is asked to contact their Team Admin. See Roles and Permissions.
Integration states
Each integration carries one of four states:
| State | Meaning |
|---|---|
| Unavailable | Your plan does not include it. |
| Available | Your team can connect it, or Strise sets it up for you. |
| Connected | A login is stored, or the business system is connected, and Strise uses it. |
| Needs attention | The external system rejected your team's login. See Needs attention. |
Business systems are never marked Unavailable: a Team Admin can connect HubSpot or Pipedrive at any time.
When Strise turns off a feature that uses a data source, the data source shows Unavailable. If your team connected it, Strise stops using the login and keeps it, so the data source is Connected again when Strise turns the feature back on.
A data source marked Unavailable has a Contact Strise button that opens a chat with Strise support. When Strise moves an integration from Unavailable to Available, your Team Admins get an Integration unlocked notification. Integrations only Strise connects send none. See Email settings.
Expand a data source to see which features use it.
Who connects what
| Integration | Who connects it | What you enter |
|---|---|---|
| HubSpot | Your Team Admin | Sign in to HubSpot |
| Pipedrive | Your Team Admin | Sign in to Pipedrive |
| Orbis | Your Team Admin | API token |
| Enento Business Insight | Your Team Admin | Username and password |
| Creditsafe Norwegian individuals | Your Team Admin | Username and password |
| Asiakastieto | Your Team Admin | User ID (12 digits), password, checksum key |
| SPAR | Your Team Admin | End-customer number and assignment ID |
| Signicat | Strise | Nothing; Strise sets it up |
| Folkeregisteret | Strise | Nothing; Strise sets it up |
| Beneficial owners from Brreg | Strise | Nothing; Strise sets it up |
Your Team Admin can connect a data source only once Strise has unlocked it for your team. Asiakastieto and SPAR need steps with the data source first. Their entry on the Integrations page describes them:
- Asiakastieto: ask Asiakastieto for API access. They send you a user ID, a password, and a checksum key.
- SPAR: apply to SPAR for a permit that names Strise. SPAR then gives you an end-customer number and an assignment ID. Both are digits only.
For Signicat, Folkeregisteret and Beneficial owners from Brreg, your team arranges access with Signicat or the register, and Strise connects the integration. The Integrations page then shows the date Strise set it up.
Credit Data uses Strise's own Creditsafe agreement unless Strise sets up your team's own Creditsafe login for company credit data. That login does not appear on the Integrations page.
Data from Strise
The Data sources section also lists the data Strise provides under its own agreements. Your team has nothing to connect. An entry shows Connected when your team has the data and Unavailable when it does not. An entry marked Unavailable has a Contact Strise button.
| Data | Source |
|---|---|
| Norwegian company data | Brønnøysundregistrene |
| Swedish company data | Creditsafe, Valu8 |
| Danish company data | Det Centrale Virksomhedsregister |
| Finnish company data | Valu8, Patentti- ja rekisterihallitus |
| UK company data | Creditsafe |
| Global company and person data | Sayari |
| Live global company data | Sayari |
| Premium Norwegian media | Opoint |
| News and adverse media | Opoint |
| Registry documents | Kyckr |
| Norwegian real estate data | Kartverket |
| PEP and sanctions lists | Trapets |
| PEP and sanctions lists | Dow Jones |
Connecting a data source
- Expand the data source and enter the login.
- Select Connect data source, for example Connect Orbis.
Before saving, Strise checks the login with the data source, for every data source except Asiakastieto and SPAR. If the data source rejects the login, Strise shows its reason and saves nothing. If Strise cannot reach the data source, it saves nothing either; try again a few minutes later. Strise has no login check it can run against Asiakastieto or SPAR, so the form checks only that their numeric fields hold digits.
Strise never shows a stored secret, such as a password or API token, again. After saving, the form shows the date the secret was set instead. To change a login, enter the new values and select Save; leave a secret empty to keep the stored one. Only Strise can remove a stored data source login, so contact Strise to remove one.
Connecting a business system
Select Connect HubSpot or Connect Pipedrive and sign in to the CRM. Then choose the Organisation number field, the CRM field that holds each company's organisation number. Syncing starts once it is set. HubSpot also has a Tag field.
From the same entry you can import your portfolio from the CRM or export it to the CRM, and Disconnect it. Disconnecting stops Strise reading from and writing to the CRM. Your companies stay in Strise. See HubSpot integration for how syncing works.
Needs attention
An integration moves to Needs attention when the external system rejects your team's login. This happens, for example, after a password change or a revoked CRM connection. A timeout or an outage at the external system never causes it. The entry shows when the login was rejected and what to do:
| Integration | What to do |
|---|---|
| A data source your Team Admin connects | Enter a new login. |
| HubSpot or Pipedrive | Select Reconnect business system and sign in again to resume syncing. |
| Signicat, Folkeregisteret, BRREG | Nothing. Strise sees the rejection and is looking into it. |
The state clears when the external system next accepts the login, when the login is replaced, or when a business system is reconnected. Your Team Admins get one Integration needs attention notification the first time an integration enters the state. See Email settings.
Activity
The Activity Log records each business system connected or disconnected, each data source login set, replaced, or removed, and each change to the CRM field mappings. It never contains the login itself.
Last updated on