View as Markdown
Motion icon

Motion ACTION

Move Workspace

Move a specific task to another workspace. When moving tasks from one workspace to another, the tasks project, status, and label(s) and assignee will all be reset. See the documentation
  • Action
  • Writes data
  • Destructive
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Motion account once, then configure and run Move Workspace from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "motion-move-workspace",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    motion: { authProvisionId: "apn_xxxxxxx" },
    taskId: "Task Id",
    workspaceId: "Workspace Id",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Move Workspace inputs
Property Type Description
taskId Task Id string
The id of the task.
Required Dynamic
workspaceId Workspace Id string
The id of the workspace where the task is going.
Required Dynamic
assigneeId Assignee Id string
The user id the task should be assigned to.
Optional Dynamic

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
motion-move-workspace
Version
0.0.3
App
Motion
Authentication
API key
Read-only
No
Destructive
Yes
Open world
Yes