Send package and visitor alerts with Slack, SMS, email, Google Sheets and Claude
Ready for 3.0What this workflow does
This AI workflow has 15 nodes and runs when an HTTP GET request hits its webhook URL. Along the way it connects Anthropic Chat Model, seven, Slack and Google Sheets.
How it runs
Trigger: When an HTTP GET request hits its webhook URL.
- Workflow Configuration (Edit Fields (Set)): sets or maps fields
- Normalize Data (Edit Fields (Set)): sets or maps fields
- Classify Urgency (Basic LLM Chain): sends a prompt to an LLM, with model: Anthropic Chat Model; output parser: Urgency Output Parser
- Route by Urgency (Switch): routes items into branches
- Email Tenant - High Urgency (Send Email): sends an email over SMTP
- Notify Management (Slack): uses Slack
- Email Tenant - Regular (Send Email): sends an email over SMTP
- SMS Tenant - High Urgency (seven): uses seven
- Merge: merges the data from its input branches
- Log to Google Sheets (Google Sheets): uses Google Sheets
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (11)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - Anthropic Chat Model
@n8n/n8n-nodes-langchain.lmChatAnthropic - Switch
n8n-nodes-base.switch - Send Email
n8n-nodes-base.emailSend - seven
n8n-nodes-base.sms77 - Slack
n8n-nodes-base.slack - Google Sheets
n8n-nodes-base.googleSheets - Merge
n8n-nodes-base.merge - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured
From the author
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…