Integrations
SharedConnect Usable both ways with your existing systems: data lands idempotently (no duplicate mess on re-sync) and flows back out via an outbound queue.
What you do here
You create connections (e.g. to DATEV, a shop, a REST API or via webhook), pick the direction (inbound, outbound or two-way) and the target data (e.g. customers or articles). Inbound records are matched by their external id: known = update, new = create. That keeps two-way mirroring clean and duplicate-free.
Status & log
Each connection has a status (active, paused, error) and a run log: when it last synced, how many records came in and out and whether there were errors. The actual transport (fetch/deliver) is handled by a background service — here you configure and monitor it.
Tips
Use the field mapping to map local fields onto the external system's keys — only mapped fields are transferred. Endpoints must start with https; internal addresses are blocked for security reasons. "Sync now" triggers a connection immediately without waiting for the schedule. If a connection shows an error, first check the endpoint and the last result in the run log, and pause it until the cause is fixed.
What you can do here
- ✓Integrations
- ✓Integration
- ✓New integration
- ✓Edit
- ✓Delete
- ✓Sync now
- ✓Set status
- ✓Pause
Live preview — real view with sample data