Send package and visitor alerts with Slack, SMS, email, Google Sheets and Claude

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

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Who this is for Property management teams handling multiple properties with high package/visitor traffic who want automated tenant and management notifications. What this workflow does Automaticall...

Best for

Miscellaneous automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.webhook, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.chainllm, @n8n/n8n-nodes-langchain.lmchatanthropic, n8n-nodes-base.switch, n8n-nodes-base.emailsend, n8n-nodes-base.sms77, n8n-nodes-base.slack

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: Send package and visitor alerts with Slack, SMS, email, Google Sheets and Claude
Workflow name: Send package and visitor alerts with Slack, SMS, email, Google Sheets and Claude

Who this is for

Property management teams handling multiple properties with high package/visitor traffic who want automated tenant and management notifications.

What this workflow does

Automatically classifies package and visitor events, sends notifications to tenants, alerts property managers, and logs activity for accountability.

How it works

Package/visitor system triggers workflow.
AI classifies urgency and type.
Notifications sent via Email, SMS, and Slack.
Google Sheets logs all events.
Optional AI follow-up suggestions for unclaimed packages or missed visitors.

How to set up

Connect Webhook, Slack, Email, SMS, and AI. Test routing and logging. Adjust AI prompts for local building protocols.

Requirements

AI Node
Webhook from package/visitor system
Slack, Email, SMS credentials
Google Sheets

Built by QuarterSmart. Created by Hyrum Hurst.

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 - Package/Visitor Webhook

Type / Role: n8n-nodes-base.webhook - webhook
Config choices: Version 2.1

Block 2 - Workflow Configuration

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

Block 3 - Normalize Data

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

Block 4 - Classify Urgency

Type / Role: @n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices: Version 1.7

Block 5 - Anthropic Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices: Version 1.3

Block 6 - Route by Urgency

Type / Role: n8n-nodes-base.switch - switch
Config choices: Version 3.3

Block 7 - Email Tenant - High Urgency

Type / Role: n8n-nodes-base.emailSend - emailSend
Config choices: Version 2.1

Block 8 - Email Tenant - Regular

Type / Role: n8n-nodes-base.emailSend - emailSend
Config choices: Version 2.1

Block 9 - SMS Tenant - High Urgency

Type / Role: n8n-nodes-base.sms77 - sms77
Config choices: Version 1

Block 10 - Notify Management

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

Block 11 - Log to Google Sheets

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

Block 12 - Merge Notification Branches

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 13 - Suggest Follow-up

Type / Role: @n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices: Version 1.7

Block 14 - Urgency Output Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.3

Block 15 - Anthropic Chat Model 2

Type / Role: @n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices: Version 1.3

Block 16 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 17 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 18 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 19 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 20 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Send package and visitor alerts with Slack, SMS, email, Google Sheets and Claude
Complexity	advanced
Nodes	20
Categories	Miscellaneous, AI Summarization
Author	Hyrum Hurst
Published	03 Jan 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/12430/12430.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 Miscellaneous workflows AI Summarization workflows

Frequently asked questions

What does Send package and visitor alerts with Slack, SMS, email, Google Sheets and Claude 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 Miscellaneous, AI Summarization use case.

Hyrum Hurst

25 workflows

Nodes

n8n-nodes-base.webhook n8n-nodes-base.set @n8n/n8n-nodes-langchain.chainllm @n8n/n8n-nodes-langchain.lmchatanthropic n8n-nodes-base.switch n8n-nodes-base.emailsend n8n-nodes-base.sms77 n8n-nodes-base.slack

Complexity

advanced

Published 03 Jan 2026

Likes 0

View on n8n.io Download Workflow

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

Share Your Workflow

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

Submit Your Template How to Submit

Related Workflows

Predict airport queue wait times and email alerts with OpenAI and SendGrid

