OneOps
Connectors

Sync and schedules

Sync rules, running more than one rule per source, and how data is normalized into a common schema.

A sync is a pull that brings external records into the platform and keeps them current. This page covers how syncs are configured and what happens to the data.

Sync rules

A sync rule describes one repeating pull. Each rule has:

  • A source. The connector it pulls from.
  • A schedule. How often it runs.
  • A scope. The window and the records it covers.
  • A destination. Where the records land inside the platform.

A scheduled sync uses the span since its last successful run, so it picks up only what is new.

Multiple rules per source

A single source can have more than one sync rule. That lets you pull different kinds of records on different cadences (for example, frequent trip updates and a slower nightly pull of reference data) without forcing everything onto one schedule.

How data is normalized

Records from every source are normalized into a common schema as they come in. That is what lets Agentic Studio, intelligence dashboards, and the rest of the platform use your data the same way no matter which system it came from.

When a sync runs, it fetches the records for its window, reconciles them against what is already stored (inserting, updating, or skipping rather than duplicating), records the outcome and counts, and notifies downstream tools if anything changed.

See also

Connecting a source

The guided setup flow, managing credentials, and requesting a custom integration.

Connector health

Sync status states, the sync log, and what to do about common errors.