Personalized hotel reward emails for high-spenders with Salesforce, Gemini AI & Brevo
This n8n workflow automatically detects high‑spending hotel guests after checkout and emails them a personalized, one‑time reward offer.
🔧 What it does
- Watches Salesforce
Guest__ccustom object for checkout updates. - Pulls guest spend data on optional paid amenities:
- Room Service
- Minibar
- Laundry
- Late Checkout
- Extra Bed
- Airport Transfer
- Calculates total spend to identify VIP guests (≥ $50).
- Uses AI to:
- Spot unused services.
- Randomly pick one unused service.
- Generate a realistic, short promo like:
"Free late checkout on your next stay"
- Parses AI output into JSON.
- Sends a polished HTML email to the guest with their personalized offer.
📦 Key nodes
Salesforce Trigger→ monitors new checkouts.Salesforce→ fetches detailed spend data.Function→ sums up total amenity spend.IF→ filters for VIP guests.LangChain LLM+Google Vertex AI→ drafts the offer text.Structured Output Parser→ cleans AI output.Brevo→ delivers branded email.
📊 Example output
> Subject: John, We Have Something Special for Your Next Stay
> Offer in email: Enjoy a complimentary minibar selection on your next stay.
✨ Why it matters
Rewarding guests who already spend boosts loyalty and repeat bookings — without generic discounts. The offer feels personal, relevant, and exclusive.
Personalized Hotel Reward Emails for High-Spenders with Salesforce, Gemini AI & Brevo
This n8n workflow automates the process of identifying high-spending hotel guests from Salesforce, generating personalized reward emails using Google Gemini AI, and sending them via Brevo (formerly Sendinblue). It helps hotels nurture their most valuable customers with tailored offers.
What it does
- Triggers on Salesforce Data: Listens for new or updated "Contact" records in Salesforce.
- Filters High-Spenders: Checks if the guest's "Total Spend" in Salesforce exceeds a predefined threshold (e.g., $5000).
- Generates Personalized Email Content (Gemini AI):
- If the guest is a high-spender, it uses a Google Vertex Chat Model (powered by Gemini AI) to generate a personalized reward email.
- The AI is instructed to create a compelling email based on the guest's name, total spend, and a suggested reward (e.g., a free night, upgrade, or spa credit).
- It then structures the AI's output into a JSON format using a Structured Output Parser for easy extraction of the email subject and body.
- Sends Email via Brevo: Dispatches the personalized reward email to the high-spending guest using Brevo.
- Updates Salesforce (Optional - not explicitly in JSON but implied by common use cases): While not explicitly shown in the provided JSON, a common next step would be to update the Salesforce contact record to log that an email was sent or to track the reward offered.
Prerequisites/Requirements
- n8n Account: A running n8n instance (cloud or self-hosted).
- Salesforce Account: With appropriate permissions to read Contact records.
- Google Cloud Project: With the Vertex AI API enabled and a service account for the Google Vertex Chat Model. This will likely involve setting up a Google Cloud credential in n8n.
- Brevo (Sendinblue) Account: With an API key for sending emails.
- Basic LLM Chain Node: Requires the
@n8n/n8n-nodes-langchainpackage to be installed in your n8n instance. - Structured Output Parser Node: Also from the
@n8n/n8n-nodes-langchainpackage.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots menu (
...) in the top right and select "Import from JSON". - Paste the workflow JSON or upload the file.
- Configure Credentials:
- Salesforce Trigger:
- Click on the "Salesforce Trigger" node.
- Select or create a new Salesforce OAuth2 credential. Follow the n8n documentation for setting up Salesforce credentials.
- Configure the "Object" to
Contactand set the "Operation" toWatch for New or Updated.
- Google Vertex Chat Model:
- Click on the "Google Vertex Chat Model" node.
- Select or create a new Google Cloud credential (e.g., Service Account Key). Ensure the service account has permissions to use Vertex AI.
- Configure the
Model Name(e.g.,gemini-pro).
- Brevo:
- Click on the "Brevo" node.
- Select or create a new Brevo API credential.
- Salesforce Trigger:
- Configure Nodes:
- If Node (ID: 20):
- Adjust the condition to match your high-spender logic. The current setup likely checks a numeric field for a value greater than a specific amount (e.g.,
{{ $json.totalSpend > 5000 }}).
- Adjust the condition to match your high-spender logic. The current setup likely checks a numeric field for a value greater than a specific amount (e.g.,
- Code Node (ID: 834):
- This node likely prepares the prompt for the AI. Review and adjust the prompt to fine-tune the email generation to your specific needs and brand voice.
- Basic LLM Chain (ID: 1123):
- Ensure the prompt template and variables are correctly mapped from the previous "Code" node.
- Structured Output Parser (ID: 1179):
- This node is crucial for extracting the subject and body from the AI's response. Verify its schema definition matches the expected JSON output from the AI.
- Brevo Node (ID: 820):
- Configure the "Operation" to
Send Email. - Map the recipient email address (e.g.,
{{ $json.email }}) and the subject and body from the "Structured Output Parser" node. - Set your sender email address.
- Configure the "Operation" to
- If Node (ID: 20):
- Activate the Workflow: Once all credentials and configurations are set, save and activate the workflow.
Now, whenever a Salesforce Contact record is created or updated and meets your high-spender criteria, a personalized reward email will be generated and sent automatically!
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte
🎓 How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.