Integrations
      Back to home
      1. Knowledge Base
      2. Integrations

      Oneserve to Oneserve (O2O) Integration Guide

      Oneserve to Oneserve (O2O) enables seamless job sharing between two Oneserve systems through real-time integration. When a subcontractor team is assigned to an activity in the primary system, a linked job is created in the secondary system.

      Data Flow Between Systems

      1. Primary to Secondary System Events

      The following events in the primary system automatically trigger actions in the secondary system:

      Event Action in Secondary System
      Job Activity assignment to sub-contractor team Creates a new job
      Mapped Job Status updates Adds Job Event
      Job Document upload (with mapped category) Uploads document

      Coming Soon:

      • Document Approval: Only approved documents will be uploaded
      • Version Management: Approve, reject, or cancel versions in secondary system

      2. Secondary to Primary System Events

      The following events in the secondary system automatically trigger actions in the primary system:

      Event Action in Primary System
      Appointment Scheduled/Rescheduled/Cancelled/Completed Adds Job Event
      Mapped Job Status updates Adds Job Event
      Job Document upload (with mapped category) Uploads document

      Coming Soon:

      • Document Approval: Only approved documents will be uploaded
      • Version Creation: Creates version with updated activities

      Version Management (Variations)

      Current Status: Variations must be managed separately in each system while enhanced version management features are being developed.

      For detailed instructions on creating variations, refer to our variation management guide.

      Configuration Requirements

      O2O creates a bidirectional link between a Primary system (where jobs originate) and a Secondary system (where work is assigned).

      3.1 Primary System Configuration

      Required Information:

      • Team name representing the Secondary system
      • Document Categories to be shared with the Secondary system

      3.2 Secondary System Configuration

      Required Information:

      • Work Log Type name for incoming work
      • Work Type name
      • Workflow name
      • Client name
      • Service name
      • Job Status name for sending 'Accepted' notifications to Primary system
      • Document Categories to be shared with Primary system

      3.3 Shared Configuration Requirements

      Data Alignment Needed:

      Priority Mapping

      • Map Primary system priorities to corresponding Secondary system priorities

      System Code Alignment

      • Activity (SOR) Codes must match between systems
      • Site References must match between systems
      • Contact References must match between systems

      This integration requires proper configuration in both systems. Contact your support team before implementation to ensure all requirements are met.