Zixflow ACTION
Update Activity
Updates an existing activity or task in Zixflow. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Zixflow account once, then configure and run Update Activity 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: "zixflow-update-activity",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zixflow: { authProvisionId: "apn_xxxxxxx" },
activityId: "Activity ID",
iconType: "Icon Type",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "zixflow-update-activity",
"configured_props": {
"zixflow": { "authProvisionId": "apn_xxxxxxx" },
"activityId": "Activity ID",
"iconType": "Icon Type"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "zixflow",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "zixflow-update-activity",
arguments: {
activityId: "Activity ID",
iconType: "Icon Type",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
activityId Activity ID | string | The unique identifier for the activity or task Required Dynamic |
iconType Icon Type | string | Specifies the type of icon associated with the activity Optional |
iconValue Icon Value | string | Defines the specific value of the icon based on the iconType Optional Dynamic |
scheduleAt Schedule At | string | Specifies the scheduled time for the activity in the format YYYY-MM-DDTHH:mm:ss.SSSZ Optional |
name Activity Name | string | The name or title of the activity Optional |
description Description | string | A description providing additional details about the activity Optional |
statusId Status ID | string | The unique identifier for the status attribute. To get the Status ID, please use Get Activities action to get all activities, then investigate the status field in each record Optional Dynamic |
associationType Association Type | string | The association type. Optional Dynamic |
associatedId Associated ID | string | The ID of the collection record associated with the activity. 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
- zixflow-update-activity
- Version
- 0.0.2
- App
- Zixflow
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