Set up integrations

Add integrations for the apps behind the first workflow you want to improve: team invites, code activity, issue execution, meetings, or updates.

You can plan directly in the workspace without integrations. When current work already lives in other apps, connect the smallest set that makes the next step useful.

Start with the workflow

Slack is often useful during onboarding because it makes team invitations, channel updates, and async standups easier.

Add version control when code activity should help explain completed work. Add an issue tracker when active execution should appear in boards, recaps, and triage. Add Calendar when meetings should help explain the workday.

Replacing a tracker or roadmap tool? Create initiatives for planned work and connect the apps that still hold current execution. If Jira, Linear, or Trello remains useful during the transition, keep it connected while the team decides what moves into the workspace.

Browse integrations

Open an integration page for setup details.

Version control

Issue tracking

Communication

Calendar and meetings

AI assistants and coding apps

Automation

Personal and workspace integrations

Some integrations are personal. Each person connects the accounts that affect their own work so attribution stays accurate.

Other integrations are workspace or team level. Slack channels, custom apps, webhook subscriptions, and some app installations are configured by admins from Settings -> Integrations because they affect shared behavior.

When a connected issue tracker still owns execution, we follow that provider's status, priority, assignment, and visibility rules. When work is created here, manage those fields in the workspace.

Keep access narrow

Access stays scoped to each provider's grants. We use provider controls for organizations, repositories, projects, channels, and accounts.

After the first integrations are set up, create your first initiative so the workspace has a real roadmap item to plan around.