View as Markdown
Svix icon

Svix TRIGGER

New Event Received (Instant)

Emit new event when an event is received for an application
  • Trigger
  • Instant
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Svix 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: "svix-new-event-received",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    svix: { authProvisionId: "apn_xxxxxxx" },
    appId: "Application ID",
    eventTypes: ["Event Types"],
  },
  webhookUrl: "https://example.com/webhooks/svix",
})

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
appId Application ID string
The application's ID or UID
Required Dynamic
eventTypes Event Types string[]
The type of events to watch for
Required Dynamic

01

Connect

Your user authorizes Svix 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
svix-new-event-received
Version
0.0.1
App
Svix
Authentication
API key
Delivery
Instant event
Output
Events emitted by Svix.