Automation / 6 min read
Prepare a weekly listing poster on a schedule
Turn a reviewed poster workflow into a weekly job with an explicit timezone and approval before each render.
What you need
- A validated review-first poster workflow.
- A specific listing and template, weekday, local time and IANA timezone.
- A reviewer who can handle each scheduled request.
A prompt you can use
Replace the bracketed placeholders with your own details. If you do not have an ID, ask the AI to find the item you can access by name, address or MLS number. Check the match before using its returned ID.
If I have not provided an ID, first discover the resources I can access by name, address or MLS number as supported for that resource, show the matches, and ask me to confirm before using the returned ID. Update workflow [WORKFLOW_ID] without changing unrelated steps. Schedule it every Monday at 09:00 in America/New_York. Verify the current cron syntax and timezone behavior; explain the next three scheduled times in local time and UTC. Keep listing_read at the start so each run reads current facts. Keep approval before rendering and no distribution steps. Save and validate a new draft revision. Do not publish or enable it until I review the schedule and effects.
How the work flows
- Schedule with timezone
- Read current listing
- Prepare inputs
- Human review
- Approved render
This is the intended sequence, not a saved or executed workflow. Ask the AI to implement it against the currently supported tools and report the actual state.
- 01
Specify the timezone, not just the hour
The schedule contract accepts cron, timezone and inputData. For a weekly job, confirm weekday and timezone together. Ask the AI to verify daylight-saving behavior rather than treating 09:00 New York as a fixed UTC offset.
- 02
Read facts when the job runs
Keep a stable listing ID in trigger inputs, not a copied price and description. Each run should read the current authorized listing and stop for missing or unsuitable data. Define what to do if the listing is no longer active.
- 03
Enable only the reviewed revision
Saving, publishing and enabling are separate states. Review the proposed revision, expected frequency and rendering costs, then explicitly authorize the relevant actions. Check the first run’s timestamp and approval request.
Verify the result
- The next three trigger times match the intended local schedule.
- The first run reads fresh facts and pauses before rendering.
- The saved, published and enabled states are reported separately.
When something fails
If a run appears at the wrong hour, inspect the saved timezone and cron before changing the schedule. Pausing future triggers does not necessarily cancel a run already waiting for approval.