# IT and Maintenance Request Form with AI Priority > An internal request form where AI sets the priority and team, logs it to Google Sheets and emails a confirmation. What to ask, the rules, and the build. Source: https://learn.ynteractive.com/content/blog/it-help-desk-request-form-ai · Updated 2026-10-16 · Free from Stepthrough (https://learn.ynteractive.com) Quick answer An IT and maintenance request form gives staff one place to report what's broken, and an AI step can read each request, set a priority, assign a team, log it to a spreadsheet and email the person a confirmation. For operations managers and office managers who field these requests by email and hallway conversation, it replaces "did anyone see my message?" with a record and a reply. The free lesson [AI Maintenance & IT Request Form](https://learn.ynteractive.com/content/ai-maintenance-it-request-form-lovable-n8n) builds exactly this for a made-up warehouse business, using Lovable for the form and n8n for the AI. Last updated October 16, 2026 [Take the free module →](https://learn.ynteractive.com/courses/ai-for-operations/15)Module 15 of the free [AI for Operations Teams](https://learn.ynteractive.com/courses/ai-for-operations) course, about 15 minutes. No account needed. By [Robert Breen](https://learn.ynteractive.com/content/about) · Published October 16, 2026 · Updated October 16, 2026 · 6 min read Operations · Lovable · n8n This guide covers what the form should ask, how to write the priority rules, and how the pieces connect. ## What should an internal IT request form ask? Ask only what the person handling the request needs to start: who, how to reach them, what's wrong, and where. The lesson's form has four required fields: | Field | Why it's there | | --- | --- | | Name | Who to follow up with | | Email | Where the confirmation goes | | What needs fixing? | The request itself, in the person's own words | | Location | Where the problem is | Four fields is enough for most small offices. Every extra field is a reason for someone to skip the form and send an email instead. If you later find the team always asks the same follow-up question, add that one field. ## How does AI set the priority on a request? It follows rules you write in the [AI Agent](https://learn.ynteractive.com/content/glossary/ai-agent)'s [system message](https://learn.ynteractive.com/content/glossary/system-prompt), and those rules decide almost everything about how useful the form is. The lesson's system message for Ridgeline Supply Co.: ```text You are the maintenance and IT request assistant for Ridgeline Supply Co., a small warehouse business. Set a priority: Urgent (safety risk, or it stops shipping or receiving), This week, or Backlog. Assign one team: Facilities, IT, or Equipment. Use the google sheets tool to add the request to the google sheet. Use the gmail tool to email the requester a short confirmation with the priority and team. ``` Three priorities, each defined by what it means for the business, and three teams. That's the pattern to copy. "Urgent" isn't "the person sounds upset"; it's "safety risk, or it stops shipping or receiving." Write your own definitions the same way, in terms of what actually stops work in your office. The glossary entry on [AI triage](https://learn.ynteractive.com/content/glossary/ai-triage) explains the idea, and [How to Sort Requests with AI](https://learn.ynteractive.com/content/blog/ai-triage-rules) covers writing the rules in more depth. ## Try it free, step by step **Build an AI Maintenance and IT Request Form**. Build an internal maintenance and IT request form in Lovable for Ridgeline Supply Co. and connect it to n8n — the AI agent sets the priority, assigns a team, saves the request to Google Sheets and… You do every step yourself in a practice copy of Lovable and n8n, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts. [Start the free lesson](https://learn.ynteractive.com/modules/lovable-n8n-operations) [Or read the full step-by-step guide](https://learn.ynteractive.com/content/ai-maintenance-it-request-form-lovable-n8n) ## How do I build the form without coding? Describe it to Lovable in a prompt. The lesson's prompt sets the fields, the heading, the wording on screen and the rules: - Heading: **Report a Problem**, with the line "Tell us what's broken and where. We'll set the priority and confirm by email." - While sending, the button says **Sending...** - On success: "Request received! Check your email for the priority." - On failure: "Something went wrong. Please tell your supervisor." - All four fields required, and the email format validated. - The data goes to n8n as JSON with the keys **name**, **email**, **request** and **location**. That failure message is a nice internal touch: if the form breaks, people know to tell a person instead of assuming it worked. [What Is Vibe Coding?](https://learn.ynteractive.com/content/blog/what-is-vibe-coding) explains how this kind of prompt-built form works. ## How does the form connect to n8n? Through a webhook. The workflow starts with **On webhook call**, set to respond **Using 'Respond to Webhook' Node** so the form waits for the work to finish. Then: 1. An **AI Agent** reads the request, with its prompt source set to **Define below** and a template that pulls in each field, such as `{{ $json.body.request }}`. 2. An **OpenAI Chat Model** gives it a model; the lesson picks **gpt-5-mini**. 3. A **Google Sheets Tool** appends the request to a sheet named **Requests** with the columns Name, Email, Request and Location. 4. A **Gmail Tool** emails the requester the priority and team. 5. A **Respond to Webhook** node tells the form it worked. You click **Publish**, open the Webhook node's **Production URL** tab, copy the URL, and save it in Lovable under **More** as the secret **N8N_WEBHOOK_URL**. The general version of this build is [Build a Web App with an AI Backend](https://learn.ynteractive.com/content/lovable-n8n-web-app-ai-backend), and [n8n Webhook Test URL vs Production URL](https://learn.ynteractive.com/content/blog/n8n-webhook-test-vs-production-url) explains why the production URL matters. ## Should I log the priority and team in the sheet too? It's a useful addition once the basic form works. The lesson's sheet keeps the four form fields, and the priority and team go to the requester by email. If you want to sort the backlog by priority, add **Priority** and **Team** columns to the sheet and map them in the Google Sheets Tool with the ✦ button, so the agent fills them in. Then the sheet becomes the list your facilities and IT people work from. ## What should a person still check? Anything marked Urgent, and anything involving safety. AI can sort a clear request well, but it can misread a vague one, such as "the door is acting weird." A quick daily look at the sheet catches requests that landed in the wrong team or priority. Two other habits help: - **Tell staff what Urgent means.** Put your definition on the form or in the confirmation, so people learn to describe the impact, not just the problem. - **Keep a real escalation path.** For a safety risk, people should still call or find a supervisor. The form is for the record, not for emergencies. The glossary entry on [escalation](https://learn.ynteractive.com/content/glossary/escalation) has more. On cost: the lessons are free practice copies. A real build uses Lovable and n8n Cloud, which both have paid plans, and OpenAI API credit, which is pay-as-you-go and separate from ChatGPT plans. The [operations industry page](https://learn.ynteractive.com/content/industry/operations) lists more lessons for operations teams. ## Key takeaways - An internal request form needs four fields for most offices: name, email, what needs fixing and location. - The AI Agent's system message sets the rules; the lesson defines Urgent as a safety risk or anything that stops shipping or receiving. - Lovable builds the form from a prompt, and n8n receives each submission through a webhook. - The n8n workflow uses an AI Agent, a Google Sheets Tool, a Gmail Tool and a Respond to Webhook node. - A person should still review Urgent and safety-related requests, and emergencies need a real escalation path, not just a form. ## Frequently asked questions **Can AI really decide the priority of an IT request?** It can apply rules you write, such as "Urgent means a safety risk or it stops shipping." Clear definitions make it reliable; vague ones make it guess. Review Urgent requests yourself. **Do I need separate forms for IT and facilities?** Not with this setup. One form collects every request, and the AI assigns a team, such as Facilities, IT or Equipment, from the description. **What happens if the form fails to send?** The lesson's form shows "Something went wrong. Please tell your supervisor." so the person knows to report it another way. **Does this cost anything to run?** The lesson is free. A real version uses Lovable and n8n Cloud, which have paid plans, plus OpenAI API credit billed per request. ## Free lessons in this post - [Build an AI Maintenance and IT Request Form](https://learn.ynteractive.com/content/ai-maintenance-it-request-form-lovable-n8n): Build an internal maintenance and IT request form in Lovable for Ridgeline Supply Co. and connect it to n8n — the AI agent sets the priority, assigns a team, saves the… - [Lovable + n8n: Build a Web App with an AI Backend](https://learn.ynteractive.com/content/lovable-n8n-web-app-ai-backend): Build a contact form in Lovable and connect it to an n8n workflow — webhook trigger, AI Agent, Google Sheets, Gmail, and a Respond node that ties it all together. ## Watch it in a free lesson: Lovable + n8n: Build a Web App with an AI Backend ### Build a Web App with an AI Backend: video walkthrough Full walkthrough · 9:03 · with captions Build a contact form in Lovable and connect it to an n8n workflow — webhook trigger, AI Agent, Google Sheets, Gmail, and a Respond node that ties it all together. The whole lesson narrated step by step, recorded in Stepthrough’s simulated practice environment. [Watch it with chapters and the full transcript](https://learn.ynteractive.com/content/lovable-n8n-web-app-ai-backend#watch) From the free lesson [Lovable + n8n: Build a Web App with an AI Backend](https://learn.ynteractive.com/content/lovable-n8n-web-app-ai-backend) ## Related terms Plain-English definitions, each with an example from a free lesson. Work order · [AI agent](https://learn.ynteractive.com/content/glossary/ai-agent) · [System prompt (system message)](https://learn.ynteractive.com/content/glossary/system-prompt) · Change management · [Deployment (publishing a web app)](https://learn.ynteractive.com/content/glossary/web-app-deployment) · Employee offboarding · Integration · No-code (and low-code) [The full AI glossary](https://learn.ynteractive.com/content/glossary) ## Related prompts - [IT and maintenance request reply prompt](https://learn.ynteractive.com/content/prompts/internal-it-request-reply-prompt): Update a coworker on their IT or maintenance request: where it stands, a workaround, when they'll hear next, and no fix time… - [Knowledge base article from a ticket prompt](https://learn.ynteractive.com/content/prompts/knowledge-base-article-from-ticket-prompt): Turn a solved support or IT ticket into a short help article: symptoms, cause, steps to fix it and when to ask for help, so the… - [Maintenance request triage prompt](https://learn.ynteractive.com/content/prompts/maintenance-request-triage-prompt): Sort a pile of maintenance and IT requests by priority and team, with the words that drove each call quoted and vague requests… - [Monthly operations report prompt](https://learn.ynteractive.com/content/prompts/monthly-operations-report-prompt): A ChatGPT prompt for a monthly operations report: this month against last month and target, what drove the big moves, open… [All free prompt templates](https://learn.ynteractive.com/content/prompts) ## Visual guides The same ideas as quick visual guides: swipe through the slides, or read each one as text. - [Build a web form with an AI backend, no code](https://learn.ynteractive.com/content/visual/lovable-n8n-form): Most website forms just land in an inbox and wait. This one does the work. You describe the form in Lovable, and it builds it. - [Mistake to Avoid: Testing an Unpublished n8n Workflow](https://learn.ynteractive.com/content/visual/mistake-testing-an-unpublished-workflow): A visual tip: an n8n production webhook URL only works once the workflow is published. Publish first, then copy the URL into your app. - [n8n Webhook URL: Don't Paste It into Your Page](https://learn.ynteractive.com/content/visual/mistake-webhook-url-in-the-page): Where should your n8n webhook URL go? Not in the page code. Store it as a Lovable secret so it stays out of the source and is easy to change. [All visual guides](https://learn.ynteractive.com/content/visual) ## Keep reading - [What Is a Webhook? Explained in Simple Words (With Example)](https://learn.ynteractive.com/content/blog/what-is-a-webhook): A webhook is a way for one app to tell another app something just happened. Explained in simple words, with a form-to-n8n example and which URL to use. - [n8n Webhook Test URL vs Production URL, Explained](https://learn.ynteractive.com/content/blog/n8n-webhook-test-vs-production-url): n8n webhook test URL vs production URL: why a form works while you test, then stops live, and the fixes for Publish, Respond and $json.body. - [AI for Operations Teams: Vendor Follow-Ups and Requests](https://learn.ynteractive.com/content/blog/ai-for-operations-teams): AI for operations managers: an n8n agent that chases late purchase orders with reply-by dates, and a request form that sets priority and team. [All blog posts](https://learn.ynteractive.com/content/blog) · [All free tutorials](https://learn.ynteractive.com/content)