Make OpenAI Sora modules deprecated: use HTTP with Sume
Make's notes list the OpenAI Sora and Video modules as deprecated by Sept 24. Replace them with an HTTP module that submits a Sume video job and a webhook.

Make's 2026 release notes, dated September 18, list "OpenAI: Sora and Video Modules Deprecation by September 24, 2026". A scenario that used them can be rebuilt with Make's generic HTTP module: one request submits a Sume video job, and a second scenario with a custom webhook receives the finished result.
The deprecation line is from Make's 2026 notes; the Sume steps are from the video and webhook docs, read 2026-10-01.
What does the HTTP module send?
A POST to https://api.sume.com/v1/videos with a bearer key, a model (or sume/auto to let Sume pick), a prompt, and a callback_url, which the jobs docs describe as an alias of webhook_url. The response returns the job id and a polling URL straight away; the video is not in it.
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"sume/auto","prompt":"A paper boat on a rain puddle","callback_url":"https://hook.example.com/your-make-hook"}'How does the result get back into Make?
Webhook URLs must be public HTTPS URLs, so Make's custom webhook address fits. Create it in a second scenario, verify the signature, and use job_id to find the original request. Keep polling the status_url as a backup, as the docs advise.
| Scenario step | Replacement |
|---|---|
| Create video module | HTTP module: POST /v1/videos |
| Wait for render | Custom webhook, or poll status_url |
| Image or video input | Public HTTPS media URLs only |
| Retry on error | Same Idempotency-Key for exact retries |
What else changes?
Inputs must be public HTTPS URLs, so files held only inside Make need to be hosted first. Error handling is also yours: see Make error handler retry and send an Idempotency-Key on a paid submit that may retry. For the full pattern, read the Make HTTP and webhook scenario.
Sources
Related posts
- Make.com AI video scenario with Sume: HTTP and a webhook
- Make.com error handling: retry a paid API call without duplicates
- Make webhook "Queue is full" 400: what Sume does and how to recover
- Video generation API timeouts: Sume's wait caps, SDK defaults, expiry
- Idempotency keys for AI video APIs: retry without paying twice
More in Integrations
- Make webhook 300 requests per 10 seconds: Sume bulk callbacks
Make returns 429 above 300 webhook requests per 10 seconds. Sume treats a non-2xx callback as a failed attempt and retries up to 10 times, 30 seconds apart.
- Make webhook logs kept 3 days: recover a Sume result later
Make keeps webhook logs for 3 days (30 on Enterprise). A Sume result does not depend on them: store the job id, read job events, and redeliver the callback.
- Make webhook queue MCP tools: stuck items and Sume redelivery
When a webhook queue item looks stuck, check Make's queue and Sume's delivery status separately. Sume can re-POST a job's terminal event with Redeliver.
- Mastra idleTimeoutMs observer detach: the Sume job keeps running
Mastra idleTimeoutMs detaches the observer and keeps the run. A Sume job it started keeps running too: re-wait on its id, do not resubmit.
Written by Sume