Send customer visit notifications from Google Calendar to Slack and Sheets

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Customer Visit Notification This workflow monitors Google Calendar for events indicating that a customer will visit the company today or the next day, retrieves the required details, and sends remi...

Best for

Internal Wiki automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.googlecalendar, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.filter, n8n-nodes-base.googlesheets, n8n-nodes-base.splitinbatches

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by BHSoft.

Original n8n.io source

1.1 Workflow description

Title: Send customer visit notifications from Google Calendar to Slack and Sheets
Workflow name: Send customer visit notifications from Google Calendar to Slack and Sheets

Customer Visit Notification

This workflow monitors Google Calendar for events indicating that a customer will visit the company today or the next day, retrieves the required details, and sends reminder notifications to the relevant stakeholders. It also posts a company-wide announcement to ensure proper preparation and a professional reception for the customer.

📌Who is this for?

Reception / Administration team
Sales / Account owners in charge of customers
Management / Related team leaders
Security / IT / Logistics (for meeting room, equipment, and check-in preparation)

📌The problem

Customer visit information is usually shared manually and can be easily missed.
Related staff are not informed in time to prepare.
This causes last-minute preparation for reception, meeting rooms, documents, and support.
It affects the customer experience and the company’s professional image.

📌How it works

When a customer meeting is scheduled, the system records the information (time, customer name, company, person in charge).
The system automatically sends notifications to related groups based on timeline:
Notify the whole office 1 hour before the visit.
Notify related members 24 hours in advance.
Notifications can be sent via Email / Slack / Internal chat.

📌Quick setup

Required information:

N8n Version 2.4.6
Google Calendar OAuth2 API: Client ID, Client Secret
Google Sheets OAuth2 API: Client ID, Client Secret
Slack App: Bot User OAuth Token

Google Sheets will be used to log all notified events.

📌Results

Everyone is aware of the customer visit schedule.
Teams can proactively prepare meeting rooms, documents, and manpower.
Reduce mistakes and missed communication.
Improve customer experience and company professionalism.

📌Take it further

Customer check-in using QR code / Visitor form
Send reminders to prepare documents
Store visit history
Monthly/quarterly reports for number of customer visits

📌Need help customizing?

Contact me for consulting and support: Linkedin / Website

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Step 1: Activation schedule: Every 1 hour, from 6 AM to 6 PM.

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.2

Block 2 - Step 4: Get the event information from Google Calendar for tomorrow.

Type / Role: n8n-nodes-base.googleCalendar - googleCalendar
Config choices: Version 1.3

Block 3 - Step 2: Set Variables

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 4 - Step 3: Get datetime

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 5 - Step 5: Check if there is a record or not?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 6 - Step 6: Filter out events whose titles match the action of a customer visiting the company.

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.3

Block 7 - Step 7: Check if there is a record or not?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 8 - Step 8: Read the Odoo Calendar Event notifications that have been sent.

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 9 - Step 9: Read Google Sheets member slack

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.5

Block 10 - Step 10: Filter out records that have not been sent.

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 11 - Step 11: Check if there is a record or not?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 12 - Step 12: Loop Over Items

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 13 - Step 13: Extract the email and member ID of the partners.

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 14 - Step 14: Loop Over Partners.

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 15 - Step 15: Wait 1s

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 16 - Step 16: Send a message to your Partners

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 17 - Step 17: Return output of step8

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 18 - Step 18: Loop Over Items

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 19 - Step 19: Fill in the Calendar Event information in the Google Sheet.

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 20 - Step 20: Get the event information from Google Calendar for today..

Type / Role: n8n-nodes-base.googleCalendar - googleCalendar
Config choices: Version 1.3

Block 21 - Step 21: Check if there is a record or not?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 22 - Step 22: Filter out events whose titles match the action of a customer visiting the company.

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.3

Block 23 - Step 23: Check if there is a record or not?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 24 - Step 24: Read the Odoo Calendar Event notifications that have been sent.

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Showing the first 24 of 61 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Send customer visit notifications from Google Calendar to Slack and Sheets
Complexity	advanced
Nodes	61
Categories	Internal Wiki
Author	BHSoft
Published	30 Jan 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/13111/13111.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Internal Wiki workflows

Frequently asked questions

What does Send customer visit notifications from Google Calendar to Slack and Sheets do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Internal Wiki use case.

BHSoft

5 workflows

Nodes

n8n-nodes-base.scheduletrigger n8n-nodes-base.googlecalendar n8n-nodes-base.set n8n-nodes-base.code n8n-nodes-base.if n8n-nodes-base.filter n8n-nodes-base.googlesheets n8n-nodes-base.splitinbatches

Complexity

advanced

Published 30 Jan 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/13111/13111.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Build a RAG knowledge base from PDFs with Gemini, Supabase and Google Sheets

