# New Engagement — HubSpot

> Emit new event for each new engagement (call, email, meeting, note, postal mail, or task) created. Per-activity docs: Calls Emails Meetings Notes Postal Mail Tasks See the documentation

- Key: `hubspot-new-engagement`
- Type: Trigger (Polling)
- Version: 0.0.51
- App: HubSpot (`hubspot`) — https://pipedream.com/apps/hubspot.md
- This page (HTML): https://pipedream.com/apps/hubspot/triggers/new-engagement
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/hubspot/sources/new-engagement/new-engagement.mjs

## Description

Emit new event for each new engagement (call, email, meeting, note, postal mail, or task) created. Per-activity docs: [Calls](https://developers.hubspot.com/docs/api-reference/latest/crm/activities/calls/search/search-calls) [Emails](https://developers.hubspot.com/docs/api-reference/latest/crm/activities/emails/search/search-emails) [Meetings](https://developers.hubspot.com/docs/api-reference/latest/crm/activities/meetings/search/search-meetings) [Notes](https://developers.hubspot.com/docs/api-reference/latest/crm/activities/notes/search/search-notes) [Postal Mail](https://developers.hubspot.com/docs/api-reference/latest/crm/activities/postal-mail/search/search-postal-mail) [Tasks](https://developers.hubspot.com/docs/api-reference/latest/crm/activities/tasks/search/search-tasks) [See the documentation](https://developers.hubspot.com/docs/api-reference/latest/crm/using-object-apis)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `timer` | `$.interface.timer` | Yes | Timer |
| `types` | `string[]` | No | Filter results by the type of engagement. Defaults to all types. |

## Returns

Events emitted by HubSpot.

## Run it

**TypeScript**

```ts
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-engagement",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    hubspot: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    types: ["Engagement Types"],
  },
  webhookUrl: "https://example.com/webhooks/hubspot",
})

console.log(deployed.id)
```

**cURL**

```bash
curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "hubspot-new-engagement",
    "webhook_url": "https://example.com/webhooks/hubspot",
    "configured_props": {
      "hubspot": { "authProvisionId": "apn_xxxxxxx" },
      "timer": { "intervalSeconds": 900 },
      "types": ["Engagement Types"]
    }
  }'
```

**MCP**

MCP servers expose HubSpot actions as on-demand tools.

New Engagement is an event source, so your application deploys it with the Connect SDK or API and then either receives each event at a webhook URL or retrieves events on demand with the trigger events API.

## Event delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source. Or: no webhook required — your app or agent can fetch recent events from the [trigger events API](https://pipedream.com/docs/connect/api-reference/list-trigger-events.md) instead.

---

- App: https://pipedream.com/apps/hubspot.md · All apps: https://pipedream.com/apps