Managing Integration Configurations

Enable, disable, and manage integration configurations for any StackOne Project

The Integrations section of the StackOne dashboard allows you to manage integrations (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 (e.g., HRIS, ATS, IAM, CRM, Marketing, LMS, and more). Some integrations and categories are only available based on your plan or contract. If you do not see a category or integration that you would like, contact your support manager.
• Enable, configure, and disable integrations.
• Quickly access linked accounts and logs related to the integrations
• Delete integrations

Configuring your first integration

To configure your first integration, navigate to the Integrations section and click on the + button.

You will be presented with a list of connectors to choose from. Select the connector you want to configure.

You can also search for a specific connector by name.

Once you have selected the connector, you will be presented with a form to configure the integration.

Fill in the form with the required information and click the Save button. You will notice a “Default Configuration” dropdown that allows you to mark an integration as the default configuration for that connector in the project. You can change the default configuration later once you have configured multiple integrations for the same connector.

Once you have configured the integration, you will see it in the list of integrations.

You can filter integrations by name or category.

Managing integrations

Enabling and disabling integrations

Setting up an integration for the first time will automatically set its state as enabled, meaning it will be displayed in the Integrations Hub and you will be able to retrieve a Connect Session token with the associated provider key.

When disabling an integration, a warning will appear. Note that disabling an integration with linked accounts will make all those accounts go into an inactive status, and API requests to these accounts will not be permitted. You can 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 it for each individual project.

Ellipsis menu options

The ellipsis menu on each integration row provides different options depending on whether you have a single integration or multiple integrations configured for the same connector.

Single integration for a connector

When you have only one integration configured for a connector, the ellipsis menu provides the following options:

• Edit the integration
• View logs for the integration
• Copy the ID of the integration
• Copy the ID of the connector
• Disable the integration
• Delete the integration

Multiple integrations for a connector

When you have configured multiple integrations for the same connector, the available options differ depending on whether the integration is set as the default or not.

For the default integration:

• Edit the integration
• View logs for the integration
• Copy the ID of the integration
• Copy the ID of the connector
• Disable the integration

For non-default integrations:

• Edit the integration
• View logs for the integration
• Copy the ID of the integration
• Copy the ID of the connector
• Disable the integration
• Delete the integration
• Make it default

Deleting an integration

You’ll only be able to delete an integration if there are no linked accounts for it, and if it’s either the only integration for the connector or a non-default integration for the connector.

Authentication types

When setting up or updating an integration, you are configuring a specific authentication type. The authentication type determines the process for your end-user to link their account for that provider, specifically which details or credentials they will need to submit.

API Key and Basic Token

In most instances, you will see API Key or Basic Token, in which case the end-user will need to generate the required secret (e.g., Ashby or Hibob).

OAuth-based authentications

For other integrations, you may have a choice of OAuth (and similar, e.g., OIDC), in which case your user may experience a more streamlined login-like flow (e.g., Lever or Hubspot).

Some integrations will prompt for OAuth-based fields such as Client ID and Client Secret.

Although you can use StackOne-provided secrets, this may mean your end-user journey will see StackOne’s branding (i.e., StackOne’s logo or name) when linking an account. StackOne can assist you in retrieving your own OAuth or 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 use https://api.stackone.com/connect/oauth2/{provider key}/callback (replace {provider key} with the actual key, for example: hubspot or bamboohr).

Configuring multiple integrations for the same connector

You can configure multiple integrations for the same connector. This is useful if you want to use different configurations for the same connector for different groups of accounts in the same project, for example if some accounts need to be linked with an API key and others with an OAuth token.

To configure multiple integrations for the same connector, you can go to the Integrations page and click on the + button. You will be presented with the same form as before, and you will be able to configure whether this integration should be the default integration for the connector or not.

You can toggle the default integration for the connector by clicking on the “Make default” option mentioned in the ellipsis menu options section above.

For example, with the TeamTailor connector we used in the previous example, we previously set up a Public API key integration. Now we want to set up a Public + Partner API key integration.

If we set the Public API key integration as the default integration, in the hub we’ll show the Public API integration setup fields. In this case, the difference between the two is the External Trigger Token field.

However, if we set the Public + Partner API key integration as the default integration, in the hub we’ll show the Public + Partner API integration setup fields. Notice the presence of the External Trigger Token field.

You will be able to select which specific integration configuration to use in the hub in the future without having to toggle the default integration for the connector back and forth.

Troubleshooting

Integration or account not visible on the Integrations page

If you cannot see a specific integration provider or account on the Integrations page, this is typically because the integration needs to be enabled for your account by StackOne.

Common scenarios:

• The integration provider you’re looking for doesn’t appear in the list
• A specific category (e.g., HRIS, ATS, LMS) is not visible
• An integration that was previously visible is no longer showing

Resolution:

Contact your StackOne support manager or reach out to [e-mail] to request access to the specific integration or category. The StackOne team will enable it for your account.

Integration and category availability depends on your plan and contract. Some integrations require additional setup or partnership agreements before they can be enabled.

Integration not visible in the Integrations Hub

If you cannot see a specific integration in the Integrations Hub, and the integration is visible from the Integrations page, this is typically due to the integration being disabled.

Wrong fields being shown in the Integrations Hub

If the fields shown in the Integrations Hub don’t match what you expect, verify that the correct integration is set as the default integration for the connector.