Syncing from other systems
Integrations covers Cobblr telling other services what happened. Sync is the other direction: mirror records from an external system into your workspace, and keep them current.
Connections
Add a sync connection on the Integrations page: pick a source, give it the source's address and a credential, and choose which entity types to mirror.
- Each type toggles and reconciles on its own.
- A section can target a specific module instance.
- The connection exposes a webhook URL so the source can push changes live instead of waiting for the next pull.
Preview before import
The first import shows you both sides before anything is written: what the source has, and what it matches in your workspace. You review and merge rather than blind-import, and photos on the source's records can come along into Cobblr's file storage.
Sources are installable
A sync source is a manifest you install, not code baked into Cobblr: it declares the source's endpoints and how its fields map onto Cobblr's. Anyone can write one for a system they use (a maker-inventory app, a database with an API), and the one Cobblr install stays generic. For filament, there's a Spoolman integration on the inventory side.
To write a source for a system you use, see Sync-source manifests.
Reaching a source on your LAN
If the source runs on your local network and your Cobblr can't reach it directly, the sync rides the edge bridge: the bridge dials out from your network and carries the fetch, so nothing gets exposed.