On transactional event

onBrevoTransactionalEvent is the broad subscription for delivery, engagement, bounce, invalid-address, spam, unsubscribe, and provider-error events. Use a typed helper when only one semantic category matters.

Example

import { automation, log } from "automate.ax"
import { onBrevoTransactionalEvent } from "automate.ax/brevo"

export default automation("Audit Brevo events", () => {
  const event = onBrevoTransactionalEvent()

  log({ value: event })
})

Options

account?: string | IntegrationAccountReference<"brevo"> selects a static Brevo API-key binding and defaults to the project’s default binding. A signal cannot choose the watched account at runtime.

Trigger data

interface BrevoTransactionalEvent {
  event:
    | "blocked"
    | "click"
    | "deferred"
    | "delivered"
    | "error"
    | "hard_bounce"
    | "invalid_email"
    | "opened"
    | "request"
    | "soft_bounce"
    | "spam"
    | "unique_opened"
    | "unsubscribed"
  occurredAt: number
  webhookId: number
  email?: string
  messageId?: string
  data: Record<string, JSONValue>
}

occurredAt is Unix time in seconds. data preserves the complete provider-native webhook, including fields Automate.ax has not promoted. Email and message identity can be absent on some provider events. Automate.ax manages one authenticated, non-batched transactional webhook per connected account and deduplicates exact provider retries. If one automation subscribes through both this broad helper and a matching typed helper, the same provider callback intentionally emits once to each subscription.

Get started

Concepts

Reference

On transactional event

Example

Options

Trigger data

​Example

​Options

​Trigger data

Example

Options

Trigger data