Capabilities
Capabilities | Supported |
Connector Capabilities | |
Read | Yes |
Backfill | No |
Bidirectional Capabilities | |
Incident Create | No |
Incident Update | No |
Narrative Update | No |
Customers of this CAD may be able to use bidirectional capabilities through IntelliComm. See Bidirectional CAD Integrations.
Overview
This integration uses email. ProPhoenix does not use the GovWorx Data Agent. A ProPhoenix report sends a CSV file to a GovWorx email address for your agency.
See the general information in CAD Data Ingestion via Email.
How It Works
GovWorx provides a department-specific email address.
Your ProPhoenix administrator schedules the report to send to that address with the CSV file attached.
GovWorx reads the CSV file, finds the incidents in it, and creates or updates each incident.
Report Layouts
GovWorx reads three ProPhoenix report layouts. GovWorx picks the layout from the column headers in the first row.
Law: the default layout.
Fire/EMS: the headers include CADNo2.
Fire RMS: the headers include rptdttm2.
An incident takes several rows in the file. GovWorx groups the rows into one incident by the CAD number. In the Law layout, keep the CAD number in the first column of the first row for each incident. Rows below it that have no CAD number belong to that incident.
Attachments
GovWorx reads the first attachment. GovWorx reads a later attachment only when the first one is not a ProPhoenix report.
When more than one later attachment qualifies, GovWorx cannot choose one. Send one report in each email.
The file must be UTF-8 CSV. A byte order mark at the start of the file is fine.
Date Formats
Law and Fire RMS: month/day/two-digit year hour:minute, for example 02/02/26 05:27. Unit action times can include seconds.
Fire/EMS: month/day/year hour:minute, for example 2/2/2026 5:27. The year can have two or four digits.
Call Taker
ProPhoenix reports have no call taker column. GovWorx uses the earliest note author.
Law: When no note has an author, GovWorx uses the person on the Dispatched row. For an officer-initiated incident with no dispatch, GovWorx uses the PFCode of the first officer-initiated or traffic stop row.
Fire/EMS: GovWorx uses the earliest note author as the call taker ID.
Fire RMS: When no note has an author, GovWorx uses calltaker2.
GovWorx reads a person as either ID - Name or Name - ID.
Standard Data Fields
These are the standard data fields GovWorx reads from ProPhoenix reports. The tables below show each GovWorx field and the report column it comes from, for each layout. Column names are from the first row of the CSV file. A blank cell means that layout does not provide the field.
Note: Additional fields are considered enhancement requests.
Incident fields
GovWorx field | Law report | Fire/EMS report | Fire RMS report |
Incident ID |
|
|
|
Incident Number |
|
|
|
Incident Type |
|
|
|
Incident Date |
|
|
|
Closed At |
|
| |
Priority |
|
| |
Disposition |
|
| |
Location |
|
|
|
Agency |
| ||
Call Source |
| ||
Caller Name |
|
|
|
Caller Number |
|
|
|
Dispatch Queue At |
| ||
Call Taker ID and Name | See the Call Taker section above | Author of the earliest note | See the Call Taker section above |
Notes
GovWorx field | Law report | Fire/EMS report | Fire RMS report |
Note Text |
|
|
|
Note By |
|
|
|
Note Time |
|
|
|
Responders and units
GovWorx field | Law report | Fire/EMS report | Fire RMS report |
Unit Name |
|
|
|
Personnel ID |
|
| |
Dispatched By |
|
| |
Dispatched At |
|
|
|
Enroute At |
|
|
|
Arrived At |
|
|
|
Cleared At |
|
|
|
Need Help?
If you need assistance, contact the GovWorx Technical Services team or email [email protected].