n8n Cloud Starter 2,500 executions: one execution per Sume bulk batch

The count

n8n's pricing page charges per execution, and one workflow run is one execution however many steps it has. Annual prices are in EUR: Starter is EUR 20 for 2.5K executions with 5 concurrent, Pro is EUR 50 for 10K with 20 to 50 concurrent, and Business is EUR 667 for 40K and is self-hosted only. Community Edition is free.

That makes the cost question about how many runs, not how many nodes. A 100-row sheet submitted one row per run is 100 executions. The same rows sent to Sume's bulk endpoint are one.

n8n plan facts

Annual billing, EUR, from the page.

Batch it

Sume Formats can queue up to 100 runs in one bulk request with a concurrency field, and you read progress from GET /v1/format-run-queues/{id}. The API key needs the formats:write scope to submit and formats:read to poll. See bulk runs.

For 1,000 clips that is 10 submit executions (1,000 divided by 100) instead of 1,000. Add one receiving execution per webhook and you stay far below the Starter allowance of 2,500: even if every clip also triggers one webhook execution, it is 1,010 in total, or about 40% of Starter.

# n8n HTTP Request node, one execution per 100 rows
POST https://api.sume.com/v1/formats/{handle}/{slug}/bulk-runs
Authorization: Bearer $SUME_API_KEY
Idempotency-Key: batch-2026-10-04-01

Caveats

Pace bulk requests to the queue limit, not to n8n's.

• Concurrent executions of 5 on Starter limit how many webhook receivers run at once.
• Sume's own concurrency is plan-only: Free 1, Pro 4, Startup 8, Scale 20. Extra jobs wait in a queue of max(3, concurrency x 5), and beyond that you get 429 queue_full.
• The path above is a sketch: copy the exact shape from the docs.