--- title: "Create monday.com tickets from problem reports" description: "Turn every \"Report a problem\" submission into an Open item on your monday.com support board, with the description and the reporter's priority already set." url: "https://www.formformform.com/automations/monday-problem-reports-to-triage" type: static generatedAt: "2026-08-23T18:56:58.727Z" --- ![monday.com logo](/logos/integrations/monday.png) # Log problem reports as tickets on a triage board Reported problems open as items on your support board, carrying the description and the priority the reporter chose. When this happens New submission on your "Report a problem" form Do this Create an item on your Support board with the issue text in a Long Text column, the Priority column set from a form field, and Status set to "Open" One-directional. A submission triggers the action — nothing is written back into your form. Support teams that live on a monday.com board need every report to arrive in the same shape: a subject on the row, the full description underneath, and a priority they can sort by. This flow creates that item the moment somebody submits the problem form. Internal IT desks reach for it first. The reporter picks a priority, the item opens on the board, and an agent claims it by dropping their name into the People column — with no separate ticketing tool sitting in the middle. ## Setting it up 1. 1 Publish your "Report a problem" form. The IT Help Desk Ticket template already collects Priority and Issue Type, which is what the board will sort and group on. 2. 2 On the Support board, check that the Priority column's labels match the choices offered on the form word for word — Low, Medium, High and so on. 3. 3 Confirm the Status column carries an "Open" label, and leave the People column empty so agents can assign themselves after triage. 4. 4 In Zapier, point the formformform "New Submission" trigger at the problem form and add the monday.com "Create Item" action on the Support board. 5. 5 Use Ticket Subject as the item name, so the board reads as a list of problems rather than a list of colleagues. 6. 6 Map Issue Description into the Long Text column, Priority into the Priority column, and set Status to "Open" as a fixed value on the action step. 7. 7 Map Work Email and Department as well, so an agent can reply and know which floor the report came from without asking. 8. 8 Submit one test report at each priority level, confirm every label resolves on the board, then turn the Zap on. ## What maps where Using the [IT Help Desk Ticket](https://www.formformform.com/templates/it-help-desk-form) as the starting point. These are its real fields — swap in your own and the mapping works the same way. Form field monday.com Ticket Subject Item name on the Support board Issue Description Long Text column on the item Priority Priority status column Issue Type Category dropdown column Work Email Email column for replies Department Department text column ## Variations worth knowing Send urgent reports to an on-call board A filter on Priority splits the flow in two. Urgent creates its item on a board the on-call agent watches all day, while everything else joins the normal Support queue for the next triage pass. Let Issue Type choose the group Boards that keep a group per category — hardware, access, software — can take Issue Type as the group rather than a column. Triage is then finished before anyone has opened the item. ## If something isn't arriving Priority arrives empty on some tickets. monday.com discards a label it does not recognise, so a form answer of "Very high" cannot land in a column that only holds Low, Medium and High. Align the two lists, or add a Zapier Formatter step that rewrites the form's wording into the column's labels. Long descriptions are cut short on the item. A plain Text column truncates. Long Text holds the whole answer, including line breaks. Change the column type on the board first, then re-point the Issue Description mapping at it and re-test. ## Frequently asked questions Can an agent reply to the reporter from the board? Not through this connection, which only writes into monday.com. Reply using monday.com's own email features or your normal mail client, addressed to the Work Email that arrived on the item. The form receives nothing back. What happens if somebody reports the same fault twice? Two submissions create two items. Zapier cannot see what is already on the board. Most teams let the duplicates land and merge them during triage, since a lookup step tends to miss near-matches and quietly drop real reports. Do people who report problems need a monday.com seat? No. Respondents only ever see a form. Seats are needed by the agents working the Support board, which is the main reason teams route reports through a form instead of handing out guest access to everyone. ## Related automations - [Add new sales leads to your pipeline board](https://www.formformform.com/automations/monday-sales-enquiries-to-pipeline) Each sales enquiry lands in the New leads group of your CRM board, tagged "New lead" and ready to work. - [Build a guest list from every event RSVP](https://www.formformform.com/automations/monday-rsvps-onto-guest-board) RSVPs build your attendee board as they arrive, keeping headcount and ticket mix current without manual entry. - [Drop new applications into the Applied group](https://www.formformform.com/automations/monday-applicants-into-applied-stage) Each application becomes an item in the Applied group of your recruiting board, tagged with the role applied for. - [Log survey feedback on your product board](https://www.formformform.com/automations/monday-feedback-onto-product-board) Survey responses land on your product board as tagged items you can group by theme during planning. - [Track custom order requests on a fulfilment board](https://www.formformform.com/automations/monday-custom-orders-to-fulfilment) Custom order requests arrive as To do items on your orders board, with quantity in a numbers column. - [Add every RSVP to your confirmed guest list](https://www.formformform.com/automations/trello-rsvps-to-guest-list) Each RSVP creates a card on the "Confirmed guests" list with the ticket type as a label and dietary notes in the description. - [All monday.com integration details →](https://www.formformform.com/integrations/monday) - [Start from the IT Help Desk Ticket →](https://www.formformform.com/templates/it-help-desk-form) - [Browse every automation →](https://www.formformform.com/automations) ## Build the form first The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow. [Start free](https://app.formformform.com/register?utm_source=landing&utm_medium=bottom&utm_campaign=automations&utm_content=monday-problem-reports-to-triage)