Managing External App Connections in Your CRM

Your CRM includes a marketplace of apps that allow you to connect with third-party services and tools. To use these integrations, you must establish a connection between the app and the external service. This article explains how these connections work and how to manage them.

How Connections Work

Connections are always created and stored at the individual sub-account level. This means each sub-account in your CRM has its own, separate connection to a third-party app. If one sub-account connects to an email service, for instance, that connection is not shared with other sub-accounts.

When you install an app that needs an external connection for a specific sub-account, the system will prompt you to set up that connection immediately after installation.

If you are installing an app across many sub-accounts at once, the connection request does not launch automatically for all of them. Because connections are unique to each sub-account, users within each sub-account must complete the connection process from their own sub-account's marketplace.

Supported Authentication Methods

When connecting an app, you may need to authenticate with the third-party service. The CRM currently supports three primary methods:

• OAuth: You will be redirected to log into the third-party app (like Google or Facebook) and authorize the CRM to access it.
• API Keys: You copy a unique API key from the settings of the third-party application and paste it into a field within the CRM.
• Basic Authentication: You provide the username and password credentials for your account with the third-party service.

The method required depends entirely on the specific app and the external service it connects to. The connection interface in the CRM will guide you through the necessary steps for the chosen method.