Skip to main content
Door Ops
Free trial

Try Door Ops free. No card. No automatic charge. Build better door-company software with us.

Free beta & paid plans

IntegrationsBuild your own integration

Build your own integration

Connect any CRM, accounts pack, phone system or job tool using the public Door Ops surfaces. You do not wait for a native connector.

Door Ops ships native connectors only when the provider contract is verified (Joblogic, eWorks Manager, BigChange today).

For everything else, you can integrate yourself. That is allowed on purpose. We will not make you wait for a Door Ops-built adapter before you can move data.

Pick a surface

You are...Use
Syncing records on a scheduleREST API with an organisation API key
Reacting when a job, form or invoice changesOutbound webhooks
Driving DoorOps from Grok Bot, ChatGPT, Claude or CursorAI integrations and setup guides
Doing a one-off history dumpSettings → Integrations → file import
Using Zapier, Make or Power AutomateWebhook in, API out

Access depends on your company's enabled features and your role. API keys, outbound webhooks and AI Agent Access have separate access requirements. Check your account or contact DoorOps if you need a feature enabled. Existing packages keep their agreed access.

A typical custom job-system bridge

  1. Create an API key in Settings → Developers with the smallest scopes you need (customers:read, jobs:write, and so on).
  2. Create customers and sites in Door Ops (or import them) so forms and jobs have parents.
  3. When your other system raises a callout, POST /api/v1/jobs (or create the job in the UI and store the Door Ops id on your side).
  4. Subscribe a webhook for job.updated / form events so your system sees completion without polling.
  5. Verify X-DoorOps-Signature (HMAC) and de-duplicate on X-DoorOps-Delivery.

Door Ops will not delete records over the API. Archive in your own system if you need a two-way cleanup.

Telephony and fleet without a native adapter

The API already has provider-neutral endpoints:

  • POST /api/v1/telephony/calls with telephony:write
  • POST /api/v1/fleet/vehicle-locations with fleet:write

Send exact Door Ops or previously migrated provider IDs in links. Door Ops will not guess a customer from a phone number or a vehicle from a name.

What we will not do

  • Fuzzy-match customers by name or address
  • Schedule work, send a customer message or change a quote without reviewing the exact proposal and getting human confirmation
  • Let an AI assistant certify a door or invent an inspection, signature or approval
  • Store your other system's passwords in Door Ops so we can scrape it

If you later want a first-party connector, we still need the provider's API docs, a sandbox, and a written scope. Until then, this page is the supported path.