View as Markdown
HubSpot icon

HubSpot ACTION

Update Thread

Updates an existing thread's status. To archive a thread, use the Archive Thread action; to restore an archived thread, use the Unarchive Thread action. HubSpot's PATCH endpoint does not support either operation via a status change. See the documentation
  • Action
  • Writes data
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's HubSpot account once, then configure and run Update Thread 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: "hubspot-update-thread",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    hubspot: { authProvisionId: "apn_xxxxxxx" },
    inboxId: "Inbox ID",
    channelId: "Channel 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.

Update Thread inputs
Property Type Description
inboxId Inbox ID string
The ID of an inbox
Optional Dynamic
channelId Channel ID string
The ID of a channel
Optional Dynamic
threadId Thread ID string
The ID of a thread
Required Dynamic
status Status string
Set to OPEN to reactivate a closed thread or CLOSED to mark it as resolved
Required

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
hubspot-update-thread
Version
0.0.5
App
HubSpot
Authentication
OAuth
Read-only
No
Destructive
No
Open world
Yes