Imported records
Supported customer, vehicle, service, invoice, payment, appointment, estimate, and repair-order context is imported according to current API coverage.
Shopmonkey integration
Import supported Shopmonkey records through a guarded read boundary.
VehicleDesk uses the official Shopmonkey API origin, truthful call budgets, native webhook verification, and visible local data-quality evidence. Shopmonkey remains authoritative for source repair records.
Review integration fit Available / controlled
Shopmonkey source recordsBudgeted API + signed webhooksTenant-scoped VehicleDesk dataStaff-reviewed local workflow
Connection detail
The direction, owner, failure state, and source boundary are explicit.
These are product and implementation behaviors, not a generic integration logo claim.
Authoritative source
Shopmonkey remains authoritative for source repair records and financial finalization.
VehicleDesk local state
Notes, tasks, reminders, opportunity/deferred state, workflow outcomes, safety evidence, and data-quality findings may be stored locally.
Sync frequency and limits
Scheduled and manual jobs use explicit call budgets, retry accounting, quota snapshots, and safe full-sync controls.
Webhook behavior
Signed provider events enter a queued, replay-aware intake path before processing.
Write boundary
Provider writes remain disabled unless a separately reviewed workflow explicitly enables a narrow operation.
Rate and failure state
Budget exhaustion, rate limits, provider errors, stale data, and failed jobs remain distinct visible states.
Credential security
Credentials stay server-side, encrypted, destination-bound, and can be rotated or disconnected without exposing their value.
Setup owner
A VehicleDesk implementation owner and a shop-side owner confirm access, scope, initial sync, and data-quality evidence.
Freshness and support
Sync Health records last success, warnings, quota state, and support evidence for investigation.
Practical workflow review
Review the source data and sync boundaries before connecting a shop.
Preview the workflow-review agenda, current product scope, safety boundaries, and implementation questions before public requests open.