View as Markdown
Hookdeck icon

Hookdeck TRIGGER

New Event Received (Instant)

Emit new event when a new event is received from a HookDeck source.
  • Trigger
  • Instant
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Hookdeck 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: "hookdeck-new-event-received",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    hookdeck: { authProvisionId: "apn_xxxxxxx" },
    name: "Connection Name",
    description: "Description",
  },
  webhookUrl: "https://example.com/webhooks/hookdeck",
})

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 Event Received (Instant) configuration
Property Type Description
name Connection Name string
The name of the connection.
Optional
description Description string
The description of the connection.
Optional
sourceId Pre-existing Source string
The source ID of the connection.
Optional Dynamic
source New Source object
An object representing the source of the connection. Object must contain at least name. Please check the documentation for more information.
Optional
destinationName Destination Name string
The destination name that will be created or updated with Pipedream HTTP endpoint for Pipedream source to receive your event. Existing destination with the same name will be overridden with the new HTTP endpoint
Optional

01

Connect

Your user authorizes Hookdeck 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 — as it happens.

OR

On-demand retrieval

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

Registry key
hookdeck-new-event-received
Version
0.0.3
App
Hookdeck
Authentication
API key
Delivery
Instant event
Output
Events emitted by Hookdeck.