View as Markdown
Brevo icon

Brevo TRIGGER

New Marketing Webhook (Instant)

Emit new event when triggered by a marketing event
  • Trigger
  • Instant
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Brevo 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: "brevo-marketing-webhook",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    brevo: { authProvisionId: "apn_xxxxxxx" },
    description: "Description",
    events: ["Events"],
  },
  webhookUrl: "https://example.com/webhooks/brevo",
})

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 Marketing Webhook (Instant) configuration
Property Type Description
description Description string
Description of the webhook.
Required
events Events string[]
Events triggering the webhook.
Required

01

Connect

Your user authorizes Brevo 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
brevo-marketing-webhook
Version
0.0.2
App
Brevo
Authentication
API key
Delivery
Instant event
Output
Events emitted by Brevo.