> ## 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

> Connect supported native integrations or external MCP providers to OrgX.

OrgX can connect to supported native integrations. External MCP providers can
offer additional tools, but their authorization and delivery contracts remain
separate from OrgX.

<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)

Use the [canonical OpenClaw setup guide](/docs/guides/openclaw-plugin-setup) for
installation, authentication, and workspace pairing.

<Steps>
  <Step title="Install the plugin">
    Follow the install command in the canonical setup guide.
  </Step>

  <Step title="Pair in the browser">
    Complete the OrgX OAuth and pairing flow.
  </Step>

  <Step title="Validate">
    Run the read-only validation call in the setup guide.
  </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">
    **Beta integration**

    Follow the current OAuth setup and review the documented sync scope before
    enabling agent actions.
  </Card>

  <Card title="GitHub" icon="github" color="#24292F">
    **Available integration**

    Follow the OAuth setup and review the documented repository access and write
    actions before enabling agent work.
  </Card>

  <Card title="Stripe" icon="credit-card" color="#635BFF">
    **Content Studio billing surface**

    Checkout and inbound callback behavior are documented in the API reference.
  </Card>
</CardGroup>

<Note>
  Slack, Notion, HubSpot, Figma, and Mailchimp are not native OrgX integrations
  in this guide. An external MCP server may provide its own connection, but its
  tools and permissions are outside the OrgX integration contract.
</Note>

***

## Linear

If your team already uses Linear, follow the current connection flow and review
which issue, project, and status records are in scope. Synchronization and
write behavior depend on the connected account and granted permissions.

### 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    | Sync behavior depends on the documented connection |
| 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 the documented webhook or connection settings |

***

## 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">
    Select the repositories that the connected agent workflow may access. If
    repository selection is not shown in your workspace, review the GitHub
    installation's actual repository permissions before enabling writes; do not
    assume that every accessible repository is in scope.
  </Step>
</Steps>

### Capabilities

| Feature               | Status       |
| --------------------- | ------------ |
| OAuth authentication  | ✅ Live       |
| Token storage         | ✅ Live       |
| PR creation by agents | ✅ Live       |
| Issue commenting      | ✅ Live       |
| Repository access     | ✅ Documented |
| Branch and PR writes  | ✅ Documented |

### 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>

### Scope

OrgX does not provide a native Slack connector in this guide. To use Slack,
connect an external MCP server in the client that owns the Slack credentials.
OrgX cannot attest to that server's permissions, retention, or delivery
semantics.

***

## 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>

### Scope

OrgX does not provide a native Notion connector in this guide. Use an external
MCP server only after reviewing its permissions and data-handling behavior.

## 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>