Azure Event Grid Triggers

Once available, Orvanta will be able to connect to Azure Event Grid and trigger a script or flow when events are delivered from custom topics, system topics, domains, or Event Grid Namespace topics, covering both push delivery (webhook) and pull delivery (lock-token acknowledgment) — the same shape as the other event-backed triggers (Kafka, NATS, GCP Pub/Sub).

Preprocessor event shape

For reference, an Azure-triggered preprocessor would receive an event shaped like this:

export async function preprocessor(
  event: {
    kind: 'azure',
    payload: any,
    id: string,
    source: string,
    type: string,
    subject?: string,
    time?: string,
    delivery_type: 'push' | 'pull',
    headers?: Record<string, string>,
    lock_token?: string,
    trigger_path?: string,
  }
) {
  if (event.kind !== 'azure') {
    throw new Error(`Expected an azure trigger kind, got: ${event.kind}`);
  }
  return {
    eventType: event.type,
    subject: event.subject,
    data: event.payload,
  };
}

payload: The CloudEvent data field — typically a JSON object whose shape depends on the event source (Storage, Resource Manager, Key Vault, a custom topic, etc.).
type: CloudEvents type (e.g. Microsoft.Storage.BlobCreated).
delivery_type: "push" or "pull".
lock_token: Lock token used to acknowledge or reject the message (pull mode only).

See Preprocessors for how a preprocessor’s return value maps onto a script’s main() parameters.