View as Markdown
HubSpot icon

HubSpot TRIGGER

New Contact Property Change

Emit new event when a specified property is provided or updated on a contact. See the documentation
  • Trigger
  • Polling
  • OAuth
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's HubSpot account, configure the source, and choose the webhook where your backend receives events.

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 deployed = await pd.triggers.deploy({
  id: "hubspot-new-contact-property-change",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    hubspot: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    property: "Property",
  },
  webhookUrl: "https://example.com/webhooks/hubspot",
})

console.log(deployed.id)

MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.

SCHEMA

Configuration

These inputs define which events the source watches. Dynamic options are loaded from the connected account.

New Contact Property Change configuration
Property Type Description
timer Timer $.interface.timer
Required
property Property string
The contact property to watch for changes
Required Dynamic
skipFirstRun Skip existing contacts when first activated boolean
When enabled, this trigger will ignore all existing contacts and only watch for property changes that happen after activation. When disabled, it will process all existing contacts on first run.
Optional
requirePropertyHistory Only trigger on actual property changes boolean
When enabled, only fires when a contact property is actually modified. When disabled, may also trigger for newly created contacts even if the property wasn't changed.
Optional
fetchAllProperties Fetch all contact properties boolean
When enabled, fetches all available contact properties instead of just the watched property. This provides complete contact data but may increase API usage.
Optional

01

Connect

Your user authorizes HubSpot through Pipedream managed auth.

02

Deploy

Your backend deploys this source with that user's own configuration.

03

Webhook delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.

OR

On-demand retrieval

No webhook required. Your app or agent can fetch recent events from the trigger events API.

Registry key
hubspot-new-contact-property-change
Version
0.0.41
App
HubSpot
Authentication
OAuth
Delivery
Polling source
Output
Events emitted by HubSpot.