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)
The fastest way to connect OrgX to your IDE. OpenClaw handles authentication, MCP configuration, and workspace pairing automatically.Install OpenClaw
Install the OpenClaw browser extension.
Pair with OrgX
Visit useorgx.com, go to Settings, and click
“Pair with OpenClaw”.
- Automatic MCP config — no manual token management
- Live OrgX dashboard inside OpenClaw
- Seamless workspace switching
- Manual-key fallback for advanced setups
Integration Status
Linear
✅ Generally AvailableFull OAuth integration with project/issue sync, Kanban updates, real-time
webhooks, and comment threading.
GitHub
⚠️ BetaOAuth integration with repository access, PR creation, and issue commenting.
Stripe
✅ Generally AvailableBilling integration with checkout flow, customer portal, and subscription management.
Slack
🔜 Coming SoonBlocker detection, team notifications, decision alerts.
Notion
🔜 Coming SoonDatabase sync, brief exports, documentation links.
HubSpot
🔜 Coming SoonDeal updates, contact sync, activity logging.
Figma
🔜 Coming SoonFrame exports, comment integration, design feedback loops.
Mailchimp
🔜 Coming SoonCampaign drafting, audience management, schedule automation.
Linear
If your team already uses Linear, connect it once and agents will sync issues, projects, and status updates automatically.Setup
Authorize in Linear
You’ll be redirected to Linear’s OAuth flow. Select the workspace you want to
connect.
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.Primary ICP question answered here: “Why connect this integration now?”
GitHub unlocks end-to-end engineering execution with traceable artifacts and
approval checkpoints.
Setup
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:- Agent analyzes the task and codebase
- Creates a branch with changes
- Opens a PR with description and context
- Links the PR back to the originating task or issue when available
- Surfaces a decision for you to review/merge
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.
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
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.
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
- Agent calls the MCP tool (e.g., Slack send message)
- If native integration exists, it executes normally
- If only a stub exists, we log the call and return a placeholder
- 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 |
Stub coverage is runtime-dependent. Use the active MCP tool catalog in your
client to confirm what is currently callable.
FAQ
Can I disconnect an integration?
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?
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?
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?
When will a specific integration be available?
Check the status cards above. We prioritize based on user demand. Request an
integration by emailing [email protected].
Next Steps
How OrgX Works
Understand how integrations fit into the system.
MCP Tools
See all available MCP tools.