---
title: "Move Node"
description: "'Effortlessly move nodes in workflows to target containers using node IDs or paths with this flexible handler.' (Gitana 4.0)"
product: "Gitana"
version: "4.0"
url: "/documentation/gitana/4.0/engine/workflow/workflow-handlers/move-node"
---

# Move Node

Type: `moveNode`

This handler moves nodes that are part of a workflow's payload to a target container. The target container can be identified either by a node ID or a node path.

The `config` for this handler is as follows:

```
{
    "targetNodeId": "<target node id>",
    "targetOffsetPath": "<target path>"
}
```

If `targetOffsetPath` is specified, then `targetNodeId` is the root node to calculate the offset against. If `targetNodeId` is not provided, the default repository root is used.

Here is an example where we move a node to the `/Content/Published` folder.

```
{
    "targetOffsetPath": "/Content/Published"
}
```

This is equivalent to:

```
{
    "targetNodeId": "root",
    "targetOffsetPath": "/Content/Published"
}
```

We can also move to a specific node identified by its node ID or its QName:

```
{
    "targetNodeId": "ABCDEFGH123456"
}
```

Or:

```
{
    "targetNodeId": "custom:content_published"
}
```

Finally, you can do relative offsets. Suppose the `/Content` folder has node ID `XYZABC1234987`:

```
{
    "targetNodeId": "XYZABC1234987",
    "targetOffsetPath": "/Published"
}
```

## See Also

- The [Move Node](/documentation/gitana/4.0/engine/behaviors/actions/move-node.md) action