--- title: "Save bug reports to a OneDrive support folder" description: "Turn each bug report into a triage-ordered file in OneDrive, carrying the reproduction steps, the environment details and the reporter's screenshot link." url: "https://www.formformform.com/automations/onedrive-bug-report-evidence-files" type: static generatedAt: "2026-08-23T18:56:58.727Z" --- ![OneDrive logo](/logos/integrations/onedrive.ico) # File each bug report where support can find it Each bug report becomes a file in a OneDrive support folder, ordered by severity and carrying the screenshot link. When this happens New submission on your support or bug-report form Do this Create a text file for the report in a Support folder in OneDrive, carrying the steps and the screenshot link One-directional. A submission triggers the action — nothing is written back into your form. A bug report is read twice: once by the agent who takes it, and again weeks later by whoever finally reproduces it. The second reading is the one that fails, because by then the thread has been closed, reopened, and passed between three people. Support teams that keep a OneDrive folder alongside the helpdesk get a copy that outlives the ticket. The reproduction steps, the environment and the link to the screenshot sit in one plain file, searchable from the drive, and nobody needs a licence for the ticket system to read it. ## Setting it up 1. 1 Publish the Bug Report Form template and add a File Upload question so a reporter can attach the screenshot directly, up to 2 MB. Screenshot or Video Link is already on the template — keep it for a screen recording, a full-resolution capture, or anything past that limit. 2. 2 Add conditional logic so a Severity of critical reveals a short question about who is affected, and lower severities skip past it. 3. 3 In Zapier, create a Zap on formformform's New Submission trigger and select the bug form. 4. 4 Add OneDrive as the action app, choose Create New Text File, and connect the Microsoft account behind your support drive. 5. 5 Send everything to /Support/Bugs, or split on Severity so /Support/Bugs/Critical is a folder one person can be asked to watch. 6. 6 Name each file with Severity first and Bug Title second, so the folder listing reads as a triage queue rather than an arrival order. 7. 7 Lay the body out the way an engineer works: Screenshot or Video Link and URL Where the Bug Occurs at the top, then Steps to Reproduce, then the expected and actual behaviour. 8. 8 File a test bug, confirm the link inside the file opens for a colleague and not only for you, then turn the Zap on. ## What maps where Using the [Bug Report Form](https://www.formformform.com/templates/bug-report-form) as the starting point. These are its real fields — swap in your own and the mapping works the same way. Form field OneDrive Severity Front of the OneDrive file name, so the folder sorts the serious ones to the top Bug Title Rest of the file name, after the severity marker Screenshot or Video Link Body, on its own line near the top so an agent opens the evidence first URL Where the Bug Occurs Body, in the environment block Browser / Device Body, in the environment block beside the URL Steps to Reproduce Body, under its own heading, ahead of the expected and actual behaviour ## Variations worth knowing Raise the ticket in the same run Add a Freshdesk or Help Scout action after the OneDrive step. One submission then produces both a ticket for the agent and a plain file on the drive, and the two stay in step because they came from the same trigger rather than two workflows. A folder per month for regression hunting Set the path from the Zapier submission date, so /Support/Bugs/2026-08 holds everything reported that month. When a deploy goes out mid-month and reports spike, the folder gives you the before and after without querying anything. ## If something isn't arriving The screenshot link opens for the reporter but not for the support team. The link points at the reporter's own drive with restricted sharing. Ask in the field's help text for a link anyone can open, and for evidence that matters point reporters at the File Upload question instead — an attached screenshot lands in the submission itself and never depends on someone else's sharing settings. Internal reports from your own staff are crowding out the customer ones. Add a Zapier filter on Email Address so anything from your own domain writes to /Support/Internal instead. Agents working customer issues then open a folder that holds only customer reports. ## Frequently asked questions Should reporters attach a screenshot or paste a link? Attach it, in most cases. A File Upload question takes the screenshot straight into the submission, up to 2 MB, which a cropped capture rarely exceeds. A link is the better answer for a screen recording, a full-resolution image or a whole folder of evidence, which is why the Bug Report Form keeps its Screenshot or Video Link question. The attached file stays in formformform for the team to open; the link is the part that travels into the OneDrive record. Does this replace our helpdesk? No, it sits beside it. The helpdesk owns the conversation and the status; the OneDrive folder holds a plain copy of the evidence that anyone can search without a seat on the ticket system. Most teams run both from the same submission. How quickly does the file appear after someone reports a bug? The submission reaches Zapier in real time, so the file usually lands within a minute. The exact delay depends on your Zapier plan and how busy the queue is, and extra steps placed before the OneDrive action push it out a little further. ## Related automations - [Create a project folder when a client signs on](https://www.formformform.com/automations/onedrive-client-workspace-folders) Each new engagement gets a named OneDrive folder, the standard subfolders, and the scope written in before the kickoff call. - [File every completed waiver in one audit folder](https://www.formformform.com/automations/onedrive-waiver-record-filing) Each completed waiver lands as a dated record in a restricted OneDrive folder, ready for the day someone asks for it. - [File every contest entry for the judging panel](https://www.formformform.com/automations/onedrive-contest-entry-records) Each entry becomes a file in its category folder in OneDrive, so the judging panel opens a sorted set rather than an inbox. - [Keep a text-file archive of every business inquiry](https://www.formformform.com/automations/onedrive-inquiry-text-archive) Every inquiry is written to a dated text file in OneDrive, giving you a searchable second copy of the response. - [Save every job application to a hiring folder](https://www.formformform.com/automations/onedrive-candidate-application-files) Every application becomes a candidate file in a shared OneDrive folder, named by role and ready for the hiring panel. - [Append every support request to a running log](https://www.formformform.com/automations/dropbox-support-request-log) Every help desk submission appends a line to one shared Dropbox text file, so the team reads the day's requests in order. - [All OneDrive integration details →](https://www.formformform.com/integrations/onedrive) - [Start from the Bug Report Form →](https://www.formformform.com/templates/bug-report-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=onedrive-bug-report-evidence-files)