Small business holiday ad creative with AI: one Format, one bulk run

Google showed three creatives building local campaigns with Flow. A shop can run a first-party Sume Format per product and queue up to 100 runs in a bulk call.

4 min readSume
All posts

A local shop can make holiday ad creative by calling a first-party Sume Format at the reserved sume handle, one call per product, and by queuing a short list as a bulk run of up to 100 Format runs. No fork or install is needed first.

Google's blog post, read 2026-10-01, describes The Small Brief: three creative leaders given unlimited access to Google Flow to build campaigns for local businesses and nonprofits. Sume facts are from the Format catalog, bulk runs and create a run docs.

What did Google's Small Brief show?

The post says Google launched the project in May, with its agency, to celebrate Small Business Week. Three creatives built campaigns for local businesses using Google Flow, and the post links behind-the-scenes videos. It is a showcase of what small teams can make; it gives no cost or performance figures that this post relies on.

Which Sume Format should a shop start with?

The catalog lists the callable slugs today, including sume-product-usage-demo, sume-product-commercial, sume-before-after and sume-slideshow. Read one first with GET /v1/formats/sume/{slug}, which returns its description and an io profile: input_kind is url, text, image or product, and output_kind is video, image or text. A slug not on the list answers 404 format_not_found.

Formats by Sume are called at POST /v1/formats/sume/{slug}/runs, and any key carrying formats:write may call one. The run, its media and its spend belong to the calling key.

How do I queue the whole holiday list?

The bulk route takes concurrency (1 to 16) and items (1 to 100), each item the same body as a single run. It returns 202 with a queue; poll GET /v1/format-run-queues/{id}. Use a fresh Idempotency-Key per batch, because replaying a spent key returns the old queue.

Bulk queue facts from the Sume docs, read 2026-10-01.
ItemValue
Items per queue1 to 100
concurrency1 to 16
Queue webhookNone; webhooks are per item
completed statusEvery item is terminal, not all succeeded; check counts.failed
curl -sS -X POST "https://api.sume.com/v1/formats/sume/sume-product-usage-demo/bulk-runs" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "concurrency": 2,
    "items": [
      { "instruction": "Holiday gift angle", "input": { "url": "https://example.com/p/1" } },
      { "instruction": "Holiday gift angle", "input": { "url": "https://example.com/p/2" } }
    ]
  }'

What should I check before running it?

Read the io profile so input matches, set a per-run generation_spend_cap_usd, and run one item before the batch. For a phase plan across the season, see holiday ad creative by phase.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume