stateful3 platforms2 source families

Orchestrate work in the field

Workmate

Workforce automation for people, clients, tasks, attendance, proof, and live operations.

Build dispatch and field-service systems around organizations, teams, workers, clients, tasks, shifts, location evidence, forms, and approvals. Workmate is journey-oriented: assignment, acceptance, execution, proof, exception handling, and completion are all first-class states.

What you can build

Capabilities

Worker and team managementProduction guidance, platform support, examples, and operational considerations included.01

Task assignment and dispatchProduction guidance, platform support, examples, and operational considerations included.02

Attendance and shift workflowsProduction guidance, platform support, examples, and operational considerations included.03

Client visits and proof of serviceProduction guidance, platform support, examples, and operational considerations included.04

Live operations and exceptionsProduction guidance, platform support, examples, and operational considerations included.05

Forms, evidence, and completion reportsProduction guidance, platform support, examples, and operational considerations included.06

Choose your surface

Available platforms

Keep business identifiers and server-side policy portable; use the native surface where device integration or long-lived state matters.

REST Android Web

Authentication

Organization and user-scoped access

Use service identities for dispatch integrations and user identities for worker actions; preserve the actor in every transition.

Use separate projects for development, staging, and production.
Apply the narrowest domain, IP, platform, product, and resource scopes available.
Never ship a server secret in a browser bundle, mobile binary, prompt, or public repository.

Copy, run, understand

Quickstart

Replace placeholders with credentials from the developer console. Examples include the lifecycle and failure-handling context that short snippets usually omit.

Workmate quickstart

{
  "externalId": "JOB-2026-004219",
  "type": "equipment_inspection",
  "assigneeId": "worker_1288",
  "location": { "mapplsPin": "MMI000" },
  "window": { "startsAt": "2026-08-17T04:30:00Z", "endsAt": "2026-08-17T06:30:00Z" },
  "requiredProof": ["arrival_location", "checklist", "photo", "customer_signature"]
}

Before productionRestrict and rotate credentialsHandle timeouts and typed errorsAdd tracing without logging secretsTest quota and degraded-mode behavior

Stateful integration

A field-service job end to end

Every transition is attributable, replayable, and safe to retry.

State · unassigned

Create

Attach client, site, SLA, skills, time window, and proof requirements.

task.created

State · assigned

Dispatch

Choose a qualified worker using proximity, load, shift, and route cost.

task.assigned

State · accepted

Accept

Worker accepts, rejects, or raises an availability exception.

task.accepted

State · en_route

Travel

Navigate to the site and notify operations of predicted SLA risk.

task.en_route

State · in_progress

Execute

Verify arrival, collect structured work evidence, and handle blockers.

task.started

State · completed

Close

Validate proof, obtain sign-off, sync downstream systems, and audit.

task.completed

Production state machines

Operate the complete lifecycle

These blueprints name every state, actor, command, event, invariant, durable record, retry boundary, failure recovery, source contract, and operational signal.

stateful

Field-service task lifecycle

Create, assign, accept, travel, prove, approve, and close a field job without losing actor, retry, or evidence history.

Browse all stateful journey blueprints

Traceable documentation

Source repositories

Reference content is reconciled against these public and private source families. Version, authentication generation, and maturity are recorded before content is promoted.

mapmyindia-workmate-apisREST API · legacy →mappls-workmate-android-sdkSDK · current →

Browse all 14 related integration guides