How ORQO Connects
High-level overview of every inbound and outbound integration path in ORQO.
Overview
Supported Platforms
Apps vs. Skills vs. MCP
What the three integration types are, when to pick which, and how they fit together.
Apps & Channels
Apps are connections to external platforms. They handle the world-facing concerns — receiving messages, delivering agent output, OAuth, webhook verification. Anything engine-facing — the tools agents call when interacting with the platform — lives in a separate primitive called a Skill. Most platform integrations pair an App with a Skill, but either side can stand alone (see Integration Hierarchy for the full picture).
Doorkeeper AI
Doorkeeper is your organization's AI front desk. It receives inbound messages from all connected Apps — Slack, WhatsApp, Telegram — and handles them intelligently: responding directly, delegating to workflows, managing projects and documents, or routing to the right contact.
Integration Builder AI
Chat with Integration Builder to add new platforms — Stripe, Notion, Slack, and more — to your ORQO organization without writing code.
Workflow Assistant
Chat with the Workflow Assistant to design, build, run, and improve workflows in any project — without touching the visual builders directly.
Tool Builder
Chat with the Tool Builder to write, verify, and save custom Python tools for your organization — without writing Python yourself.
Public Chatbot
Any project with Long-Term Memory activated can publish a Public Chatbot — a knowledge assistant that answers questions from that project's knowledge graph. Toggle it on in the project settings, then either embed the ready-made chat widget on your website or integrate via the JSON API.
Webhooks
Webhooks let external systems send events to ORQO over HTTP. Any system that can make an HTTP POST request can integrate with ORQO via webhooks.
API
ORQO provides an API for programmatic access. Use it to trigger workflows, receive callbacks, and integrate ORQO into your automation pipelines.