Automation / 6 min read
Make a new listing poster after a price change
Build a listing-specific price-change workflow that rechecks facts and asks for review before making a new poster.
What you need
- One authorized listing ID and permission to monitor its price.
- A saved poster template and permission to use the selected media.
- The existing review-first workflow, or permission to create a draft.
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. Draft an event workflow for listing [LISTING_ID] using poster template [TEMPLATE_ID]. Use the supported listing.updated trigger for listPrice changes only. Read the current listing after the event, show the current price and proposed poster inputs for human approval, then render only if approved. Do not claim this detects every MLS edit. Keep sending and publishing out of the flow. Validate and save the draft; explain which events match and which do not. Do not enable or run it.
How the work flows
- listing.updated for one listing
- Filter listPrice
- Read current facts
- Review inputs
- 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
Choose a supported change
Use listing.updated for the selected listingId and set changedFields to listPrice. This recipe responds to price changes, not photo uploads or other MLS edits.
- 02
Use the verified current price
Read the current price for the new poster. Do not invent an old price or a percentage reduction when the available event or record does not provide the required values. Keep the listing identity and source update time visible in the review.
- 03
Validate without changing a real listing
Ask for matched and unmatched test inputs: the selected listing, another listing, and an unrelated field change. Validate branch behavior without editing an MLS record just to trigger the flow. A real run still needs approval and may incur rendering costs.
Verify the result
- Only the selected listing and chosen fields match.
- Unsupported field changes do not start this recipe.
- A rejected review never creates replacement marketing media.
When something fails
A missing event is not proof that no change occurred. Check trigger enablement, listing identity and supported changed fields. Inspect the original run before retrying after an uncertain result.