View as Markdown
HubSpot icon

HubSpot ACTION

Get Actor

Resolves an actor ID (e.g. the value returned by a message's senders[].actorId field) to its name, email, and type. See the documentation
  • Action
  • Read only
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's HubSpot account once, then configure and run Get Actor 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-get-actor",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    hubspot: { authProvisionId: "apn_xxxxxxx" },
    actorId: "Actor",
  },
})

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.

Get Actor inputs
Property Type Description
actorId Actor string
The HubSpot Conversations actor ID to resolve. Accepts a HubSpot owner ID or a fully-qualified actor ID with type prefix: A-12345 (owner/agent), I-67890 (integration), B-11111 (bot), S-... (system), V-... (visitor), E-... (email), L-... (LLM). Owner IDs without a type prefix are auto-prefixed with A-. Actor IDs typically appear in a message's senders[].actorId field.
Required 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
hubspot-get-actor
Version
0.0.5
App
HubSpot
Authentication
OAuth
Read-only
Yes
Destructive
No
Open world
Yes