Automate Incident Report Routing with Zapier
What This Builds
When a guard submits a digital incident report, Zapier automatically sends an email notification to the right supervisor — with the incident type, location, and time in the subject line. No manual forwarding. No missed reports. No 2 AM calls to figure out where a report went.
Prerequisites
- Zapier account (free tier at zapier.com)
- Digital incident report system: Google Forms (free) or GoCanvas (paid — use what your employer has)
- Email access for supervisor notifications
- Permission from your supervisor to set this up for your site
- Account needed: Free Zapier account (100 tasks/month free); GoCanvas if that's your system
The Concept
Zapier is a connection tool — it watches for something to happen in one app (a new form submission) and automatically does something in another app (sends an email). You don't write code. You just tell Zapier "When this happens, do that."
Think of it like a relay race: the guard crosses the finish line (submits a report), and Zapier automatically passes the baton to the supervisor (sends the email) — without anyone having to make a phone call or check a inbox.
Build It Step by Step
Part 1: Set up your digital incident form
If you don't already have a digital incident form, set up Google Forms — it's free and connects to Zapier easily.
To create a Google Form:
- Go to forms.google.com
- Click "+" to create a new form
- Title it: "Incident Report — [Site Name]"
- Add these fields:
- Guard Name (short answer)
- Date and Time of Incident (date/time)
- Location / Post (dropdown: create options for each area of your site)
- Incident Type (dropdown: Suspicious Person, Theft/Shoplifting, Vehicle Incident, Medical, Access Control, Other)
- Incident Description (paragraph — long text)
- Immediate Action Taken (paragraph)
- Status (dropdown: Resolved, Pending Follow-up, Police Contacted)
- Click Share → copy the link and share it with your guards
Guards submit this form from their phone browser — no app required.
What you should see: A shareable form link that guards can open and submit from their phones.
Part 2: Create a Zapier account
Go to zapier.com and sign up for a free account. The free tier allows 100 "tasks" per month — each form submission that triggers an email counts as one task. For most security teams, the free tier is sufficient.
What you should see: The Zapier dashboard with your "Zaps" (automations) listed (empty at first).
Part 3: Create the Zap — Trigger
- Click "Create Zap" (or "+ New Zap")
- In the Trigger step, search for and select "Google Forms" (or your form tool)
- For the event, select "New Response in Spreadsheet"
- Connect your Google account when prompted — Zapier needs permission to read your form responses
- Select your incident report form from the dropdown
- Click "Test trigger" — Zapier will pull in the most recent form submission to confirm the connection works
What you should see: A test submission from your form appears in Zapier with all the field values populated.
Troubleshooting: If no submissions appear, submit a test form entry first, then try the trigger test again.
Part 4: Create the Zap — Action (Send Email)
- Click "+" to add an action step
- Search for and select "Gmail" (or "Email by Zapier" for a simpler option that doesn't require linking an account)
- For the event, select "Send Email"
- Connect your Gmail account when prompted
Now configure the email:
To: [supervisor's email address] — you can also add multiple recipients separated by commas
Subject: Use the "Insert Data" button to pull in form fields:
[Incident Type] at [Location] — [Date and Time] — [Guard Name]
Example result: "Suspicious Person at North Parking — 3/19/2026 11:47 PM — Officer Johnson"
Body: Build the email body using form fields:
Incident Report Submitted
Guard: [Guard Name]
Date/Time: [Date and Time of Incident]
Location: [Location / Post]
Type: [Incident Type]
Status: [Status]
Description:
[Incident Description]
Immediate Action Taken:
[Immediate Action Taken]
---
This is an automated notification from the incident reporting system.
- Click "Test action" — Zapier will send a test email using the sample form data to verify it works
What you should see: A test email in your supervisor's inbox with all the incident details populated.
Part 5: Turn on the Zap and test live
- Click "Publish" or toggle the Zap to "On"
- Submit a test form entry as a guard would
- Confirm the email arrives in the supervisor's inbox within 1–2 minutes
- Adjust the email format or recipients if needed
What you should see: The Zap is active. Every new incident report submission triggers an automatic email notification.
Real Example: Office Building Security Team
Setup: A site supervisor sets up Google Forms for incident reporting across 4 guard posts. Zapier connects form submissions to two email recipients: the supervisor and the property manager (for incidents rated "Police Contacted" or above).
Input (guard on post): Guard submits form from phone: Incident Type = "Medical Emergency," Location = "3rd Floor Lobby," Time = 2:14 AM, Status = "Police Contacted," Description = [details].
Output (automatic): Within 60 seconds, supervisor receives email: "Medical Emergency at 3rd Floor Lobby — 3/19/2026 2:14 AM — Officer Martinez" — with the full incident details in the body. No phone call required. Full documentation trail created automatically.
Time saved: Supervisor is notified instantly, even at 2 AM, without the guard having to call — and there's an automatic written record that the report was filed and notification was sent.
What to Do When It Breaks
Email not arriving → Check Zapier's task history — go to your Zap's settings and look at "Task History." If the task failed, the error message will tell you why (usually a permission issue with Gmail).
Form fields not appearing in the email → Make sure your Google Form is connected to a Google Spreadsheet (in Google Forms → Responses → click the spreadsheet icon). Zapier reads from the spreadsheet, not the form directly.
Email is going to spam → Have your supervisor whitelist the sending email address or mark the first notification as "Not spam."
Hit the 100-task limit on free tier → Either upgrade Zapier ($20/mo for 750 tasks) or consider whether all incidents need email notification vs. just "Police Contacted" or "Pending Follow-up" status ones.
Variations
- Simpler version: Skip Zapier entirely — have guards email their incident report to the supervisor directly using the Voice-to-Report Pipeline (Level 3 guide). Less automated but zero setup cost.
- Extended version: Add a second Zap that posts a Slack or Teams notification (useful if your team uses a group chat instead of email). Add conditional routing — "Police Contacted" incidents go to a different, higher-priority recipient list.
What to Do Next
- This week: Set up the form and Zapier connection; test with 3 live submissions
- This month: Track whether supervisors are getting notifications faster and whether follow-up on open incidents improves
- Advanced: Add a Zapier step that logs each incident to a Google Sheet for the trend analysis workflow (see Level 4 guide: "Incident Pattern Analysis")
Advanced guide for security guard supervisors. Zapier free tier supports 100 tasks/month. Paid plans start at $20/month. Google Forms is free. GoCanvas requires an employer subscription.