IntegrationsIntegrations overview
Integrations overview
Connect DoorOps to AI assistants, job systems and custom tools using native connectors, MCP, APIs and webhooks.
DoorOps integrations keep access within the authorised company and the signed-in person's permissions.
AI assistants
Connect Grok Bot, ChatGPT, Claude, Cursor or your own OpenAI API application to DoorOps through a custom MCP connection. Ask for job information, customer records, asset history and paperwork reviews, or prepare an authorised operational change for confirmation.
Use https://doorops.com/mcp/connect with OAuth. Your company needs MCP access enabled; provider plan requirements and workspace policies also apply. Start by asking the assistant which DoorOps company and role it is connected as.
| Assistant | Connection guide |
|---|---|
| Grok Bot and Grok web | Set up Grok Bot or Grok |
| ChatGPT | Create a custom DoorOps app |
| Claude | Add a custom connector |
| Cursor | Add a remote MCP server |
| OpenAI API | Use remote MCP in your application |
Your normal DoorOps role, validation and business safeguards remain in force. Review exact changes and consequences before approving creations, edits, sends, scheduling, merges or deletions. Revoke access under Settings → Connected apps. Read the MCP guide for scope, confirmations and troubleshooting.
Guidance checked 7 October 2026; each setup guide links its provider's current instructions. These are custom connections, with directory publication handled separately.
Native connectors
Verified, first-party connections. Use these when they match the system you already run.
| Provider | Core and Plus |
|---|---|
| Joblogic | Customer import, reviewed PDF handoff, historical import, encrypted archive, replay and event intake for already-imported jobs |
| eWorks Manager | Customer directory, historical import and archive-first mapping |
| BigChange | Contacts, REST historical import and optional separately licensed JobWatch handoff |
Provider credentials, API licensing and any managed setup are separate requirements. Legacy Lite retains its customer-directory and supported PDF handoff scope.
Native does not mean live two-way sync. Historical import and reviewed one-way delivery come first. Live sync is called out as not available until a provider contract exists.
If we do not have your system
That is the default path, not a gap you have to wait on.
Use build your own integration:
- REST API for reads and safe writes
- Signed webhooks so Door Ops tells your system when something changed
- Tenant MCP if the consumer is an AI agent
- CSV / structured file import for a one-off history dump
- Zapier, Make or Power Automate on top of the webhook + API pair
Accounting (Xero, Sage, QuickBooks) is the invoice and payment-status ledger. Quotes stay in Door Ops. Extra CRMs are on the roadmap. Until a native connector ships, the same public surfaces work.
Rules that never change
- Exact provider IDs, never fuzzy name matching
- Encrypted source archive for anything we cannot map 1:1
- Stripe entitlements gate commercial access
- Tenant roles still apply on top