Flowvio's inbound ProNett integration turns accepted orders into scheduled pest control jobs. Each order is matched to an existing Flowvio site, uses the reporting template chosen for that connection, and can be assigned to the site's default technician.
Why connect them?
ProNett can send the work. Flowvio makes it ready to complete.
The integration removes the gap between an order arriving and a technician being able to act on it. Flowvio keeps the useful order context attached to the job while giving your team the templates, field capture and reporting tools they use every day.
Separate brand connections
Keep each ProNett brand or account traceable with its own status, default template, mappings and delivery history.
Explicit site matching
Link the ProNett site number to the correct existing Flowvio customer site before an order can become a job.
Field-ready job details
Use the due date as the schedule, the problem or equipment type as the title, and preserve key order context in the job notes.
Optional default technician
Assign new ProNett work to the Flowvio site's default active technician without changing jobs that already exist.
How it works
Four steps from connection to completion
- Connect each brand or account. Give the connection a clear name, choose the active Flowvio job template every accepted order should use, and keep processing active or paused.
- Map your existing customer sites. Match each ProNett site number to the correct Flowvio site. The number is also searchable in the Flowvio site directory.
- Receive a scheduled Flowvio job. When a valid order arrives for an active mapped site, Flowvio creates one job with a snapshot of the selected template and blank answers ready for the visit.
- Complete the visit in Flowvio. The technician captures the work through the normal field workflow, then continues into Flowvio's existing report review and PDF process.
Controlled setup
Choose the workflow before the first order arrives
Each connection has a clear identity, a default template and an active or paused state. That keeps work from different ProNett brands traceable and gives every new job the right starting structure.
- One connection for each ProNett brand or account
- Only active Flowvio templates can be selected for new jobs
- Processing can be paused without deleting the connection or its history
Built for real operations
When an order cannot become a job, it does not disappear
Safe duplicates
Repeated order numbers with the same normalised content are recorded as duplicates instead of creating another field job.
Actionable errors
Missing site mappings, inactive sites, invalid dates and other processing issues are surfaced for an administrator to resolve.
Auditable recovery
Admins can acknowledge issues and reprocess a delivery after correcting its site mapping or default template.
Useful delivery history
See received batches, per-order outcomes, linked Flowvio jobs and the latest vendor status without losing the original delivery record.
A clear boundary
What this integration does — and what it does not
It does
Receive ProNett orders, map them to existing sites, create scheduled Flowvio jobs, preserve selected order context and track delivery outcomes.
It does not
Send job or report updates back to ProNett, create customer sites automatically, or map the ProNett engineer directly to a Flowvio technician.
Important: this is an inbound integration, not a two-way sync. Changed ProNett order payloads update the integration record and retain the linked Flowvio job; they do not rewrite a job already in progress.
FAQ
ProNett integration questions
Keep exploring