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.

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.

OpenClaw Plugin (Recommended First Integration)

Use the canonical OpenClaw setup guide for installation, authentication, and workspace pairing.

1. Install the plugin

   Follow the install command in the canonical setup guide.

2. Pair in the browser

   Complete the OrgX OAuth and pairing flow.

3. Validate

   Run the read-only validation call in the setup guide.

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 →

---

Integration Status

Linear

Beta integration

Follow the current OAuth setup and review the documented sync scope before enabling agent actions.

GitHub

Available integration

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

Stripe

Content Studio billing surface

Checkout and inbound callback behavior are documented in the API reference.

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.

---

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

1. Navigate to Settings

   Go to Settings → Integrations in OrgX

2. Click Connect

   Click the Connect button next to Linear
3. Authorize in Linear

   You’ll be redirected to Linear’s OAuth flow. Select the workspace you want to connect.

4. Select Projects

   Choose which Linear projects to sync with OrgX. You can change this later.

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.

Primary ICP question answered here: “Why connect this integration now?” GitHub unlocks end-to-end engineering execution with traceable artifacts and approval checkpoints.

Setup

1. Navigate to Settings

   Go to Settings → Integrations in OrgX

2. Click Connect GitHub

   Click the Connect button next to GitHub

3. Authorize via OAuth

   Grant OrgX access to your GitHub account or organization.

4. 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.

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

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

---

Slack

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.

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

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.

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

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.

What happens if an integration token expires?

OrgX will notify you in the Mission Control. Reconnect via Settings to refresh the token.

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.

When will a specific integration be available?

Check the status cards above. We prioritize based on user demand. Request an integration by emailing [e-mail].

Next Steps

How OrgX Works

Understand how integrations fit into the system.

MCP Tools

See all available MCP tools.