Joblogic

Active

An AI agent for Joblogic. It works in a scene with a live connection to Joblogic. It asks before it writes, and every run is traced.

Connect Daslab scenes to Joblogic. Pin a job or a site and see it live, search the asset register and forms logbook, and write back — create jobs, move statuses, book visits, and attach notes so the office and the engineer both see what an agent found.

Data & Databases Custom 4 asset types

What you can connect

Add these to your scene and AI gets access.

Joblogic Account Joblogic Accounts

A Joblogic tenant, connected via client credentials and a tenant id.

NameEnvironment

Job Jobs

A Joblogic job — reactive or PPM work at a customer site.

Job NumberCustomerSiteStatus

Site Sites

A customer site in Joblogic — where jobs are carried out and assets live.

NamePostcodeRegion

Guide Guides

Joblogic setup guides, troubleshooting, and reference — pin one to read it in-scene, or ask the agent.

TitleSummary

Connect Joblogic over MCP

Daslab is itself an MCP server.

Connect Joblogic in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your Joblogic tools, and your approval gate and trace travel with them.

https://daslab.run/mcp/<your-world>/<your-scene>

One scene can hold Joblogic and everything else you connect, so a single endpoint carries them all. Set up a client.

Use cases

Pin a job and watch its status, engineer, and appointment
Turn an inbound request or a detected fault into a scheduled job and visit
Reconcile the asset register and compliance forms across sites

Knowledge base

Getting Joblogic API access api-access
The API Access app, client-credentials auth, tenant ids, IP allowlisting, rate limits, and the UAT environment.
Data model & endpoint map data-model
How Joblogic's entities fit together, the GetAll/GetById/PUT convention shared by ~70 entity groups, and the ids and dates to expect.
Integration patterns integration-patterns
Work in / actuals out, and fault → job → visit → certificate, written as agent flows over the tools this provider exposes.

Ships with the integration — agents read these with docs_read, before the account is connected. Knowledge bases →