# Joblogic

Joblogic is the first native job-system connector.

## What you need

Joblogic API access is **not** your Joblogic login. Ask Joblogic for a Client ID, client secret and tenant ID. DoorOps calls from published egress IPs that Joblogic must allow.

Use UAT credentials for a dry run before production.

## Lite

Connect, test, and import the customer directory (customers, contacts, sites) so new DoorOps forms already have names attached.

## Growth

Full historical import with an encrypted source archive. The picker is staged on purpose. A full Joblogic account can take hours because the API allows 100 requests a minute and many child records are fetched per parent.

Recommended order:

1. Customers, contacts and sites
2. Assets and contracts
3. Engineers, parts and suppliers
4. Jobs and field history
5. Quotes and invoices

Run **Check this run** before you queue. DoorOps reads live counts and estimates duration. Do not start a second import on the same connection while one is running. You can cancel and resume from a checkpoint.

Archive-only preview fetches and stores source records without creating DoorOps customers or jobs. Turn on operational mapping once you are happy with the archive.

Child endpoints that return HTTP 400 or 404 are skipped. They do not abort the rest of the run.

## Reviewed PDF handoff

A reviewed DoorOps PDF can be matched to an **exact** Joblogic job and queued as a provider note attachment. No fuzzy job search.

## Events

Joblogic support configures the callback URL. DoorOps refreshes only jobs that already mapped. Unmatched events stay in the event ledger.