## Quick Overview This workflow ingests educational PDF URLs from Google Sheets, extracts and chunks their text, generates embeddings with Google Gemini, and stores them in a Supabase pgvector table for retrieval, while also exposing a public chat webhook that answers questions using Gemini and the same Supabase knowledge base. ## How it works 1. Runs every hour on a schedule and reads rows from a Google Sheets document, keeping only entries where the status is empty. 2. Processes each queued URL one at a time and routes it based on whether it is a seraj-uae.com page or a direct Google Drive file link. 3. For seraj-uae.com URLs, fetches the HTML page to extract the PDF download link (or embedded Google Drive file ID) and the document title. 4. Downloads the PDF from either the source website via HTTP or from Google Drive, waits briefly, and extracts text from the PDF binary. 5. Cleans and validates the extracted text, then splits it into overlapping chunks and generates embeddings using Google Gemini. 6. Inserts the embedded chunks into a Supabase pgvector table with file/title/source metadata and updates the Google Sheets row to “Embedded” or “Not Text Based PDF” if no text is found. 7. Separately, exposes a public n8n Chat webhook that receives student questions and uses Gemini Flash with Supabase vector retrieval to return answers. ## Setup 1. Create a Supabase project with pgvector enabled, create the seraj_documents table, and add the match_seraj_documents function used for vector search. 2. Add Supabase API credentials in n8n and ensure the table name (seraj_documents) and query function name (match_seraj_documents) match your Supabase setup. 3. Add Google Sheets OAuth2 credentials and update the Google Sheet document ID/sheet reference, ensuring columns include source_url, status, and row_number. 4. Add Google Drive OAuth2 credentials for downloading PDFs hosted in Drive. 5. Add a Google Gemini (PaLM) API credential for embeddings and Gemini Flash, then activate the workflow and copy the public chat webhook URL for your website chat widget.

View

Build a Slack knowledge graph with Claude, Neo4j and Google Sheets

## Quick Overview This workflow ingests chat messages via a webhook or a 15-minute schedule, filters out low-signal content, uses Anthropic Claude to extract entities and relationships, and stores the resulting knowledge graph in Neo4j while appending an audit log row to Google Sheets. ## How it works 1. Receives a chat message via an n8n webhook or runs every 15 minutes to process polled Slack data. 2. Normalizes the incoming payload into consistent fields like channel, sender, timestamp, and message text. 3. Uses a Python script to tag message signals (questions, decisions, action items) and filter out noise such as greetings, bots, and very short messages. 4. Sends each relevant message to Anthropic Claude to extract entities, relationships, a summary, message type, and importance. 5. Sends the extracted graph to Anthropic Claude again to add implicit relationships, weights, decision-chain metadata, and a thread category. 6. Merges both AI passes into a single nodes-and-edges knowledge graph, validates references and edge weights, and drops invalid graphs. 7. Upserts the graph into Neo4j via its transactional HTTP endpoint, appends an audit row to Google Sheets, and returns a JSON success response to the webhook caller. ## Setup 1. Add an Anthropic API credential and select the Claude model used by the two AI steps. 2. Configure Neo4j access by replacing the Neo4j HTTP endpoint URL and setting up HTTP Basic Auth credentials for your Neo4j instance. 3. Configure Google Sheets OAuth2 credentials and replace the placeholder Google Sheet ID, sheet tab name/range (KnowledgeGraph), and any required API permissions. 4. If using the webhook ingest path, copy the production webhook URL from n8n and configure your Slack/app integration to POST message payloads to `/chat-ingest` with the expected fields (text, channel, sender, timestamps).

View

Answer voice queries from a webhook over Google Drive docs using GPT-4o-mini and Supabase

## Quick overview Placetel AI – RAG Voice Assistant with Google Drive & Supabase ## How it works 1. Runs on a daily schedule at 02:00 or via manual start to reindex documents. 2. Lists files from a specified Google Drive folder and iterates through each file. 3. Downloads each Google Drive file, loads its text content, creates embeddings with OpenAI, and stores the resulting chunks in a Supabase vector table. 4. Receives a question via a POST webhook with a JSON body containing `chatInput`. 5. Generates an answer with GPT-4o-mini by semantically retrieving relevant passages from the Supabase vector store using the same OpenAI embeddings model. 6. Returns the generated, source-cited response to the webhook caller for voice output. ## Setup 1. Add Google Drive OAuth2 credentials and replace `DEINE_ORDNER_ID` in the Drive query with the folder you want to index. 2. Add an OpenAI API credential and ensure the same embeddings model/settings are used for both indexing and querying. 3. Create/configure a Supabase project with a `documents` table and the `match_documents` RPC/query used for vector search, then add your Supabase credentials. 4. Copy the webhook URL from the webhook trigger and configure your calling system to POST `{ "chatInput": "..." }` to it.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Send customer visit notifications from Google Calendar to Slack and Sheets

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Customer Visit Notification

📌Who is this for?

📌The problem

📌How it works

📌Quick setup

📌Results

📌Take it further

📌Need help customizing?

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Step 1: Activation schedule: Every 1 hour, from 6 AM to 6 PM.

Block 2 - Step 4: Get the event information from Google Calendar for tomorrow.

Block 3 - Step 2: Set Variables

Block 4 - Step 3: Get datetime

Block 5 - Step 5: Check if there is a record or not?

Block 6 - Step 6: Filter out events whose titles match the action of a customer visiting the company.

Block 7 - Step 7: Check if there is a record or not?

Block 8 - Step 8: Read the Odoo Calendar Event notifications that have been sent.

Block 9 - Step 9: Read Google Sheets member slack

Block 10 - Step 10: Filter out records that have not been sent.

Block 11 - Step 11: Check if there is a record or not?

Block 12 - Step 12: Loop Over Items

Block 13 - Step 13: Extract the email and member ID of the partners.

Block 14 - Step 14: Loop Over Partners.

Block 15 - Step 15: Wait 1s

Block 16 - Step 16: Send a message to your Partners

Block 17 - Step 17: Return output of step8

Block 18 - Step 18: Loop Over Items

Block 19 - Step 19: Fill in the Calendar Event information in the Google Sheet.

Block 20 - Step 20: Get the event information from Google Calendar for today..

Block 21 - Step 21: Check if there is a record or not?

Block 22 - Step 22: Filter out events whose titles match the action of a customer visiting the company.

Block 23 - Step 23: Check if there is a record or not?

Block 24 - Step 24: Read the Odoo Calendar Event notifications that have been sent.

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions