Skip to main content
Jobs move data between connections. A Job selects a source and destination, tables to sync, optional transforms, sync mode, schedule, and execution mode (Hosted or Agent). Each execution is a run with progress, events, and history.
Match projects under Match → Projects are not sync Jobs. Use Jobs to move data; use Match to resolve duplicate entities.
In the sidebar, Jobs sit under the Data group (with Connections and Files), not under Know / Trust / Match.

​
Open Jobs

  1. Select Data → Jobs.
Page title: Jobs. Primary action: New Job. Search placeholder: Search jobs…. Status chips filter the list. Empty state: No sync jobs yet (A job connects a source to a destination and keeps your data in sync on a schedule.) with + New Job.

​
Create a Job

  1. Data → Jobs → New Job (page title New job).
  2. Complete the wizard steps in order:
  1. On Configure, set sync mode, destination write mode, schedule, retries / workers, and execution mode as needed.
  2. Under advanced options, Job Type is ETL or Reverse ETL.
  3. Click Create Job.
Typical sequence after create: open the Job → Rerun (or wait for schedule) → inspect Runs / View Logs. See ETL pipelines and Reverse ETL for mode detail.

​
Job detail

Open a Job from the list. Tabs:

​
Tables

  • Filter by status with the chip group.
  • Search table names.
  • + Add Table opens Add Tables.
  • Selection actions: Rerun N, Remove N.

​
Runs

  1. Review run history.
  2. Click View Logs for Events & Logs (/jobs/{id}/events).
  3. If there are no runs: No runs yet — Rerun this job to create the first execution. → Rerun job.

​
Common actions

​
Jobs vs Match projects

Last modified on October 10, 2026