Notion database, personalized emails by Claude Haiku, orchestrated by Make.
← Back to consultingTravel client needed to automate discovery meeting management. Each booking triggered manual actions. Generic emails didn't match premium positioning.
Automate the entire booking flow while keeping personalization. Haiku generates unique sensory and cultural destination descriptions with a concierge tone—no superlatives.
The webhook captures the booking in real time, triggering the entire workflow.
The webhook receives booking data with client information, destination, travel dates, and preferences. This initiates the automated sequence without manual intervention.
The Google Calendar API is called to create a discovery meeting slot and generate a unique meeting link.
A calendar event is created with predefined duration and availability rules. Google Meet automatically generates a video conference link, which is then embedded in the client's confirmation email.
The Notion database centralizes all client records, booking history, and personalization preferences.
The workflow queries Notion for the client profile, including past trips, preferences, communication style, and any special requirements. This data feeds into the personalization layer.
The prompt is calibrated with precise constraints: formal address, no greeting or signature, only the destination description.
Haiku receives the destination, client name, and context. It generates a unique, sensory-rich paragraph describing the destination with cultural nuance and a premium concierge tone. The output is deterministic: no superlatives, no marketing language, just authentic insight.
The email integrates Haiku's personalized message, the Google Meet link, and all booking details.
A richly formatted HTML email is sent to the client with their name, destination details (personalized by Haiku), the calendar invite, and the Google Meet link. Tone matches the premium positioning.
The team automatically receives new meeting details, booking summary, and client contact information.
An internal email alerts the team with the client name, destination, meeting date/time, and Google Meet link. This ensures the team is prepared before the discovery call.
The query filters on three criteria: meeting status is "confirmed", scheduled date is tomorrow, and reminder not yet sent.
A scheduled Make scenario runs each evening. It queries the Notion database to find all confirmed meetings scheduled for the next day that haven't received a reminder yet.
Short and direct: meeting time, destination, and Google Meet link. Sent to both client and team.
A concise reminder email is sent the day before. For clients: meeting details and link. For the team: same details plus any last-minute notes from the Notion database.
The meeting record is updated with the timestamp of the reminder sent and its status marked as "reminder_sent".
After the reminder is sent, Make updates the meeting record in Notion to mark that the reminder has been delivered. This prevents duplicate reminders and provides audit trail.
Client autonomy: visual workflow, can ask Claude for help modifying. No deployment, no infrastructure maintenance. The client owns the system immediately and can iterate without developer dependency.
Workflow complexity (multiple APIs, conditional logic, scheduling) requires orchestration beyond a simple prompt. But a full custom backend would be overkill and lock the client into dependency. The right level: Make + Claude Haiku for the creative personalization.
2 Make scenarios + Claude Haiku
Make, Notion, Gmail, Google Calendar
Claude Haiku (personalization)
Visual workflow, self-modifiable