Linen Tracking Automation
Cross-platform intake workflow.
A vacation rental company operating across hundreds of properties in North Georgia needed a form-based linen-tracking intake process covering what goes out, what comes back, and what gets flagged, routing data into a centralized log that the housekeeping team could access within Microsoft 365, where they already worked, but also accessible to a third-party laundering service.
Microsoft Forms was the natural starting point. No additional licensing, already in the environment. The problem: Microsoft Forms does not support conditional logic. A linen tracking form without conditional fields is too blunt. It cannot adapt to property type, linen category, or exception handling without presenting staff with an unusable wall of questions.
The options were to build something clunky and force staff to use it, or find another way.
Rather than compromise the form experience, the solution moved the form layer to Zoho Forms, which natively supports conditional logic, while keeping the data destination in SharePoint, where the housekeeping team already had access.
That required a bridge: a webhook-triggered automation in n8n that would receive Zoho Form submissions in real time and write structured records to a SharePoint List within the Housekeeping Teams site.
I had never used n8n before this project. The full build, from identifying the approach to a live working workflow, took one day.
Configured with scoped Microsoft Graph API permissions to allow programmatic write access to SharePoint without relying on a shared user account.
Structured inside the Housekeeping Teams site to serve as the central data destination, accessible to the team without any new tools or logins.
Conditional logic configured to handle property-specific inputs, linen categories, and exception scenarios. The piece Microsoft Forms could not do.
Triggered by Zoho webhook on each form submission. Parses the payload and writes a structured record to SharePoint via the Graph API with no manual transfer required.
The problem was not a lack of tools. The available tool had a specific limitation that required working around it through integration rather than replacement.
Choosing Zoho for its conditional logic, keeping SharePoint as the destination to preserve team access, using n8n to bridge the two, and building a proper Azure App Registration rather than a workaround: these decisions reflect a pattern across all of my systems work. Identify the right layer to solve the right problem, and build the minimum infrastructure needed to connect them cleanly.
The housekeeping team did not have to change how they work. They got a better form, and the data ended up exactly where it needed to be.
Microsoft Graph API
Azure App Registration
SharePoint configuration
Zoho Forms
Cross-platform integration
Rapid tool onboarding
Operational problem-solving
Leave a Reply