Setting Up a Sync

This article walks through configuring a new table sync job, from picking the source to running the first batch and confirming the results.

Step-by-Step

1. Open Architect Panel → Table Sync and click New Sync.
2. Pick the source type:
   • SQL endpoint — JDBC/ODBC connection to a remote database.
   • REST API — call into an external API.
   • CSV / SFTP — fetch a file periodically.
   • Webhook receiver — accept pushes from the source.
3. Provide credentials / endpoint URLs. Test the connection.
4. Map columns: each source column to a target column on the ActiveManage datastore. Optional transforms (string trim, date format conversion, lookup table).
5. Set sync rules:
   • Direction (pull / push / bidirectional).
   • Identifier column.
   • Delete policy (mirror deletes, ignore deletes).
   • Conflict policy (newer wins, source wins, manual review).
6. Schedule:
   • On-demand only (manual triggers).
   • Hourly / daily / weekly cron.
   • Real-time via webhooks.
7. Run a test sync of N rows in dry-run mode. Review the proposed changes.
8. Enable.

Worked Examples

• Salesforce contacts → ActiveManage users: REST source, hourly, identifier = Salesforce 18-char ID, conflict = newer wins.
• Master product CSV from supplier: SFTP source, daily 06:00 UTC, identifier = SKU, conflict = source wins (we're a mirror, not master).
• Webhook-driven inventory: Webhook receiver, real-time, identifier = warehouse SKU, conflict = source wins.
• Bidirectional orders: SQL source, real-time via change-data-capture stream, identifier = order ID, conflict = manual review on any clash.