Integrations - Inkfire Frontdesk

Integration library

Record what connects to Inkfire, who owns the truth, what data moves and how the platform behaves when the service is offline.

Microsoft Entra / 365

Microsoft for staff identity

Planned

Staff identity and future Microsoft collaboration workflows.

Connection details

Authentication: OIDC / OAuth 2.0

Data flow: Microsoft authenticates staff; Platform Core maps identity to Inkfire capabilities.

Offline behaviour: Existing sessions continue until expiry where safe; new staff login is marked degraded.

Xero

Xero for accounting records

Planned

Accounting integration for invoice and financial visibility. The platform should not become a second accounting ledger.

Connection details

Authentication: OAuth 2.0

Data flow: Read financial status and approved summaries; queue controlled sync jobs where required.

Offline behaviour: Finance cards show stale/offline state; other Frontdesk modules continue.

NinjaOne

NinjaOne for managed-device telemetry

Planned

IT monitoring and device/infrastructure operations surfaced into Frontdesk.

Connection details

Authentication: Scoped API credentials

Data flow: Periodic async sync into IT views and incident signals.

Offline behaviour: IT integration goes amber; cached data remains labelled stale; no wider outage.

Inkfire SiteKit

Platform Core for business data; client site for local technical state

Planned

Native WordPress edge agent for client-safe views, telemetry, diagnostics and signed remote operations.

Connection details

Authentication: Per-installation identity + Ed25519 signed commands

Data flow: SiteKit pushes telemetry and polls outward for signed commands.

Offline behaviour: Client WordPress continues normally; Frontdesk marks the installation unreachable.

Inkfire Sentinel

Independent health observations

Planned

Independent monitoring outside the primary platform failure domain.

Connection details

Authentication: Signed heartbeats / scoped monitor credentials

Data flow: Core and agents push heartbeats; Sentinel performs synthetic checks and external alerts.

Offline behaviour: Sentinel failure is reported separately and must not affect Frontdesk runtime.

Cloudflare

Cloudflare for edge/DNS state

Draft

Potential edge, DNS, cache and security signal integration.

Connection details

Authentication: Scoped API token

Data flow: Only selected operational signals should be surfaced.

Offline behaviour: No platform impact; edge tools remain externally manageable.