Managing Integrations
Enable, disable and manage integrations for any StackOne Project
The Integrations section of the StackOne dashboard allows you to manage integration (aka provider) for a StackOne Project.
On the integrations page, you can:
- View the list of all integrations for all the categories supported by StackOne (eg.
HRISATSIAMCRMMarketingandLMS. Some integrations and categories are only available based on your plan/contract. If you do not see a category or integration that you would like, contact support manager - Enable, configure and disable integrations.
- Quickly **access **linked accounts and logs related to the integrations
Integrations Listing
Enabling and disabling integrations
Setting up an integration for the first time confirm will automatically set its state as enabled, meaning it will be displayed in the Integrations Hub and you will be able to retrieve Connect Sessions token with the associated provider key.
When disabling an integration by toggling the radio button, a warning will appear. Note that disabling an integration with accounts linked for it will make all these accounts go into an inactive status and API request to these accounts will not be permitted. You will be able to switch any integration back to an enabled state just as easily, which will reset all associated linked accounts to an active status.
Integration settings are scoped to a specific project. If you need an integration to be configured on multiple StackOne projects you will have to configure for all individual projects.
Configuring an integration
When setting up or updating an integration you are configuring a specific authentication type. The authentication type decides what will be the process for your end-user to link their account for that provider, specifically which details/credentials they will need to submit.
In most instances you will see API Key or Basic Token in which case the end-user will need to generate the required secret (eg. Ashby or Hibob). For other integrations, you may have a choice of OAuth (and similar, eg. OIDC) in which case, your user may experience a more streamlined login-like flow (eg. Lever or Hubspot.
Integrations with OAuth-based authentications
Some Integrations will prompt for Oauth based fields such (commonly Client ID & Client Secret).
Although you can use StackOne-provided secrets this may mean your end-user journey will see StackOne’s branding (ie. StackOne’s logo or name) when linking an account. StackOne can assist you in retrieving your own oauth / partner credentials for such integrations - contact StackOne’s support team via your channel of choice to request additional assistance.
When configuring an oauth application with a provider, you may be asked for a Callback or Redirect URI. Make sure to usehttps://api.stackone.com/connect/oauth2/{provider key}/callback (replace {provider key} with the actual key, for example: hubspot or bamboohr).
Managing Integrations
Enable, disable and manage integrations for any StackOne Project
The Integrations section of the StackOne dashboard allows you to manage integration (aka provider) for a StackOne Project.
On the integrations page, you can:
- View the list of all integrations for all the categories supported by StackOne (eg.
HRISATSIAMCRMMarketingandLMS. Some integrations and categories are only available based on your plan/contract. If you do not see a category or integration that you would like, contact support manager - Enable, configure and disable integrations.
- Quickly **access **linked accounts and logs related to the integrations
Integrations Listing
Enabling and disabling integrations
Setting up an integration for the first time confirm will automatically set its state as enabled, meaning it will be displayed in the Integrations Hub and you will be able to retrieve Connect Sessions token with the associated provider key.
When disabling an integration by toggling the radio button, a warning will appear. Note that disabling an integration with accounts linked for it will make all these accounts go into an inactive status and API request to these accounts will not be permitted. You will be able to switch any integration back to an enabled state just as easily, which will reset all associated linked accounts to an active status.
Integration settings are scoped to a specific project. If you need an integration to be configured on multiple StackOne projects you will have to configure for all individual projects.
Configuring an integration
When setting up or updating an integration you are configuring a specific authentication type. The authentication type decides what will be the process for your end-user to link their account for that provider, specifically which details/credentials they will need to submit.
In most instances you will see API Key or Basic Token in which case the end-user will need to generate the required secret (eg. Ashby or Hibob). For other integrations, you may have a choice of OAuth (and similar, eg. OIDC) in which case, your user may experience a more streamlined login-like flow (eg. Lever or Hubspot.
Integrations with OAuth-based authentications
Some Integrations will prompt for Oauth based fields such (commonly Client ID & Client Secret).
Although you can use StackOne-provided secrets this may mean your end-user journey will see StackOne’s branding (ie. StackOne’s logo or name) when linking an account. StackOne can assist you in retrieving your own oauth / partner credentials for such integrations - contact StackOne’s support team via your channel of choice to request additional assistance.
When configuring an oauth application with a provider, you may be asked for a Callback or Redirect URI. Make sure to usehttps://api.stackone.com/connect/oauth2/{provider key}/callback (replace {provider key} with the actual key, for example: hubspot or bamboohr).