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

Use the integrations page when you need to connect LenGrowth to a data source or workflow tool.

The page is divided into two tabs:

That split is intentional. Workflow apps are for communication and team interaction. Data sources are for analytics, commerce, CRM, and behavior signals.

At the top of the page, a card titled Company source connections explains that every integration attaches to the active company.

The copy reminds the user to:

That means the integrations page is not a global settings list. It is tied to the current company workspace.

When a company is selected, the page shows Active company and the company name.

If there are no companies in the account yet, the page prompts the user to create one first.

The Workflow Apps tab includes:

These cards are meant to bring LenGrowth into the tools where the team already works.

The Data Sources tab includes:

These cards feed the reporting and recommendation system with company context and performance signals.

Each integration card shows:

When a card is open, the details modal explains why the integration exists, what data it accesses, and how to set it up.

If the integration is already connected, the card can also show the selected source, such as:

The exact label depends on the integration.

Before connecting anything, choose the correct company from the header.

Every connection on this page attaches to that company. If the wrong company is selected, the integration will be saved in the wrong workspace.

Decide whether you need a workflow app or a data source.

Use Workflow Apps for Slack, Teams, or Basecamp.

Use Data Sources for analytics, ads, CRM, commerce, local profile, or product analytics tools.

Click the card you want to manage.

The modal gives you the integration’s purpose, what data it uses, and the setup path.

Some integrations open an external auth flow. Others ask you to enter a value such as a token, tenant ID, account ID, or domain.

The exact fields depend on the integration. The page does not pretend every setup is the same.

Some integrations require a follow-up selection after the account is connected.

Examples from the page include:

That extra step matters because the connection alone is not always enough. The report needs a specific source.

After setup, check the status label on the card.

The card may say Connected, Configured, Active, or show a similar state summary depending on the integration.

Once the integration is connected, LenGrowth can use it in reporting and task context where supported.

The integrations page also shows step-by-step setup content inside the modal, including troubleshooting guidance when available.

If a source is not connected, the report may still work, but it will have less source-backed evidence.

If the connection is removed, the card returns to its disconnected state and the report stops relying on that source.

Make sure you are in the correct tab. Workflow apps and data sources are separated.

Some integrations may be gated or partially unavailable depending on the current plan. The page shows that directly in the card when it applies.

Some integrations need an additional property, site, or account selection before they can feed reporting properly.

Open the integration card and use the step-by-step setup inside the modal. The page is designed to keep the setup details close to the connection itself.

Select a company from the header first. The page is company-specific.