Append every support request to a running log
Every help desk submission appends a line to one shared Dropbox text file, so the team reads the day's requests in order.
New submission on your IT help desk form
Append the request details to a text file in Dropbox
One-directional. A submission triggers the action — nothing is written back into your form.
Two people covering support do not need a ticketing tool; they need to see what came in and who picked it up. One text file, appended to on every submission, is enough — it opens on any device, it sorts by time, and nobody has to be given a seat.
Internal IT teams and small studios run this. When the volume outgrows it, the log is the evidence for what a proper help desk would have to handle, with the issue types and priorities already counted for you.
Setting it up
- 1
Publish the IT Help Desk Ticket template and put its link where people already ask for help: the intranet page, the channel topic, a QR code by the printer.
- 2
Create the Zap with formformform as the trigger app, choose New Submission, and select the help desk form.
- 3
Add Dropbox as the action app and choose Create or Append to Text File rather than Create Text File, so every submission adds to the same file.
- 4
Set the path to a shared file such as /Support/intake-log.txt and confirm everyone on the rota can open it.
- 5
Compose the appended line as one row — date, priority, issue type, requester, subject — in the same order every time, separated by a character you can split on later.
- 6
Keep the long description off that line and add it on a second indented line, so the log stays scannable and the detail is still there.
- 7
Start a new file each month by putting the month in the path, so no single file grows to the point where it opens slowly.
- 8
Submit two test tickets in a row and check both lines landed in one file rather than two, then turn the Zap on.
What maps where
Using the IT Help Desk Ticket as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Dropbox |
|---|---|
| Priority | Second column of the appended line, so urgent rows are easy to scan |
| Issue Type | Third column of the appended line |
| Full Name | Requester column of the line |
| Ticket Subject | Summary column at the end of the line |
| Issue Description | Indented second line beneath the entry |
| Affected Device or System | End of the indented detail line |
Variations worth knowing
Add a Zapier filter on Priority so the highest level appends to /Support/urgent.txt as well as the main log. Whoever is on call opens one short file at the start of a shift instead of scanning everything that arrived overnight.
Put Department in the path — /Support/2026-Q3/Finance.txt — and the volume per team counts itself. It is the cheapest evidence available when someone asks which department generates the most work for two people and a shared inbox.
If something isn't arriving
The Create Text File action always writes a new file. Switch the step to Create or Append to Text File, and check the path resolves to exactly the same name on every run, since a date in the file name starts a fresh file each day.
Simultaneous appends to the same Dropbox file can collide. Put a short Zapier delay step before the Dropbox action to space them out, then replay the missing task from your Zap history to recover the lost line.
Frequently asked questions
Can we mark a request as done in the log?
Only by editing the file in Dropbox yourself. Nothing writes back to formformform, so the log records what arrived rather than acting as a status board. Most teams add a done marker at the start of the line by hand.
How big can the log file get before it becomes a problem?
Plain text stays small — a line per ticket is bytes, not megabytes — though editors do slow down on very long files. Rolling to a new file each month, as in the setup above, keeps every file quick to open and search.
Do the requests still appear in formformform?
Yes. Every submission stays in your responses view where you can filter, search and export it, and the Dropbox log is a second copy for the people who never open the form builder. The two do not need to be kept in step.
Related automations
- Collect vendor artwork details into the event folder
Vendor registrations write a per-vendor record into the event's Dropbox folder, with booth details and a link to their artwork.
- Create a project folder when a new client onboards
A completed onboarding form creates a Dropbox folder named for the client and project, ready before the first call.
- File every property disclosure as a written record
Each completed property disclosure writes a dated text record into the Dropbox folder for that address.
- Keep a text-file archive of every contact submission
Each contact form response becomes a timestamped text file in Dropbox, giving you a plain-text backup you can search and keep.
- Save every job application as a candidate file
Every careers form submission writes a candidate file into a shared Dropbox Applicants folder, named for the role and the applicant.
- Archive every submission as a dated text file
Each submission becomes a dated text file in one shared Drive folder, readable by anyone with access to it.
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