Black Friday 2026 countdown posts on a schedule, with a spend cap
Plan daily countdown posts from November 20 to Black Friday, November 27, 2026, as one Sume Scheduled action. Where the schedule lives and what the API can do.

To post a Black Friday countdown every day without opening an editor, save the daily task once as a Sume Scheduled action, give it a daily cadence from November 20 and a spend cap, and let it run through Friday, November 27, 2026. Thanksgiving is Thursday, November 26, so the posts run from seven days out through the day itself.
One thing to know before you plan around the API: Sume's docs read on 2026-10-04 say a schedule is created in the dashboard or in chat, while the API lists schedules, reads them and starts runs. Do not write a script that expects to POST a new cron.
What does each day's post contain?
Give the action a task that is the same every day and reads the date: "Make a 9:16 countdown card for the number of days left to Black Friday, November 27, 2026, with the shop's offer line, and show me the draft." Put the offer, the colours and the do-not-say list in the saved task so every post agrees with the one before.
What is the spend cap?
Scheduled actions have a spend cap per run; the docs describe a default of $1. For a still image card that is plenty, and it protects the wallet if the task drifts into video. Raise it on purpose, not by default. Scheduled lists the fields; the image rates are on the API pricing page.
| Date | Days to Black Friday | Post |
|---|---|---|
| Fri Nov 20 | 7 | Teaser: the offer in one line |
| Mon Nov 23 | 4 | Hero product card |
| Wed Nov 25 | 2 | Last order day for delivery |
| Thu Nov 26 | 1 | Thanksgiving: a thank-you, no sale |
| Fri Nov 27 | 0 | Doors open card |
How can the API help on the day?
If a post needs a rerun, start one run of the saved action by id and read its status. Run a schedule via API covers the keys that can do it and the body. Replay the same Idempotency-Key for a retry so a flaky client does not start a second paid run.
import os, requests
BASE = "https://api.sume.com"
H = {"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"}
actions = requests.get(f"{BASE}/v1/actions", headers=H, timeout=30).json()
print(actions)What should I check each morning?
Open the card before it publishes. Check the day count, the date and the offer wording; a stale number is the common failure of any scheduled post. Keep the Thanksgiving post free of sale language, which is your call, not a Sume setting.
Sources
Related posts
More in Use cases
- Black Friday ad fatigue: refresh a clip with a new first second
When a Black Friday ad stops converting, keep the footage and change the opening: a new hook, new caption cues and a new music bed, for about $0.30 per refresh.
- Black Friday email header: a 2-second motion clip for 12.5 cents
Animate your Black Friday 2026 email header image into a 2-second clip with Wan 3.0 at 480p for $0.125 on Sume. Date, prompt, price table and the email caveat.
- Board game trailer: table clips and box art as Gemini Omni references
Use up to 3 short clips (3 s or less each) plus images as references in Gemini Omni Flash 1.1 to make a 10-second board game trailer with native sound.
- Brand color check for AI images: Delta E in Python before publishing
Prompts cannot guarantee a brand hex. Measure the nearest palette color in a generated image with CIE76 Delta E and block misses. Code for Sume output.
Written by Sume