Assignar
Assignar is the field execution platform used by most Demiton construction deployments. 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
Supported resources
| Resource | FETCH | PUSH |
|---|---|---|
projects | ✓ | |
workers | ✓ | ✓ |
assets | ✓ | |
clients | ✓ | |
suppliers | ✓ | |
activities | ✓ | |
allocations | ✓ | ✓ |
dockets | ✓ | |
timesheets-expanded | ✓ | |
leave-requests | ✓ | |
pay-codes | ✓ | |
competencies | ✓ | |
skills | ✓ | |
workers_with_competencies | ✓ | |
workers_with_inductions | ✓ | |
workers_with_skills | ✓ | |
project_inductions | ✓ | |
Dynamic forms (form_N_*) | ✓ |
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.
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.
Forms
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
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
FETCH → assignar.site_diariesTRANSFORM → extract_labour_entriesTRANSFORM → normalize_cost_categoriesGOVERN → validate_project_mappingPUSH → business_central.project_ledger_entriesSecurity
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
- 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