> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/update-item.md).

# Update Easit Item (Legacy Import Handler)

Create or update through an existing Easit Integration API Import Handler. Its OK result does not confirm that an item matched or changed.

**Action identifier:** `update_item`.

### Inputs

| Field                       | Type           | Required/default | Meaning                                                                                                                                                                                     |
| --------------------------- | -------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `import_handler_identifier` | string         | Required         | The identifier of the import handler (configured in Easit GO)                                                                                                                               |
| `item_id`                   | string \| null | `null`           | Case/item ID used by the import handler's search step to find the item to update. Sent as the id\_property param (default property0). Leave empty only when the handler creates a new item. |
| `id_property`               | string         | `"property0"`    | Name of the import-handler input param that carries the match ID (default 'property0').                                                                                                     |
| `properties`                | object         | Required         | Import-handler input params (e.g. {'property1': ''}) mapped to values. Keys are positional param names the handler expects, not business field names.                                       |

Example input:

```json
{
  "import_handler_identifier": "BPECustomerImport",
  "item_id": "9457",
  "properties": {
    "property1": "Updated from workflow"
  }
}
```

### Output

Paths are relative to this action's output. Select them from the builder's variable picker rather than typing them. A field that is null or empty was not returned by Easit; it is not proof that the value is empty in Easit.

| Path      | Type           | Meaning                                                                             |
| --------- | -------------- | ----------------------------------------------------------------------------------- |
| `success` | boolean        | Whether Easit returned OK; this does not confirm that an item matched or changed.   |
| `uid`     | string         | Easit result uid, the requested item identifier, or an empty string if unavailable. |
| `result`  | string         | Easit import result code or a failure code.                                         |
| `error`   | string \| null | Failure details when the operation did not succeed; otherwise null.                 |

### Behavior and limits

Invokes an existing Easit Integration API Import Handler. Supply `import_handler_identifier` and `properties`, a map of the handler's positional input names (such as `property1`) to string values.

For updates, supply `item_id` using the identifier expected by the handler's search step. `id_property` names that input parameter and defaults to `property0`. Omit `item_id` only when the handler is intentionally configured to create an item. Use input parameter names, not GraphQL field system names.

Returns `success`, `uid`, `result`, and an optional `error`. Easit's `OK` result does not prove that an item matched or changed; read back or verify in Easit.

Keep this action for existing customer import-handler contracts. New field updates should use GraphQL. Requires permission to invoke the configured handler.

See [Troubleshooting](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/troubleshooting.md), or return to the [action catalog](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions.md).
