> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/mutations/updatepickingoutboundshipmentnotification.md).

# Update Picking Outbound Shipment Notification

updatePickingOutboundShipmentNotification Mutation

Audience: Programmer

Updates an existing `PickingOutboundShipmentNotification`. This allows modification of the notification's custom data, data type, and parent order association.

## Arguments

| Name    | Type                                              | Description                               |
| ------- | ------------------------------------------------- | ----------------------------------------- |
| `id`    | `ID!`                                             | Required ID of the notification to update |
| `input` | `UpdatePickingOutboundShipmentNotificationInput!` | Input data for updating the notification  |

## Return Type

`PickingOutboundShipmentNotificationOutput` - Contains the updated notification and any associated workflows.

## Input Fields

`UpdatePickingOutboundShipmentNotificationInput`:

| Field               | Type      | Description                                        |
| ------------------- | --------- | -------------------------------------------------- |
| `dataTypeID`        | `UUID`    | Optional data type ID for custom validation        |
| `clearDataTypeID`   | `Boolean` | Clear the current data type ID                     |
| `dataTypeSlug`      | `String`  | Optional data type slug for custom validation      |
| `clearDataTypeSlug` | `Boolean` | Clear the current data type slug                   |
| `data`              | `Map`     | Custom JSONB data associated with the notification |
| `clearData`         | `Boolean` | Clear all custom data                              |
| `orderID`           | `ID`      | ID of the parent picking order                     |

## Response Fields

`PickingOutboundShipmentNotificationOutput`:

| Field                                 | Type                                  | Description                           |
| ------------------------------------- | ------------------------------------- | ------------------------------------- |
| `pickingOutboundShipmentNotification` | `PickingOutboundShipmentNotification` | The updated notification              |
| `workflows`                           | `[TemporalWorkflow]`                  | Any workflows triggered by the update |

## Usage Example

```graphql
mutation {
  updatePickingOutboundShipmentNotification(
    id: "550e8400-e29b-41d4-a716-446655440000",
    input: {
      data: {
        "carrier": "DHL",
        "tracking_number": "TRK987654321-UPDATED",
        "shipped_at": "2026-04-10T12:00:00Z",
        "delivery_eta": "2026-04-12T09:00:00Z",
        "notes": "ETA updated after carrier handoff"
      }
    }
  ) {
    pickingOutboundShipmentNotification {
      id
      orderID
      data
      updatedAt
      updatedBy
    }
    workflows {
      id
      type
      runID
      status
    }
  }
}
```

## JavaScript Example

```javascript
const updateMutation = `
  mutation UpdatePickingOutboundShipmentNotification(
    $id: ID!,
    $input: UpdatePickingOutboundShipmentNotificationInput!
  ) {
    updatePickingOutboundShipmentNotification(id: $id, input: $input) {
      pickingOutboundShipmentNotification {
        id
        orderID
        data
        updatedAt
      }
      workflows {
        id
        type
        runID
        status
      }
    }
  }
`;

const variables = {
  id: "550e8400-e29b-41d4-a716-446655440000",
  input: {
    data: {
      carrier: "DHL",
      tracking_number: "TRK987654321-UPDATED",
      shipped_at: "2026-04-10T12:00:00Z",
      delivery_eta: "2026-04-12T09:00:00Z",
      notes: "ETA updated after carrier handoff"
    }
  }
};

const response = await fetch('/graphql', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer YOUR_TOKEN'
  },
  body: JSON.stringify({ query: updateMutation, variables })
});

const result = await response.json();
console.log('Updated notification:', result.data.updatePickingOutboundShipmentNotification);
```

## Notes

* The notification must exist and be accessible to the current user.
* Use `clearData`, `clearDataTypeID`, or `clearDataTypeSlug` to explicitly remove existing values.
* Updates may trigger associated Temporal workflows; inspect the `workflows` field in the response.
* The `orderID` field can be reassigned, but it must reference a valid, accessible picking order.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/mutations/updatepickingoutboundshipmentnotification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.