Actions92
- User Actions
- Task Actions
- Add Comment
- Add Manual Work Period
- Change Board
- Change Project
- Change Time Worked
- Change Type
- Clone
- Complete Workflow Step
- Create
- Create Assignments
- Delete
- Deliver
- Get
- Get Fields
- Get Form Answers
- Get Many
- Get Subtasks
- Mark As Urgent
- Move
- Move To Next Stage
- Move To Top
- Pause
- Play
- Reestimate
- Reopen
- Reposition
- Share
- Undo Workflow Step
- Unmark As Urgent
- Unshare
- Update
- Update Comment
- Team Actions
- Projects Actions
- Board Stages Actions
- Comments Actions
- Documents Actions
- Checklists Actions
- Checklist Items Actions
- Clients Actions
- Descendants Actions
- Time Worked Actions
Task → Move
AI-generatedSummary
Moves a Runrunit task by sending a request to the Runrunit API for the given task ID, with an optional JSON payload carrying the move details. It can also return a curl preview instead of making the call.
Inputs
- Mode — 'Execute request' (default) calls the Runrunit API. 'Preview curl' only shows the curl command and does not run the request.
- Task ID (required) — ID of the task to move.
- Payload (JSON) — Optional JSON object, default {}. It is sent as the request body under the
dataproperty. Put the move parameters your Runrunit account expects here, for example the target location. The node doesn't declare the fields.
Output shape
One output item per input item, holding the Runrunit API response for the move. In Preview mode it holds the curl command instead.
The source pack contains only signature-level stubs for the executors, so the exact HTTP method, endpoint path and response shape could not be confirmed. The payload fields are not defined in the node, so check the Runrunit API docs for what a move accepts.
Examples
Example 1: Preview the move request before running it
Mode: Preview curl; Task ID: the task's ID; Payload: {}
Example 2: Move a task using details from an earlier step
Mode: Execute request; Task ID: {{$json.id}}; Payload: JSON with the move parameters required by the Runrunit API