Define what each connection needs to do.
Explore the systems and planned services in the ORQESTRA design. This is a guide to integration responsibilities, not a catalogue of production-ready connectors.
Planned connections,
with clear source responsibilities.
ERP-ONEXi is the core engine for finance and operations, with CRM-XT and COLABEX responsible for customer and project records. FINANCE-HQ, SOCIAL MEDIHUB and AGENT INTELLIGENCE add capabilities around them. Review the status and required actions for each.
6 connections in this view
ERP-ONEXi
Finance & operationsThe target engine for accounting, invoicing, purchasing, orders and inventory. ERP-ONEXi is the module name used in the ORQESTRA product design.
Integration in development. Production financial and operational workflows are not offered by this preview.
- Intended information
- Invoice status, payment allocations, customer accounts, product records and operational positions.
- Intended actions
- Prepare and submit supported financial or operational work through explicit company and account mappings.
Responsibility and controls
ERP-ONEXi owns financial and operational transactions. A local draft is not an issued invoice; the accounting result requires source confirmation.
CRM-XT
Customers & salesThe target CRM engine for companies, people and opportunities. CRM-XT is the module name used in the ORQESTRA product design.
Integration in development. Connected pipeline and customer workflows still require verification.
- Intended information
- Customer references, people, opportunity stages and permitted sales activity.
- Intended actions
- Update supported CRM records and use defined commercial events to begin a downstream workflow.
Responsibility and controls
CRM-XT owns pipeline state and commercial responsibility. Shared customer identity links those records to the rest of the business.
COLABEX
Work & knowledgeThe target collaboration engine for documents, conversations and project knowledge, linked to shared business records.
Integration in development. The ORQESTRA online-only workspace and source-permission checks require verification.
- Intended information
- Authorised document metadata, content, versions and conversation context.
- Intended actions
- Open source material and perform supported workspace actions within the source access boundary.
Responsibility and controls
COLABEX’s access rules must be checked before content appears in search, previews or AI answers.
FINANCE-HQ
Finance & operationsThe planned billing workflow around preparation, approval, accounting submission, document delivery and collections.
Planned workflow. Recurring billing, document delivery and collections are not active in these examples.
- Intended information
- Customer and issuing-company context, invoice preparation state and collection history.
- Intended actions
- Prepare a billing document, review it and coordinate accounting submission and delivery.
Responsibility and controls
The billing workflow coordinates preparation and review. ERP-ONEXi remains responsible for the financial transaction.
SOCIAL MEDIHUB
Content & campaignsThe planned workflow for client content, destination accounts, review, schedules and publication results.
Planned capability. Supported networks and publishing actions are not yet confirmed.
- Intended information
- Connected accounts, content revisions, campaign context and provider-supplied metrics.
- Intended actions
- Prepare, review, schedule and publish supported content to configured accounts.
Responsibility and controls
Keep account ownership and provider permissions explicit. Partial publication requires a separate result for each destination.
AGENT INTELLIGENCE
AI & executionThe planned source of specialist agent roles, connected to permitted business tools and bounded execution.
Planned capability. Agent runtimes, tools and model availability require verification.
- Intended information
- Permitted business context, role configuration, run state and source evidence.
- Intended actions
- Execute supported tasks within purpose, tool scope, runtime and policy limits.
Responsibility and controls
An agent’s role does not grant execution authority. Its runtime must enforce the permitted tools, records and actions.
A connection is more than a login.
The integration contract makes the important questions explicit before a workflow depends on it.
- 1
Access
Which organisation, account and source permissions does the connection use?
- 2
Information
What records can it read, which fields does it own and how current are its views?
- 3
Actions
What can it change, what review is required and how is the result confirmed?
- 4
Recovery
How are interrupted responses, partial outcomes and reconciliation handled?
Your existing systems belong in the conversation.
Bring the applications that the business already relies on. The workflow defines what each connection needs to read and do; its API, authentication, permissions and data model define the integration work.
Bring these four things.
- The system and account you use
- The information the workflow needs
- The action you want to perform
- The owner of access and operational support
Connect the process as carefully as the systems.
Map the source records, actions and decisions that the workflow needs. Make responsibility and recovery part of the connection from the start.