Back to Catalog

QuickBooks customer welcome emails with Google Sheets tracking

Elegant BiztechElegant Biztech
164 views
2/3/2026
Official Page

Automated QuickBooks New Customer Welcome Emails

This workflow provides a robust solution for QuickBooks users looking to automate their new customer onboarding process. It solves the time-consuming and error-prone task of manually sending welcome emails by creating a fully automated system that ensures every new customer receives a timely, personalized, and professional welcome.

The workflow periodically checks your QuickBooks Online account for new entries. To prevent sending duplicate emails to existing customers, it cleverly uses a Google Sheet as a simple database, tracking every customer who has already been contacted. This makes the process reliable and safe to run on an automated schedule.

This template was crafted with care by the team at Elegant Biztech to help you build stronger customer relationships through smart automation.

How the Workflow Operates

  1. Scheduled Trigger: The workflow initiates on a customizable schedule (e.g., every hour).
  2. Fetch Data: It simultaneously fetches all customer data from your QuickBooks account and the list of already-processed customer IDs from your Google Sheet.
  3. Find New Customers: It compares the two lists to isolate only the new customers who have not yet been processed.
  4. Log New Customers: For each new customer found, the workflow performs two logging actions:
    • It appends their full details (Name, Company, Email, etc.) to a "log" sheet for your records.
    • It adds their unique Customer ID to the "tracking" sheet to ensure they are not emailed again in the future.
  5. Craft Personalized Email: A Email Template node dynamically generates a beautiful, responsive HTML email, personalized with the customer's name, company, and location details.
  6. Send Welcome Email: The final node sends the uniquely crafted email to the new customer.

Prerequisites

Before you begin, please ensure you have the following:

  • An active n8n instance.
  • A QuickBooks Online account with API access.
  • A Google account.
  • An email service (e.g., SMTP, Gmail, Outlook) connected to n8n as credentials.

Step-by-Step Setup Guide

Follow these instructions carefully to configure the workflow for your use.

1. Create the Google Sheet

This workflow requires a Google Sheet with two specific tabs to function as its database.

  1. Create a new Google Sheet.
  2. Rename the first tab to Processed IDs. In cell A1, create the header: CustomerIds.
  3. Create a second tab and name it New Customer Logs. In row 1, create the following headers: Customer_Name, Company_Name, Email_ID, Phone_No, Customer_ID.

2. Connect Your Accounts

You must authenticate your accounts in the designated nodes.

  • Get many Customers node: Select this node and connect your QuickBooks Online credentials.
  • Read Old Customers node: Connect your Google Sheets account credentials here. This will be automatically used by the other Google Sheets nodes.
  • Send Personalized Welcome Email node: Connect the credentials for the email account you wish to send from.

3. Configure the Google Sheets Nodes

Point the workflow to the correct sheet and tabs you just created.

  • Read Old Customers node:
    • In the Document ID field, select your new Google Sheet.
    • In the Sheet Name field, select the Processed IDs tab.
  • Log New Customer Details node:
    • Verify the Document ID field is correctly set to your Google Sheet.
    • In the Sheet Name field, select the New Customer Logs tab.
  • Log New Customer ID for Tracking node:
    • Verify the Document ID is correct.
    • In the Sheet Name field, select the Processed IDs tab.

4. Customize the Email Template

Personalize the welcome email to match your brand.

  1. Open the Code node.
  2. Inside the code editor, find and replace these four placeholder values:
    • Your Logo URL: Replace the placeholder link with a public URL to your company's logo.
    • Your Website Link: Replace the placeholder with a link to your website's dashboard or homepage.
    • Your Support Email: Replace the mailto: link with your company's support email.
    • Your Company Name: Update the company name in the copyright footer.
  3. Next, select the Send Personalized Welcome Email node and update the Subject field with your company's name.

5. Activate the Workflow

  1. Open the Scheduler node to set the schedule for how often you want the workflow to run.
  2. Save the workflow.
  3. Click the Active toggle at the top right of the screen.

Your automated welcome email system is now live! For questions or to explore more custom solutions, visit us at elegantbiztech.com.

QuickBooks Customer Welcome Emails with Google Sheets Tracking

This n8n workflow automates the process of sending welcome emails to new QuickBooks customers and tracking these interactions in a Google Sheet. It ensures that every new customer receives a personalized welcome and that their onboarding status is consistently logged.

What it does

This workflow simplifies customer onboarding by:

  1. Triggering on a Schedule: The workflow runs periodically (e.g., daily, hourly) to check for new customers.
  2. Fetching QuickBooks Customers: It retrieves a list of all customers from QuickBooks Online.
  3. Fetching Google Sheet Data: It reads existing customer data from a specified Google Sheet to identify customers who have already received a welcome email.
  4. Comparing Datasets: It compares the list of QuickBooks customers with the Google Sheet data to identify new customers who haven't yet been welcomed.
  5. Preparing Email Data: For each new customer, it prepares the necessary data (like name, email, and a welcome message) for sending an email.
  6. Sending Welcome Emails: It sends a personalized welcome email to each newly identified customer.
  7. Updating Google Sheet: After sending the email, it adds a new row to the Google Sheet, marking the customer as "welcomed" and recording the date.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • QuickBooks Online Account: With credentials configured in n8n.
  • Google Sheets Account: With credentials configured in n8n.
  • Google Sheet: A Google Sheet to track welcomed customers. It should have columns to store customer details and a "Welcomed" status.
  • SMTP Server: For sending emails (configured as a credential in n8n).

Setup/Usage

  1. Import the Workflow:

    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button (or paste the JSON directly if available).
    • Paste the JSON code and click "Import".
  2. Configure Credentials:

    • Locate the "QuickBooks Online" node and configure your QuickBooks Online API credentials.
    • Locate the "Google Sheets" nodes and configure your Google Sheets API credentials.
    • Locate the "Send Email" node and configure your SMTP credentials.
  3. Configure Nodes:

    • Schedule Trigger (ID: 839): Adjust the schedule as needed (e.g., daily, every few hours).
    • QuickBooks Online (ID: 455): Ensure it's configured to list customers. You might need to specify filters if you only want to welcome certain types of customers.
    • Google Sheets (ID: 18):
      • Configure the "Read" operation to fetch data from your tracking Google Sheet. Specify the Spreadsheet ID and Sheet Name.
      • Configure the "Write" operation to append new rows to the same tracking Google Sheet. Ensure the column names match your sheet.
    • Code (ID: 834): This node will likely contain logic to format the customer data for the email and the Google Sheet. Review and adjust the JavaScript code as necessary to match your data structure and desired email content.
    • Compare Datasets (ID: 836): This node will compare the QuickBooks customers with the already welcomed customers in Google Sheets. Ensure the key fields for comparison (e.g., customer ID, email) are correctly configured.
    • Send Email (ID: 11):
      • Set the "To" address dynamically using an expression that pulls the customer's email from the previous nodes (e.g., {{ $json.email }}).
      • Customize the "Subject" and "Body" of the welcome email.
  4. Activate the Workflow:

    • Once all credentials and nodes are configured, save the workflow.
    • Toggle the workflow to "Active" to start it.

The workflow will now run on its defined schedule, automatically sending welcome emails to new QuickBooks customers and keeping your Google Sheet updated.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942