Freshchat ACTION
Update Conversation
Updates a conversation's status, assignment, or properties. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Freshchat account once, then configure and run Update Conversation 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: "freshchat-update-conversation-status",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
freshchat: { authProvisionId: "apn_xxxxxxx" },
userId: "User ID",
conversationId: "Conversation ID",
},
})
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": "freshchat-update-conversation-status",
"configured_props": {
"freshchat": { "authProvisionId": "apn_xxxxxxx" },
"userId": "User ID",
"conversationId": "Conversation ID"
}
}'// 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": "freshchat",
},
},
},
)
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: "freshchat-update-conversation-status",
arguments: {
userId: "User ID",
conversationId: "Conversation ID",
},
})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 |
|---|---|---|
userId User ID | string | The ID of a user Required Dynamic |
conversationId Conversation ID | string | The ID of a conversation Required Dynamic |
status Status | string | Status of the conversation Required |
agentId Agent ID | string | The ID of an agent to assign the conversation to. Required if status is assigned. Pass empty string to unassign. Optional Dynamic |
groupId Group ID | string | The ID of a group to assign the conversation to. Pass empty string to unassign. Optional Dynamic |
priority Priority | string | Priority level of the conversation Optional |
customProperties Custom Properties | object | Custom conversation properties as key-value pairs. Keys should be prefixed with cf_. Example: {"cf_department": "Sales", "cf_region": "West"} Optional |
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
- freshchat-update-conversation-status
- Version
- 0.0.5
- App
- Freshchat
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