Skip to main content
brevo.onMarketingEmailEvent watches marketing email webhooks. Use a narrower trigger when only one event matters.

Example

Options

account?: string | IntegrationAccountReference<"brevo"> selects a static Brevo API-key binding and defaults to the project binding. Runtime signals cannot select the watched account.

Trigger data

family is marketingEmail. type is one of delivered | hardBounced | softBounced | markedAsSpam | opened | clicked | unsubscribed. Every event includes webhookId and the complete provider callback in event. Depending on the family, optional normalized fields include message identity, email or phone, campaign identity, timestamps, status, reason, link, reply, list IDs, and credit usage. Automate.ax manages authenticated, non-batched Brevo webhooks for the required channels and deduplicates exact callback retries. A callback also matches brevo.onEvent and its family trigger when those triggers are present.