Makini keeps each connection's data fresh by syncing it on a schedule. Two settings shape every sync: the frequency (how often it runs) and the history (how far back it reads). Set app-wide defaults once, adjust any connection on its own, and start a sync by hand whenever you need one.Frequency#
Every 15 min: near real-time.
Hourly: good for fast-moving records.
Every 6 hours: recommended for most platforms.
History#
History sets how far back a full sync reads transactional records, such as work orders:Everything: a full backfill. The first sync takes longest.
1 year: the recommended starting point.
6 months, 3 months: a quicker first sync.
New data only: skips everything that already exists.
Frequency and history never change what you pay. Credits are per connection, so choose the settings that fit the data, not the bill.
Defaults for new connections#
Settings → Sync defaults sets the frequency and history that new connections start with. Each can follow each platform's own recommendation, or be a value you pick. Click Save changes to apply.Saving updates every connection that follows the default. If you widen the history, those connections fetch the additional history right away, and the page tells you how many are doing so.One connection's settings#
To tune a single connection, open its row menu under Connections and choose Sync settings. Pick a frequency and a history for that connection alone; each change saves as you make it. Choose Follow your account default to hand it back to the app-wide setting.When you widen a connection's history, Makini fetches the additional records automatically, usually right away. If a sync is already running, the fetch follows it.Start a sync now#
Open a connection's row menu and choose Trigger sync. Pick how far back this run reads:| Option | What it does |
|---|
| Since the last sync | Fetches what changed since the connection last synced. The fastest option, and what the schedule does. |
| Since a date | Re-reads everything changed since a date you pick (from the start of that day, UTC). For this run only. |
| All history | Re-reads everything inside the connection's history setting. The most thorough option, and the slowest. |
Click Start sync. The connection's schedule and history settings stay as they are. A connection runs one sync at a time, so wait for a running sync to finish before starting another.Watch a sync run#
The connection's status on the Connections page updates live. While a sync runs, its badge reads Synchronizing with a progress bar, then Preparing data while Makini builds the unified records. When it finishes, the status returns to Active. A run that fails shows Sync error, and a connection whose credentials the system refused shows Expired until you reconnect it.React to syncs in your code#
Each finished run sends a sync.completed webhook with its status, startedAt and finishedAt. Use it to read exactly what changed, with updatedSince:The first successful sync of a connection carries firstSuccess: true: that's your cue for the initial pull. See Webhook events for the full pattern. 