On transactional SMS event

brevo.onTransactionalSmsEvent watches transactional SMS webhooks. Use a narrower trigger when only one event matters.

Example

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

export default automation("Handle Brevo transactional SMS event", () => {
  const event = brevo.onTransactionalSmsEvent()
  log(t`Brevo ${event.family} / ${event.type}`)
})

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 transactionalSms. type is one of sent | delivered | hardBounced | softBounced | replied | 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.

Built-in triggers

Built-in actions

Runtime utilities

Integrations

On transactional SMS event

Example

Options

Trigger data

​Example

​Options

​Trigger data

Example

Options

Trigger data