## Quick Overview This workflow accepts traveler flight details via webhook or runs every 5 minutes, predicts airport queue wait times with a custom JavaScript model, generates an alert message using OpenAI, emails the traveler via SendGrid, and logs the prediction to Google Sheets. ## How it works 1. Receives a POST request to a webhook with traveler/flight details or runs on a 5-minute schedule. 2. Normalizes the incoming data into a consistent context (flight, airport/terminal, traveler contact details, and live queue inputs). 3. Waits briefly to throttle processing, then calculates predicted security, immigration, and boarding wait times plus risk flags and an optimal arrival time. 4. Sends the prediction to OpenAI to generate a short, traveler-friendly alert message. 5. Formats the final alert payload (alert level, email subject/body) and prepares a row for tracking. 6. Sends the alert email through the SendGrid Mail Send API and appends the prediction record to a Google Sheets tab. ## Setup 1. Configure the webhook URL in the system that submits traveler requests (POST to `/airport-queue-check`) or enable the schedule trigger for proactive runs. 2. Add OpenAI credentials and select the chat model used to generate the traveler message. 3. Add Google Sheets OAuth2 credentials and replace `YOUR_SHEET_ID` and the target range (for example, `Predictions!A1:append`) in the Google Sheets request URL. 4. Add your SendGrid API key by replacing `YOUR_SENDGRID_API_KEY` in the Authorization header, and update the sender/recipient fields (including ensuring `travelerEmail` is provided by the trigger payload).

View

Send transactional SMS with the OVHcloud SMS API

## Quick overview This workflow manually triggers an HTTP request to the OVHcloud SMS API, signing it with your OVH application credentials to send a transactional SMS to a specified phone number. ## How it works 1. Runs when you manually execute the workflow. 2. Sets the OVHcloud API credentials, SMS service name, sender, and target API region. 3. Defines the SMS recipient number and message text to send. 4. Generates the OVHcloud request URL, JSON body, timestamp, and SHA1-based X-Ovh-Signature headers. 5. Sends a POST request to the OVHcloud endpoint `/sms/{serviceName}/jobs` to create an SMS sending job. ## Setup 1. Create OVHcloud API application credentials (Application Key and Application Secret) and a Consumer Key with SMS permissions. 2. Replace the placeholder values for `APPLICATION_KEY`, `APPLICATION_SECRET`, `CONSUMER_KEY`, `SMS_SERVICE_NAME`, `SMS_SENDER`, and `OVH_REGION`. 3. Update the `receiver` (E.164 format) and `message` fields with the SMS details you want to send, and ensure your OVHcloud SMS account has available credits. ## Requirements - OVH account - SMS credits (API account)

View

Tutor English chat messages using OpenRouter with Postgres memory and log to Supabase

## Quick overview This workflow receives English practice messages via a webhook, uses an OpenRouter chat model with Postgres-backed conversation memory to generate tutoring feedback, logs the exchange to Supabase, and returns the tutor’s reply as a JSON response. ## How it works 1. Receives a POST webhook request containing a `user_id` and `message`. 2. Extracts and standardizes the incoming fields so the workflow has clean `user_id` and `message` values. 3. Sends the message to an AI English tutor powered by OpenRouter, using Postgres chat memory keyed by `user_id` to maintain per-student context. 4. Logs the tutor output to a Supabase `conversations` table along with the user identifier and original message. 5. Returns a JSON response to the caller containing the tutor’s reply. ## Setup 1. Add an OpenRouter API credential and (optionally) choose a different model in the OpenRouter chat model configuration. 2. Add Postgres credentials and ensure the database is reachable from n8n so chat memory can persist sessions by `user_id`. 3. Add Supabase credentials and create a `conversations` table, then confirm the mapped columns (`user_id`, `role`, `message`) match your schema. 4. Copy the webhook URL from n8n and configure your app to POST a JSON body with `user_id` and `message` to that endpoint.

View

Need Custom Automation?

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

Send package and visitor alerts with Slack, SMS, email, Google Sheets and Claude

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Who this is for

What this workflow does

How it works

How to set up

Requirements

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Package/Visitor Webhook

Block 2 - Workflow Configuration

Block 3 - Normalize Data

Block 4 - Classify Urgency

Block 5 - Anthropic Chat Model

Block 6 - Route by Urgency

Block 7 - Email Tenant - High Urgency

Block 8 - Email Tenant - Regular

Block 9 - SMS Tenant - High Urgency

Block 10 - Notify Management

Block 11 - Log to Google Sheets

Block 12 - Merge Notification Branches

Block 13 - Suggest Follow-up

Block 14 - Urgency Output Parser

Block 15 - Anthropic Chat Model 2

Block 16 - Sticky Note

Block 17 - Sticky Note1

Block 18 - Sticky Note2

Block 19 - Sticky Note3

Block 20 - Sticky Note4

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