Custom
Custom connector
Planned
Custom API connectors are planned. Today, documented CSV/XLSX layouts can be imported through Accounting Imports and the project Migration tool.
Planned. This connection is not available in os.construction yet. This page describes the intended scope; it is not a release date.
Coverage by service or edition
Scope under evaluation. Each service needs its own permissions and acceptance checks.
Custom connector
Planned
Custom API connectors are planned. Today, documented CSV/XLSX layouts can be imported through Accounting Imports and the project Migration tool.
Prepare for a scoped walkthrough
Use this checklist to agree the scope. These are preparation steps, not instructions for an available authorization or sync screen.
- Named source owner, allowed endpoints, schema/version, keys and destination approver.
- Confirm the destination company/project and the reviewer responsible for approving imported records.
Confirm the scope
Named source owner, allowed endpoints, schema/version, keys and destination approver.
Agree the mapping
Tenant + entity + stable external ID → source key; explicit columns → reviewed destination fields.
Preview and reconcile
Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.
Review before applying
An authorized reviewer must confirm destination scope, unresolved records and control totals. A successful extraction is not proof that data has been applied.
Check recovery and access
Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.
Mapping and synchronization
- Record mapping
Tenant + entity + stable external ID → source key; explicit columns → reviewed destination fields.
- Sync boundary
- Define page termination, rate limits, deletions and checkpoints before API implementation.
- Source ownership
- The provider remains authoritative for its source records. Local project placement, access and workflow decisions need explicit destination ownership. Match by scoped IDs, not names alone.
- Outbound policy
- No provider business writes are offered here. Sending, posting, inviting, deleting and permission changes require separately approved capabilities.
Conflicts and recovery
When records disagree
Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.
When a run stops
Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.
Limits to plan around
- Not an arbitrary endpoint or code-execution service. No promise to connect every system.
- Not available in os.construction yet. Provider documentation describes the upstream API, not an os.construction connection.
No provider connection is initiated from this page. For the reviewed accounting import workflow available today, see the accounting import guide.
Documentation and source dates
Provider documentation establishes upstream capabilities, not os.construction availability. Confirm the current edition and API contract before planning setup.
- Accounting import guideAccessed