Make.com scheduler: run a scenario daily to make a video

Make.com's scheduler is the Schedule settings panel on each scenario: a scenario runs every 15 minutes by default, and you can change it to at regular intervals, once, daily, weekdays, weekly, monthly, on specified dates, or on demand. For a daily video, set Daily at your time and have an HTTP Make a request module start the video run with a date-based idempotency key.

Make's options are quoted from its Help Center page Schedule a scenario and its date and time functions; the Sume side comes from Create a run. All were read on 2026-09-28. Sume has no Make app; the scenario makes a plain HTTPS call.

How do I schedule a Make scenario?

Open the scenario in the Scenario Builder and click Every 15 minutes on the toolbar. That opens Schedule settings, where you pick one option:

• To limit an active scenario to a date range, check Show advanced settings and fill in the Start and End date.
• The Immediately option is available only for some triggers.
• The organization dashboard shows how much time is left until the next run.

How do I start the video run from the scenario?

Add the HTTP app's Make a request module to the scheduled scenario, with Method POST and the URL https://api.sume.com/v1/formats/{handle}/{slug}/runs. Keep the API key in the module's credentials; Make.com AI video scenario walks through the authentication fields. Add an Idempotency-Key header built from the date with Make's formatDate function, for example daily-video- followed by formatDate(now; YYYY-MM-DD). Without a timezone argument, formatDate uses your organization's timezone. The JSON body:

{
  "instruction": "Make today's 30-second vertical tip video.",
  "input": { "series": "daily-tips" },
  "generation_spend_cap_usd": 5,
  "communication": { "webhook_url": "<scenario two's custom webhook URL>" }
}

Why build the key from the date?

So the day's video is made once, whatever happens to the request. Sume's docs say to derive the key from the thing being made and a version you bump, not from the moment of asking. Idempotency keys for AI video APIs covers the rules; two matter for a scheduled scenario:

• If the same day's request is sent twice with the same body, Sume answers 200 with the original run and idempotency_hit: true: no second run, no second charge.
• The same key with a different body is 409 idempotency_conflict, and nothing runs. Keep timestamps out of the body.

How does Make get the finished video?

In a second scenario. Make a request waits at most 300 seconds (its Timeout is a number from 1 to 300), and long-form video is 15 to 30 minutes of work. So the scheduled scenario only starts the run, and communication.webhook_url points at a second scenario's custom webhook, which receives one signed format.run.terminal POST when the run completes or fails. The Make.com AI video scenario post builds that scenario and checks the signature.

If nothing but the clock starts the work, Sume's own Scheduled feature can replace the first scenario: it runs saved instructions on a 5-field cron expression in an IANA timezone (Create a schedule), authored in the Agents dashboard.