> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Add optional integrations and connectors to OrgX—GitHub, Linear, Slack, and more.

OrgX integrates with the tools you already use. Agents read context from these optional integrations and take actions (with your approval) to keep everything in sync.

<Info>
  OrgX does not require Linear to get started. Start in OrgX first with the web
  app, Wizard CLI, OpenClaw, ChatGPT, or the hosted MCP endpoint, then connect
  external systems only when your workflow needs them.
</Info>

## OpenClaw Plugin (Recommended First Integration)

The fastest way to connect OrgX to your IDE. OpenClaw handles authentication, MCP configuration, and workspace pairing automatically.

<Steps>
  <Step title="Install OpenClaw">
    Install the [OpenClaw](https://openclaw.com) browser extension.
  </Step>

  {' '}

  <Step title="Pair with OrgX">
    Visit [useorgx.com](https://useorgx.com), go to **Settings**, and click
    **"Pair with OpenClaw"**.
  </Step>

  <Step title="Validate">
    In your IDE, run `workspace action=get` to confirm the connection is active.
  </Step>
</Steps>

**What you get**:

* Automatic MCP config — no manual token management
* Live OrgX dashboard inside OpenClaw
* Seamless workspace switching
* Manual-key fallback for advanced setups

[Full OpenClaw setup guide →](/docs/guides/openclaw-plugin-setup)

***

## Integration Status

<CardGroup cols={2}>
  <Card title="Linear" icon="check-circle" color="#5E6AD2">
    **✅ Generally Available**

    Full OAuth integration with project/issue sync, Kanban updates, real-time
    webhooks, and comment threading.
  </Card>

  <Card title="GitHub" icon="github" color="#24292F">
    **⚠️ Beta**

    OAuth integration with repository access, PR creation, and issue commenting.
  </Card>

  <Card title="Stripe" icon="credit-card" color="#635BFF">
    **✅ Generally Available**

    Billing integration with checkout flow, customer portal, and subscription management.
  </Card>

  <Card title="Slack" icon="slack" color="#E01E5A">
    **🔜 Coming Soon**

    Blocker detection, team notifications, decision alerts.
  </Card>

  <Card title="Notion" icon="book" color="#000000">
    **🔜 Coming Soon**

    Database sync, brief exports, documentation links.
  </Card>

  <Card title="HubSpot" icon="hubspot" color="#FF7A59">
    **🔜 Coming Soon**

    Deal updates, contact sync, activity logging.
  </Card>

  <Card title="Figma" icon="figma" color="#F24E1E">
    **🔜 Coming Soon**

    Frame exports, comment integration, design feedback loops.
  </Card>

  <Card title="Mailchimp" icon="envelope" color="#FFE01B">
    **🔜 Coming Soon**

    Campaign drafting, audience management, schedule automation.
  </Card>
</CardGroup>

***

## Linear

If your team already uses Linear, connect it once and agents will sync issues,
projects, and status updates automatically.

### Setup

<Steps>
  <Step title="Navigate to Settings">
    Go to **Settings → Integrations** in OrgX
  </Step>

  {' '}

  <Step title="Click Connect">Click the **Connect** button next to Linear</Step>

  {' '}

  <Step title="Authorize in Linear">
    You'll be redirected to Linear's OAuth flow. Select the workspace you want to
    connect.
  </Step>

  <Step title="Select Projects">
    Choose which Linear projects to sync with OrgX. You can change this later.
  </Step>
</Steps>

### What Gets Synced

| Direction     | Data                                | Frequency              |
| ------------- | ----------------------------------- | ---------------------- |
| Linear → OrgX | Issues, projects, labels, states    | Real-time via webhooks |
| OrgX → Linear | Comments, state changes, new issues | On agent action        |

### Capabilities

Once connected, agents can:

* **Read** issues, projects, and team context
* **Create** new issues from initiative breakdowns
* **Update** issue states and add comments
* **Link** artifacts back to originating issues

### Permissions Required

| Scope   | Purpose                            |
| ------- | ---------------------------------- |
| `read`  | Access issues and projects         |
| `write` | Create issues and comments         |
| `admin` | Manage webhooks for real-time sync |

***

## GitHub

Connect GitHub to enable code-related agent workflows—PR creation, issue comments, and repository context.

<Info>
  Primary ICP question answered here: **"Why connect this integration now?"**
  GitHub unlocks end-to-end engineering execution with traceable artifacts and
  approval checkpoints.
</Info>

### Setup

<Steps>
  <Step title="Navigate to Settings">
    Go to **Settings → Integrations** in OrgX
  </Step>

  {' '}

  <Step title="Click Connect GitHub">
    Click the **Connect** button next to GitHub
  </Step>

  {' '}

  <Step title="Authorize via OAuth">
    Grant OrgX access to your GitHub account or organization.
  </Step>

  <Step title="Select Repositories">
    *Coming soon* — currently all accessible repos are available to agents.
  </Step>
</Steps>

### Capabilities

| Feature               | Status         |
| --------------------- | -------------- |
| OAuth authentication  | ✅ Live         |
| Token storage         | ✅ Live         |
| PR creation by agents | ✅ Live         |
| Issue commenting      | ✅ Live         |
| Repo selection UI     | 🔜 Coming soon |
| Branch management     | 🔜 Coming soon |

### Agent Workflow

When the Engineering Agent needs to ship code:

1. Agent analyzes the task and codebase
2. Creates a branch with changes
3. Opens a PR with description and context
4. Links the PR back to the originating task or issue when available
5. Surfaces a **decision** for you to review/merge

<Warning>
  GitHub integration is in beta. We recommend reviewing all agent-created PRs
  carefully before merging.
</Warning>

***

## Slack

<Info>
  Slack is not a native OrgX connector yet. Selected agent runtimes can use
  configured Slack credentials or external MCP servers, but treat that as an
  advanced setup rather than the default product path.
</Info>

### Planned Features

* **Blocker Detection**: Agents scan channels for blocked work
* **Notifications**: Get decision alerts in Slack
* **Thread Updates**: Agents post progress updates
* **Approval Buttons**: Approve decisions directly in Slack

***

## Notion

<Info>
  Notion is not a native OrgX connector yet. Selected agent runtimes can use
  configured Notion credentials or external MCP servers, but the default product
  flow does not require Notion.
</Info>

### Planned Features

* **Database Sync**: Pull briefs and specs from Notion
* **Documentation Links**: Reference Notion pages in artifacts
* **Export Artifacts**: Push specs and reports to Notion

***

## MCP Stubs

For integrations not yet fully native, OrgX can expose external-tool or stub-like
actions in selected agent runtimes. Use the active tool catalog in your client as
the source of truth for what is callable in your workspace.

### How Stubs Work

1. Agent calls the MCP tool (e.g., Slack send message)
2. If native integration exists, it executes normally
3. If only a stub exists, we log the call and return a placeholder
4. Usage data helps us prioritize which integrations to build next

### Current Stub Targets

| Integration | Typical Actions                  |
| ----------- | -------------------------------- |
| Slack       | Send message, list channels      |
| Notion      | Query database, update page      |
| HubSpot     | Update deal, log activity        |
| Mailchimp   | Schedule campaign, list audience |
| Figma       | Export frame, list comments      |

<Info>
  Stub coverage is runtime-dependent. Use the active MCP tool catalog in your
  client to confirm what is currently callable.
</Info>

***

## FAQ

<AccordionGroup>
  <Accordion title="Can I disconnect an integration?">
    Yes — go to Settings → Integrations and click **Disconnect**. Agents will no
    longer have access, but historical data remains in OrgX.
  </Accordion>

  {' '}

  <Accordion title="What happens if an integration token expires?">
    OrgX will notify you in the Mission Control. Reconnect via Settings to refresh
    the token.
  </Accordion>

  {' '}

  <Accordion title="Can agents access all my data in connected tools?">
    Agents only access data you've explicitly granted via OAuth scopes. Each
    integration page shows exactly what permissions are requested.
  </Accordion>

  <Accordion title="When will a specific integration be available?">
    Check the status cards above. We prioritize based on user demand. Request an
    integration by emailing [hello@useorgx.com](mailto:hello@useorgx.com).
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="How OrgX Works" icon="sitemap" href="/docs/platform/architecture">
    Understand how integrations fit into the system.
  </Card>

  <Card title="MCP Tools" icon="wrench" href="/docs/api/mcp-tools">
    See all available MCP tools.
  </Card>
</CardGroup>