External Sync
Alguna’s External Sync enables bidirectional synchronization between Alguna and external systems like CRMs, ERPs, and accounting software. Keep your data in sync automatically with conflict detection and resolution.How It Works
Supported Systems
| System | Entities | Direction |
|---|---|---|
| Salesforce | Accounts, Contacts, Opportunities | Bidirectional |
| HubSpot | Companies, Contacts, Deals | Bidirectional |
| QuickBooks | Customers, Invoices, Payments | Bidirectional |
| NetSuite | Customers, Invoices, Payments | Bidirectional |
| Xero | Contacts, Invoices, Payments | Bidirectional |
Configuration
Enable Sync
Sync Direction Options
| Direction | Description |
|---|---|
alguna_to_external | Push Alguna changes to external |
external_to_alguna | Pull external changes to Alguna |
bidirectional | Sync both ways |
Field Mapping
Map fields between systems:Transform Functions
| Transform | Description |
|---|---|
none | Pass through as-is |
number_to_currency | Format as currency |
date_to_iso | Convert to ISO format |
boolean_to_string | Convert true/false to Yes/No |
custom | Use custom JavaScript function |
Conflict Resolution
When the same record is modified in both systems:Resolution Strategies
| Strategy | Description |
|---|---|
alguna_wins | Alguna data takes precedence |
external_wins | External data takes precedence |
latest_wins | Most recent modification wins |
manual | Flag for manual review |
Per-Field Resolution
Sync Triggers
Scheduled Sync
Run sync on a schedule:Real-Time Sync
Trigger sync on changes:Manual Sync
Sync Status
Check Sync State
View Sync History
Handling Errors
Error Types
| Error | Description | Resolution |
|---|---|---|
field_validation | External system rejected field value | Check field mapping |
rate_limit | External API rate limited | Automatic retry |
auth_expired | Authentication expired | Reconnect integration |
not_found | Record doesn’t exist | Skip or create |
Error Webhooks
Retry Failed Syncs
Entity Matching
By External ID
Link records using external IDs:By Email/Name
Configure matching rules:Salesforce Example
Complete Setup
Best Practices
Start One-Way
Begin with one-way sync, then enable bidirectional once stable.
Monitor Conflicts
Review conflicts regularly to tune resolution strategies.
Test in Sandbox
Test sync configuration in sandbox environments first.
Map Carefully
Document field mappings and transformation logic.
Webhooks
| Event | Description |
|---|---|
sync.completed | Sync job finished |
sync.error | Sync encountered errors |
sync.conflict | Conflict detected (if manual resolution) |