ElevenLabs Flows webhook: what changed, and Sume's per-job webhook

Per the ElevenLabs changelog, Flows template runs can send their terminal result to a configured webhook, and webhook targets now require an explicit type of all or ids; the earlier defaults were removed. Sume has no target set to configure: you pass a webhook_url on each job and verify each delivery.

Vendor wording is from the ElevenLabs changelog read 2026-10-01. The changelog lists the Flows template API and the webhook target change as separate items, so this post does not claim they are linked. Sume behavior is from Webhooks.

What did ElevenLabs change?

Two entries matter here. The Flows Template API adds endpoints to list and retrieve published Flows templates, start template runs, and retrieve run results; runs can target a published version and send their terminal result to a configured webhook. Separately, webhook targets now require a type discriminator, all or ids. If you create webhook targets from code, send the type explicitly.

How does Sume scope a webhook?

Send mode: "webhook" with a public HTTPS webhook_url on the submit request. The URL belongs to that job. The docs say redeliver does not change the destination URL and that a new URL is a new job. Delivery is terminal-only: job.completed, job.failed, job.canceled.

What about bulk runs?

For a batch of Format runs, the bulk-run docs say the queue has no webhook: communication.webhook_url is per item, and queue-level progress comes from polling status_url. If you expected one callback for a whole set, plan on a callback per item and a poll for the batch.

How do I verify a delivery?

Use verifyWebhook from @sume-com/sdk on the raw body with your workspace signing secret; the docs show SUME_COM_WEBHOOK_SIGNING_SECRET. Keep status_url polling as a backup for missed deliveries. For failures, start with debugging Sume webhook deliveries.