Celebrations that come round every year
Pink Flamingo Party Co. is a balloon décor and events company, and much of its work recurs annually: birthdays, anniversaries, graduations and corporate celebrations. A past customer is the likeliest source of the next booking, but only if they hear from the company at the right moment: early enough to start planning, not so early that the message is forgotten by the time it matters.
Bookings live in two places: orders from the Shopify store, and event projects in HoneyBook.
Shopify first, then back for HoneyBook
Phase one, delivered and live, re-engages past customers automatically from their Shopify order history. That result is what started phase two: the client came back to apply the same idea to its HoneyBook bookings, as a production n8n workflow that is now in build.
Timing on the event date
Outreach is anchored on each project’s event date, not the date it was booked, because the event date is what a recurring celebration repeats on. Every historical and future project gets that anchor. Each customer gets a reminder ten months after their event and a follow-up at eleven months unless they have since been excluded, which leaves one to two months to plan. The workflow is evaluated daily, so each customer is contacted at the right point rather than in a monthly batch, and it looks back up to four years: a customer who booked several years ago and skipped a year still qualifies.
Never the same message twice
The part that has to be right is state. A ledger records every event: the original project, its event date, the customer, and each outreach with the date it was sent, so a re-run can never send a duplicate. Existing customer history comes in through a throttled backfill that writes to the same ledger, so the live workflow will not contact a backfilled customer again. Messages go out through HoneyBook where its API supports it, keeping them on the customer’s project, and by email otherwise. The only call to action is a reply.
Sends are logged, errors are handled, and the hand-over includes controlled test sends before activation, a workflow export and a recorded walkthrough. Outcomes of the HoneyBook workflow will be reported here once it has run through its first outreach cycle.
