Assignar connector for civil contractors
Assignar is a field execution platform for civil contractors. It records site diaries, labour entries, equipment usage, safety inspections, allocations, and custom form submissions. Demiton integrates with Assignar to retrieve operational data, align it with financial systems, and write allocations back when scheduling workflows are active.
Authentication: OAuth 2.0 (client credentials)
System type: ASSIGNAR
API reference: Assignar API
See your Assignar data in Claude — book a 30-minute call.
Supported resources
Section titled “Supported resources”| Resource | FETCH | PUSH |
|---|---|---|
projects | ✓ Yes | — No |
workers | ✓ Yes | ✓ Yes |
assets | ✓ Yes | — No |
clients | ✓ Yes | — No |
suppliers | ✓ Yes | — No |
activities | ✓ Yes | — No |
allocations | ✓ Yes | ✓ Yes |
dockets | ✓ Yes | — No |
timesheets-expanded | ✓ Yes | — No |
leave-requests | ✓ Yes | — No |
pay-codes | ✓ Yes | — No |
competencies | ✓ Yes | — No |
skills | ✓ Yes | — No |
workers_with_competencies | ✓ Yes | — No |
workers_with_inductions | ✓ Yes | — No |
workers_with_skills | ✓ Yes | — No |
project_inductions | ✓ Yes | — No |
Dynamic forms (form_N_*) | ✓ Yes | — No |
Dynamic forms are discovered at runtime - each form configured in your Assignar account becomes a fetchable resource. Forms include site diaries, daily pre-starts, safety observations, incident reports, and any custom forms your organisation has created.
Registers this connector fills
Assignar keeps 32 registers current in Civil Memory , with 28 mapped to source fields. Each name is the record you ask for, not the system it came from - ask for it in Studio or from your own AI client.
| Register | What it holds | Fields from Assignar |
|---|---|---|
Site diarysite_diary | Daily site diaries: delays, weather, productivity, variations. | 18 of 24 |
Project listproject_list | Active and completed projects from your operational and ERP systems. | 13 of 18 |
Day works docketday_works_docket | Day works dockets for extra or variation work. | 10 of 26 |
Leave requestleave_request | Leave requests and their approval status. | 9 of 14 |
Safety incidentsafety_incident | Safety incidents and near misses on site. | 8 of 14 |
Safety ncrsafety_ncr | Non-conformance reports raised on site, for quality and safety. | 8 of 13 |
Health screeninghealth_screening | Fitness-for-work and fatigue screening results, by worker and project. | 7 of 13 |
Site inspectionsite_inspection | Vehicle and plant inspection checklists. | 7 of 15 |
Site requisitionssite_requisitions | Site requisitions for materials, plant or resources, by worker and project. | 7 of 15 |
Timesheet code listtimesheet_code_list | Timesheet and pay codes: award codes, allowances and the like. | 7 of 10 |
Maintenance recordmaintenance_record | Plant service and maintenance records. | 6 of 24 |
Plant prestartplant_prestart | Daily plant and equipment pre-start checks: condition, defects, compliance. | 6 of 20 |
Plant risk assessmentplant_risk_assessment | Plant and equipment risk assessments. | 6 of 21 |
Asset disposalasset_disposal | Plant and equipment written off, sold or scrapped. | 5 of 14 |
Equipment listequipment_list | The plant and equipment register across your operational systems. | 5 of 23 |
Competency verificationcompetency_verification | Verification-of-competency assessments per worker. | 4 of 10 |
Equipment assignmentequipment_assignment | Current and past equipment assignments to projects and sites. | 4 of 9 |
Induction onboardinginduction_onboarding | Site induction and onboarding acknowledgements. | 4 of 15 |
Leave category listleave_category_list | Leave types defined in your payroll and operational systems. | 4 of 33 |
Policy acknowledgementspolicy_acknowledgements | A worker's sign-off that a policy or procedure was read and accepted. | 4 of 13 |
Timesheet entrytimesheet_entry | Timesheet submissions, with hours by date and pay category. | 4 of 12 |
Allocationallocation | Who and what is rostered on which job, and when. | 3 of 15 |
Expense claimsexpense_claims | Employee expense claims, by worker and period. | 3 of 11 |
Toolbox talktoolbox_talk | Toolbox talks and pre-work safety meetings. | 3 of 20 |
Training recordstraining_records | Training logs and training requests, by worker. | 3 of 15 |
Compliance documentscompliance_documents | Safety and compliance documents attached to projects or workers. | 2 of 14 |
Employee hr recordsemployee_hr_records | HR record events for a worker: leave, disciplinary action, personnel file changes. | 2 of 27 |
Worker qualificationworker_qualification | Competencies, certificates and licences held by workers: rigging, EWP, first aid and so on. | 2 of 12 |
Project detailsproject_details | Details of active and completed projects from your operational and ERP systems. | Fills all of 11 |
Site activitysite_activity | Daily site activity: crew, plant and progress. | Fills all of 9 |
Subcontractor listsubcontractor_list | Subcontractors engaged on your projects. | Fills all of 18 |
User listuser_list | Users in your identity directory and operational systems. | Fills all of 13 |
The full field list, requiredness and an example record for any register are on its published contract. Where more than one system fills a register, the register is the same shape either way.
Integration model
Section titled “Integration model”Authentication uses OAuth 2.0 client credentials. Records are normalised into the platform’s standard response wrapper before entering the workflow runtime.
The adapter supports a range of enrichment resources (workers_with_competencies, workers_with_inductions, workers_with_skills, project_inductions) that join Assignar data server-side to produce pre-joined datasets. For large datasets, the adapter uses progress callbacks and fan-out batch operations.
Dynamic value resolution is supported - parameters like NOW_MINUS_30_DAYS are resolved at execution time, so workflow templates can reference relative time windows without hardcoded dates.
Target any Assignar form by its form ID:
FETCH → assignar.form_37 params: form_id: 37An all-forms sweep fetches submissions across every form in your account, useful for building a unified document index.
Labour extraction
Section titled “Labour extraction”Labour entries appear within site diary records. A transform step extracts them as structured records:
FETCH → assignar.timesheets-expandedTRANSFORM → extract_labour_entriesEach LabourEntry includes: worker, project, date, hours, cost category.
Typical pipeline
Section titled “Typical pipeline”FETCH → assignar.site_diaryTRANSFORM → extract_labour_entriesTRANSFORM → normalize_cost_categoriesGOVERN → validate_project_mappingPUSH → business_central.profit_and_lossConnection setup
Section titled “Connection setup”Assignar uses OAuth 2.0 client credentials - no redirect is needed. Provide the Client ID and Client Secret for the API user that acts for Demiton. Use a dedicated API user to simplify credential rotation and audit.
Security
Section titled “Security”Access type: Read and governed write (allocations and worker records)
Demiton reads the full range of operational data from Assignar. Writes are scoped to two resources: allocations (scheduling workflows) and workers (workforce lifecycle workflows). Demiton does not modify project definitions, form configurations, safety records, or any other Assignar data.
Permissions required: OAuth 2.0 client credentials with access to your Assignar organisation. Use a dedicated API user for Demiton to simplify credential rotation and audit.
Data sensitivity: Assignar data is classified as operational domain - broadly visible within your operational team, but subject to Demiton’s identity-bound access controls.
Next steps
Section titled “Next steps”- Connecting a System - step-by-step wizard for setting up the connector
- Business Central - the typical partner integration: Assignar labour entries cross-posted to BC project ledger
- KeyPay - reconcile Assignar allocations against payroll records
- MCP Server - query site diaries, workforce, and allocations through Claude once connected
- Connect your operation - talk to us about scoping a Connected deployment
Frequently asked questions
- What data does the Demiton Assignar connector read?
- The Demiton Assignar connector reads site diaries, labour entries, timesheets, allocations, leave requests, worker competencies and inductions, plant and equipment, project and client data, and dynamic form submissions. Labour entries are extracted from site diary records as structured LabourEntry objects (worker, project, date, hours, cost category). Dynamic forms - safety inspections, pre-starts, incident reports - are all fetchable.
- Can Demiton write to Assignar?
- Yes. Demiton supports governed writes to two Assignar resources: allocations (used in scheduling workflows) and workers (used in workforce lifecycle workflows). All writes go through committed, audited workflow runs. Demiton does not modify project definitions, form configurations, or safety records in Assignar.
- How does the Assignar connector work with Business Central?
- The most common pipeline is: FETCH from Assignar site diaries, TRANSFORM to extract labour entries and normalise cost categories, PUSH to Business Central project ledger entries. This reconciles field activity against project financials. Discrepancies between Assignar hours and Business Central costs are surfaced as variance records.
- What tier is required for the Assignar connector?
- The Assignar connector requires the Connected tier (AU$50,000/year). It connects to your own Assignar organisation using OAuth 2.0 client credentials. A dedicated API user is recommended to simplify credential rotation and audit.
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.