Action targets - ION Manual

Action Targets Documentation

An action’s target field names the entity type whose create, update, or delete events trigger the action. This page lists the targets grouped by domain, then maps each target to the singular query name you use in a context query and the key that entity’s changes appear under. It covers commonly-used entities and is not exhaustive. For how targets fit into an action’s other fields, see the ION Actions overview.

The target and field catalogs here reflect commonly-used entities. The authoritative, current list is what the Actions editor dropdown offers and what GraphiQL introspection returns in your environment.

Available targets

Core manufacturing

Parts and inventory

Procedures and steps

Bill of materials

Issues and quality

Procurement

Approvals

Redlines

Planning

Locations and organization

Users and teams

Other entities

Barcodes

Webhooks and notifications

Datagrid

Context query names

A context query uses the singular camelCase form of the target as its top-level query name. The entity’s changes appear in the changes dict under its own key. This table maps each target to both.

Composite-ID (joiner) entities

Some entities have compound primary keys instead of a single $id. For these, pass the composite ID parameters the entity expects.

The abomInstallation joiner takes a build requirement ID and a part inventory ID:

{
  abomInstallation(buildRequirementId: $buildRequirementId, partInventoryId: $partInventoryId) {
    quantity
    buildRequirement { quantity }
  }
}

The partKitInventory joiner takes a part inventory ID and a part kit item ID:

{
  partKitInventory(partInventoryId: $partInventoryId, partKitItemId: $partKitItemId) {
    partInventory { serialNumber }
  }
}