Google Sheets to Gmail, hospital outreach on autopilot
Hospital outreach sounds simple until you’re chasing contact details, copying email addresses, and rewriting the same message 30 times. One typo sends a pitch to the wrong inbox. One missed follow-up and the whole week slips.
This Google Sheets Gmail automation hits medical device sales reps hardest, but healthcare startup teams and IT consultants feel it too. You get consistent personalization at scale, without living in spreadsheets all day.
Below, you’ll see exactly how the workflow turns a single chat message into region-specific lookups and ready-to-send outreach emails, then what you can tweak to match your process.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Sheets to Gmail, hospital outreach on autopilot
flowchart LR
subgraph sg0["When chat message received Flow"]
direction LR
n0@{ icon: "mdi:database", form: "rounded", label: "MINDANAO", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "VISAYAS FILES", pos: "b", h: 48 }
n2@{ icon: "mdi:database", form: "rounded", label: "LUZON FILES", pos: "b", h: 48 }
n3@{ icon: "mdi:play-circle", form: "rounded", label: "When chat message received", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Hospital Parser"]
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Batch Sender", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Region Switcher", pos: "b", h: 48 }
n7@{ icon: "mdi:message-outline", form: "rounded", label: "Send Gmail Message", pos: "b", h: 48 }
n0 --> n7
n2 --> n7
n5 --> n6
n1 --> n7
n4 --> n5
n6 --> n2
n6 --> n1
n6 --> n0
n7 --> n5
n3 --> n4
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n3 trigger
class n6 decision
class n0,n1,n2 database
class n4 code
classDef customIcon fill:none,stroke:none
class n4 customIcon
The Problem: Hospital outreach breaks down fast
Targeted hospital outreach is tedious in a very specific way. You’re not just sending “a cold email.” You’re matching each hospital to the right contact, making sure you’re using the correct region list, and customizing the message enough that it doesn’t feel like a mail merge accident. Do it manually and the work expands to fill your day: search, copy, paste, double-check, repeat. And honestly, the worst part is the mental load. You keep second-guessing if you emailed that hospital already or if you grabbed the right address from the right sheet.
It adds up fast. Here’s where it usually breaks down.
- You end up reformatting lists from Slack, notes, and chat threads before you can even start sending.
- Region-specific contact details get mixed up, so a Visayas hospital gets the Luzon contact or a generic inbox.
- Personalization becomes inconsistent, which means more edits and weaker replies.
- Manual sending makes pacing unpredictable, so outreach goes quiet whenever your calendar gets busy.
The Solution: Chat-triggered hospital outreach from Sheets to Gmail
This workflow turns hospital outreach into a simple input-and-run system. You send one chat message: the first line is the region (like LUZON), and the next lines are hospital names. n8n parses that message into a clean list, then processes hospitals one at a time so nothing gets skipped. Based on the region you provided, it routes the lookup to the right Google Sheet tab and finds the matching row for each hospital. Finally, Gmail sends a tailored email using the fields pulled from your spreadsheet (like hospital name and main email). The result is repeatable outreach that still feels specific because the data and placeholders come from your own sheet structure.
The workflow starts with a chat trigger and a quick parser. Then it loops through your hospital list, routes each item to the correct region sheet, and sends a Gmail message for that hospital before moving on to the next.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you’re reaching out to 25 hospitals in Luzon each week. Manually, you might spend about 5 minutes per hospital to find the right row, confirm the main email, paste a template, and customize the opening line, so roughly 2 hours total (and that’s on a good day). With this workflow, you paste a region plus 25 hospital names into chat in about 5 minutes, then let n8n run through the list and send each Gmail message. You still review replies, but the repetitive “send” work is basically gone.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store hospital contacts by region
- Gmail to send outreach from your account
- Google OAuth credentials (create in Google Cloud Console)
Skill level: Beginner. You’ll connect Google accounts, duplicate a sheet template structure, and replace a Sheet ID in one node.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Chat message kicks it off. You send a message where line one is the region and the rest are hospital names. That’s the only “trigger” you need, so you can run outreach from wherever you already work.
Your message becomes a clean list. A small parser converts the text into structured items n8n can process, which helps avoid weird formatting issues like extra spaces or blank lines.
Hospitals are processed one at a time. The workflow loops through each hospital using batching, which is slower but more reliable. If one record is missing or mismatched, it won’t silently break the whole run.
Sheets lookup and Gmail send happen together. A switch routes to the correct Google Sheet tab (Luzon, Visayas, or Mindanao), pulls the contact details, and Gmail sends the personalized email using your template fields.
You can easily modify the email copy to match your offer and tone based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Chat Trigger
Set up the workflow entry point so hospital outreach requests can be submitted via chat input.
- Add and open Incoming Chat Trigger to generate the chat webhook endpoint.
- Leave default Options as configured and save the webhook URL for testing.
- Connect Incoming Chat Trigger to Hospital Text Parser to pass the chat input through for parsing.
Step 2: Connect Google Sheets
Configure the regional lookup sheets that provide contact details and personalization fields for each hospital.
- Open Luzon Sheet Lookup and set Document to
PH HOSPITALsand Sheet toLuzon. - Set the lookup filter: Lookup Column to
Hospital Nameand Lookup Value to={{ $json.hospital }}. - Repeat the same configuration for Visayas Sheet Lookup with Sheet set to
Visayas. - Open Mindanao Sheet Lookup and set Document to
PH HOSPITALsand Sheet toMindanao. - Credential Required: Connect your Google Sheets credentials in each of the three Google Sheets nodes.
Step 3: Set Up the Hospital Parsing and Routing Logic
Parse the chat input into per-hospital items and route each hospital to the correct regional sheet.
- Open Hospital Text Parser and keep the JavaScript as provided to split lines into
regionandhospitalitems. - Ensure Hospital Text Parser connects to Batch Dispatcher so each hospital is processed individually.
- Open Region Routing Switch and verify the three rules use
={{ $json.region }}with=LUZON,=VISAYAS, and=MINDANAOin their rightValue fields. - Confirm the routing outputs go to Luzon Sheet Lookup, Visayas Sheet Lookup, and Mindanao Sheet Lookup respectively.
⚠️ Common Pitfall: If the chat input region line doesn’t include the exact keyword (LUZON, VISAYAS, MINDANAO), the switch won’t match. Ensure the first line of the chat input contains the region name.
Step 4: Configure the Email Output
Send personalized outreach emails using Gmail with values pulled from each regional sheet.
- Open Dispatch Gmail Email and set To to
={{ $json['Main Email'] }}. - Set Subject to
=Letter of Intent: {{ $json['Hospital Name'] }}. - Set Message to the full HTML template provided, including placeholders like
{{ $json["Hospital Name"] }}and{{ $json["Video Link 1"] }}. - Connect Dispatch Gmail Email back to Batch Dispatcher so the workflow continues until all hospitals are processed.
- Credential Required: Connect your Gmail credentials in Dispatch Gmail Email.
Step 5: Test and Activate Your Workflow
Validate the end-to-end flow from chat input through sheet lookup to email delivery.
- Click Test workflow and send a chat input where line 1 is a region (e.g.,
LUZON) and subsequent lines list hospital names. - Confirm that Hospital Text Parser outputs one item per hospital and that Region Routing Switch routes to the correct sheet.
- Verify the Google Sheets lookup returns a row with fields like
Main EmailandHospital Name. - Check that Dispatch Gmail Email sends a personalized email to each hospital contact.
- When satisfied, switch the workflow to Active so it can receive incoming chat requests in production.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the n8n credential connection test and your Google account sharing access first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if your Google accounts are ready.
No. You’ll mostly connect Google credentials and edit a message template. The “code” part is already inside the workflow.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Google usage limits (usually negligible for basic Sheets and Gmail volumes).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s straightforward. Update the region routing in the “Region Routing Switch” so it matches your region names, then point each route to the right Google Sheets lookup node (or add a new one). For messaging, edit the subject and body in the “Dispatch Gmail Email” node and insert your own placeholders from the sheet columns. Common tweaks include adding a CC to a teammate, changing the sender alias, or pulling extra fields like department, phone, or procurement notes.
Usually it’s OAuth access or the sheet isn’t shared with the connected Google account. Reconnect the Google Sheets credential in n8n, then confirm the Sheet ID is correct in the configuration node and that the tab name matches the region route. If your sheet headers changed, the lookup can also “fail” by returning empty data, which then leaves Gmail with no recipient.
Practically, dozens to a few hundred per run is normal if your Gmail sending limits allow it. On n8n Cloud Starter, you’re also limited by monthly executions; each hospital typically counts as at least one execution cycle. If you self-host, there’s no execution cap, so the limit becomes your server resources and Google rate limits.
Often, yes, because this workflow needs routing by region, looping through a variable-length list, and clean handling when one hospital record is missing. n8n is comfortable with that kind of logic without turning into a maze of separate Zaps or scenarios. You also get the option to self-host, which is a big deal when you’re running outreach frequently. Zapier or Make can be simpler for a single “new row → send email” automation, but this one is more like a mini-campaign runner. If you want a quick recommendation for your exact outreach volume and compliance constraints, Talk to an automation expert.
Once this is running, outreach stops being a fragile weekly chore. The workflow handles the repetitive parts, so you can focus on the conversations that actually move deals forward.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
