The integrations page lives at https://lengrowth.com/integrations.

The integrations page is split into two tabs:

The page also shows a "Company source connections" card at the top. That card explains which company is active and tells you whether you need to create a company first or switch the selected company in the header before continuing.

Each integration appears as a card with a connection status, a brief description, and a "Connect" or "Manage connection" button. When a source is connected, the card shows "Connected" and may display sync summary text, the selected source, last sync time, and where the source is used.

Use the integrations page when you want to:

If you only want to know whether a company exists yet, use the dashboard or growth page first. If you already know the company and want to feed the workflow, this is the right page.

The page is explicit about this dependency. It tells you that every connection on the page will attach to the selected company. If there are no companies yet, it gives you a create-company action instead of letting you connect data to nowhere.

This is the first thing to check when a setup looks wrong. Many integration issues come from being on the correct page but the wrong company.

Workflow apps and data sources solve different problems, so the page keeps them separate.

Use this tab for:

These are the integrations that let LenGrowth show up in your team communication tools.

Use this tab for:

These sources feed reporting, recommendations, or company context. They are not the same as a chat-based workflow app, even if they all live on the same integrations page.

If the card is already connected, the button changes to "Manage connection". That tells you the source is live and you can review or update it instead of starting from scratch.

The page also supports a focused modal for each source. That modal is useful because it keeps the instructions, the selected account, and the connection action in one place.

Inside the modal, each integration can show a few specific areas of help:

The step-by-step section can expand into:

That wording is important because it reflects how the product actually teaches each setup. LenGrowth is not trying to send you to a generic support article. It gives you the exact pieces you need to finish the connection for that source.

If you are unsure what to expect, always open the accordion before you start pasting tokens or signing in. It usually tells you whether the source uses OAuth, an API key, a property selector, a site selector, or a manual identifier.

Workflow apps are the fastest way to bring LenGrowth into your daily communication tools.

The page uses different buttons depending on the integration type:

For Slack, the page includes a direct workspace install flow. For Teams and Basecamp, the page asks for the relevant tenant or account information after you set up the bot or chatbot on the provider side.

Some sources are OAuth-based and show a sign-in prompt such as "Sign in with Google" or a similar provider-specific button. Others use a direct input form where you paste a private app token, secret key, store domain, location ID, or API key.

The page is careful about selections after connection. If a source exposes multiple accounts or properties, the card shows a list of options and a "Select" button so you can choose the exact one that belongs to the current company.

After the source connects, do not stop at the success message.

That last step is important because it shows you where LenGrowth expects the connection to matter. If the source is connected but the selected account is wrong, the card will often make that visible immediately.

Once the connection is correct, the page starts acting like a verified source registry for that company.

You should expect:

That is why the integrations page is a setup page and a verification page at the same time. The goal is not merely to click "Connect". The goal is to make sure the right source is attached to the right company and can be used elsewhere in the product.

That means there is no active company in the header yet. Choose the company before connecting anything.

Check whether you are in the correct tab. Workflow apps and data sources are separated intentionally.

Open the card again and choose the correct item from the list. Many providers show more than one property, site, or account.

The page will tell you where to find it in the setup guidance. If you still cannot find the value, stop and confirm the provider-side setup first.

That means interaction with the source is currently blocked. Read the message on the card before trying again. If the block relates to plan access, review the subscription page first.

If something does not look right, confirm you are using the correct account, page, and permission level.