n8n Workflow: Route Property Maintenance to Slack Queues

Route property maintenance requests to the right Slack queue—fast, safely, and with duplicate protection

This n8n workflow receives property maintenance requests via a webhook, validates the required fields, detects and suppresses repeated request_id submissions, classifies urgency using deterministic safety phrase matching, and posts each approved request to the appropriate Slack channel for human review—returning clear JSON acknowledgements along the way.

What this workflow does

• Receives incoming requests by handling a POST request on an n8n webhook endpoint.
• Validates and normalizes payload fields to ensure required inputs are present (e.g., request_id, tenant_name, contact, property_address, description).
• Blocks duplicates by suppressing repeated request_id submissions using workflow static data retention, returning a JSON response indicating duplication.
• Classifies priority (emergency/urgent/routine) using deterministic phrase matching against the request description and hint fields.
• Routes to the correct Slack queue: emergency requests go to a dedicated emergency Slack channel; all other requests are posted to a routine Slack channel.
• Returns status responses: a 400 JSON response when validation fails, and a 202 JSON acknowledgement only after Slack accepts the alert, confirming the request is queued for review.

Use cases

• Property management portals sending maintenance tickets to Slack for triage.
• Operations teams routing urgent issues (e.g., safety-related language) into an emergency review queue.
• SaaS operators needing consistent request validation, idempotency via request_id, and reliable human review handoff.

Technical details

• Nodes/tech stack: webhook, if, set, code, slack, plus supporting sticky note documentation.
• Setup: configure two Slack channels (emergency and routine) and add Slack credentials in n8n; then set your company name and replace channel IDs in the workflow.