Skip to content

Integrations

Connect Mission Planning Workflow to your systems

Each integration Mission Planning Workflow supports: what flows, how fields map, and the steps to set it up.

Applies to Mission Planning Workflow as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 4 min readReport a problem
On this page
  1. Maps and geospatial systems
  2. Steps to set it up
  3. Unit and equipment data
  4. Steps to set it up
  5. Plan exchange formats
  6. Steps to set it up
  7. Moving plans between workspaces
  8. Steps to set it up
  9. Identity and sign-in
  10. Steps to set it up
  11. Tactical edge infrastructure
  12. Steps to set it up
  13. Work API
  14. Steps to set it up
  15. Using the Work API

How Mission Planning Workflow connects to your other systems. Every connection is confirmed during discovery and specified in the design before it is built.

Maps and geospatial systems

The product has no map engine and stores no maps, imagery, overlays or coordinates; planners describe places in text and measure distances in your own authorized systems.

  • What flows: In: place names and distances entered by planners.
  • Mapping: Place names or descriptions map to location_description on the mission plan.

Steps to set it up

  1. This product has no map engine and stores no map data, overlays or coordinates.

  2. Keep maps and geospatial planning in your organization's authorized systems, and describe locations in Location description.

Unit and equipment data

Resources, checklist items and movement legs loaded by CSV import or through the Work API from your own systems, or entered by planners.

  • What flows: In: resources, checklist items and movement legs.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Plan exchange formats

Approved plans exported as a JSON package (format moraph-mission-plan-package) and a printable HTML file, for other approved systems to read.

  • What flows: Out: plan, phases, checklist, resources, movement legs with calculated times, sustainment estimate and reviews. In: packages from another workspace, imported as draft plans.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Moving plans between workspaces

There is no sync: a JSON package downloaded in one workspace is carried on approved media and imported in another as a new draft plan.

  • What flows: In and out: JSON packages; reviews and approvals are not carried over.
  • Mapping: Package plan fields, phases, checklist items, resources, movement legs, risks, decision points and communications lines map to new records; reviews, approvals, risk acceptances, decisions made and lessons are not carried over.

Steps to set it up

  1. Download the JSON package in one workspace and carry it on approved media.

  2. Import it under Import and verify in the other; it arrives as a new draft plan.

Identity and sign-in

Users sign in to Moraph Apps through single sign-on at portal.moraph.com; there is no sign-in on a device and no smart card support.

  • What flows: In: user identity; product roles are granted in the Moraph Portal.
  • Mapping: Agreed in the integration design.

Steps to set it up

  1. Agree the scope of the connection with Moraph during design.

  2. Provide access to the system being connected.

  3. Test the connection in a non-production environment before go-live.

Tactical edge infrastructure

The product installs nothing on devices; approved packages can be carried on approved media to edge devices your unit manages, including with Moraph's Tactical Edge Compute Node Manager.

  • What flows: Out: export package files, carried on approved media.
  • Mapping: Through the Work API, CSV import or the product’s exports, as agreed during implementation; the product doesn’t connect to the other system itself.

Steps to set it up

  1. Agree with Moraph which records and fields move, and in which direction.

  2. Create a Work API key with only the scopes needed, or prepare the CSV layout.

  3. Test with sample records before go-live.

Work API

Plans, phases, checklist items, resources, movement legs and reviews are available to your reporting and archive systems through the Moraph Work API.

  • What flows: Out: plan versions with their approval fields, and the records linked to them. In: checklist items and resources.
  • Mapping: Plans, phases, checklist items, resources, movement legs and reviews map to records by field key. Records can't be created straight into a stage the product reaches only by its own steps (a plan in review or approved, an answered review without a recommendation), and approval can't be recorded through the Work API. Internal keys are not returned.

Steps to set it up

  1. Create a key under Work API keys with records:read for reporting, or records:write to load checklist items or resources from another system.

  2. Read and write records by field key; the same rules apply as in the product.

Using the Work API

Systems that aren't covered above can read and write Mission Planning Workflow records through the Sign in to read Work API. For example, to create a mission plan:

http
POST https://apps.moraph.com/api/v1/records
Authorization: Bearer mrph_…
Content-Type: application/json
Idempotency-Key: 7f3c2a90-example

{ "type": "mission_plan", "title": "Example title", "fields": { "operation_or_activity": "…" } }

Field keys are listed in the Sign in to read workspace reference. Request formats, paging and errors are in the Sign in to read Work API reference.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.