Skip to content

Integrations

Overview

Where the system talks to something outside itself, and what belongs on our side of that boundary.

This page is an index. The runbooks live in Operations and the reconstruction records in History. Nothing is duplicated here.

Access

No menu. This section is reached from Developer.

Screen

No screen.

Main Features

The Providers In Use

Provider What it is for The runbook
QuickBooks Online Sending invoices out Sending an Invoice to QuickBooks Online
Gmail Appointment requests arriving by email Reviewing an Appointment Email
Telegram Loader and parking notifications Loader and Yard Execution
Timekeeping Clock and break records Inbound Assignment Board
File storage Documents and photos Documents and Exceptions

The Operational Material

Page What it covers
Platform Integration And Provider Recovery Runbook Restoring a provider when it stops responding
Provider Credentials Replacing a stored credential
The Integration Boundary Record What sits on our side and what sits outside

Fields

Field What it means
Provider The external system
Credential The stored secret for it, held encrypted
Effect What we claim happened
Evidence What proves it

Status

Shown Means
Configured A stored credential exists. It does not mean the provider accepted it
Not configured No stored value for that key

Notes

  • A provider success does not prove our transaction committed, and our commit does not prove the provider succeeded. The two are separate and can differ.
  • Never retry an external effect because our screen did not confirm. Check the provider first — a duplicate invoice or a duplicate email is much harder to undo than a late one.
  • A notification is not the state. A Telegram message that arrived proves delivery, not that the change saved.
  • Credentials cannot be removed from the provider screen, and must never be copied into a document, an email, a ticket, a screenshot or a log.
  • The file provider is not connected. Selecting a file in Fleet Management uploads nothing, and the selection is not evidence of delivery.
  • Test connectivity only through the provider's own runbook. Do not verify a credential by saving it.