Skip to content

Integrations overview

GrowthOS ships Native-first: planning and execution both live inside GrowthOS with zero integration setup. Organization → Integrations (/org/integrations) is where you connect an external tracker when your plan includes Connected.

Connected pushes issues to Linear, Jira, GitLab, Asana, or ClickUp and reads status back. It is gated by integrations.connected, not a separate SKU. If a provider is grayed out, your plan does not include Connected yet.

Coding agents and Figma are not tracker integrations — they connect via MCP from Settings → API Keys & Agents. Planning stays the system of record in GrowthOS in every mode.

  • See which Connected providers your plan allows.
  • Understand why a provider is grayed out (plan gate, not a bug).
  • Open API Keys & Agents for coding-agent and Figma MCP setup.
  • Deciding execution mode for a new organization or project.
  • Checking whether Connected is available before promising it to a stakeholder.
  • Understanding why a Connected provider option is grayed out.
  • Owner or Admin role to view or change organization-level integration settings.
  • For Connected: a plan that includes integrations.connected.
  • Sidebar: Organization → Integrations
  • Direct route: /org/integrations
  1. Open Organization → Integrations (/org/integrations).
  2. Check which Connected providers are available on your plan.
  3. If a provider is grayed out, upgrade or stay Native — planning still works fully.
  4. For agents, open Settings → API Keys & Agents instead of this page.
  • You can explain to a stakeholder, in one sentence, why Connected is or is not available yet.
  • Nobody on the team is blocked waiting for Connected when Native would unblock them today.
  • You know exactly where to check when Connected access is eventually granted.
  • Default to Native; it needs zero setup.
  • Use API Keys & Agents for Cursor/Claude/Figma, not this integrations page.
  • Assuming a grayed-out provider means something is broken rather than not yet enabled.
  • Blocking a launch or demo on Connected setup when Native would work today.
  • Promising a stakeholder Connected access before confirming your organization is enabled.