Native field service integration
Native Field Service Integration: How Formpiece Writes to Simpro, Fergus and AroFlo
What lands in each platform, what gets skipped, and where Formpiece stops.
Formpiece is integration software that sits between your inbox, your booking forms and your field service software. It reads supported emailed work orders into structured fields, then writes them to Simpro or Fergus through their APIs, and turns bookings and leads into AroFlo tasks or quotes.
This page is the blueprint: the payload each platform receives, the fields that don't travel, and what stays with your team.
The problem
Why Generic Automation Breaks on Field Service Payloads
Three platforms, three object models
Simpro has jobs and quotes, Fergus has jobs and enquiries, AroFlo has tasks and quotes. One generic connector can't map a work order onto all of them.
Fields with no home
A work order can carry a status, a salesperson or a custom field that one platform stores and another doesn't. Something has to decide what happens to it.
Real IDs, not pasted text
An API payload needs a matched site and customer, not an address typed into a notes field and left for someone to tidy up.
Duplicates the create call won't catch
A create request doesn't know the order is already in the system, so the check has to happen before anything is written.
Messy input at the front
Emails and PDFs arrive unstructured, so the payload is only as clean as the parsing that feeds it.
Formpiece handles the parsing, the matching and the platform-specific mapping, so what reaches the API is already tidy.
The blueprint
How the Payloads Map to Each Platform
One parsing engine at the front, a platform-specific writer at the back. Each import inbox writes to one platform, chosen when it is created. For an inbox in detail, see work order import.
Simpro: jobs or quotes
Creates the job or quote, the site and the site contact, applies your inbox defaults such as customer and job type, attaches the work order, and can look for an existing job by order number first.
Fergus: jobs or enquiries
Creates a Fergus job or enquiry against the matched customer and site, with the order number in the customer reference. Fields Fergus has nowhere to store are skipped and reported. Quotes are not supported.
AroFlo: tasks or quotes
Bookings and leads are converted into AroFlo tasks or quotes, with client, contact, location, schedule, custom fields, notes and documents written in order. AroFlo task conversion starts from a Formpiece form, not an emailed work order.
Every parser and inbox belongs to one platform, so a Simpro layout and a Fergus layout are set up separately.
Why native
What a Native Integration Gets You
Matched records, not pasted text
Sites, customers and contacts are matched to real records before anything is written.
The same mapping every time
Each field is filled by the same rule on every payload, so records from one sender look alike.
Repeats checked before the write
On Simpro, the optional order number check finds an existing job for that customer first. On Fergus the order number is kept in the customer reference.
Gaps reported, not hidden
A value a platform can't hold is skipped and reported, not forced into the wrong field.
The next step
After the Record Exists
Once a job exists in Simpro or Fergus, or a task in AroFlo, Formpiece can generate a private booking link for it. The tenant booking guide covers the calendar logic, and the complete work order to booking workflow joins both ends.
The record exists
A job in Simpro or Fergus, or a task in AroFlo.
A link is generated
The Geosearch plan covers link generation on all three platforms.
Delivery stays with you
Sent by your own messaging, or emailed from the dashboard by hand. Formpiece doesn't send SMS.
Questions About Native Integration
Straight answers. About what each platform receives.
Which field service platforms does Formpiece write to?
Simpro and Fergus, from emailed work orders, and AroFlo, from Formpiece booking and lead forms. Each import inbox writes to one platform, chosen when it is created. The booking forms use the calendars and customer records of the platform they sit on.
What does Formpiece send to Simpro for a work order?
A job or quote with the site and site contact, your inbox defaults such as customer and job type, the order number and description read from the work order, and the work order attached. If the order number check is on, it looks for an existing job for that customer before it writes.
How does the Fergus payload differ?
Fergus takes a smaller set of fields, so the job or enquiry carries the title, description, customer and site, with the order number in the customer reference. Anything Fergus has no field for is skipped and reported. Quotes are not supported.
Can emailed work orders become AroFlo tasks?
Not today. AroFlo task conversion starts from a Formpiece booking or lead form, which creates a task or quote with the client, contact, location and schedule. Emailed work order import runs on Simpro and Fergus.
How are repeat orders handled across platforms?
On Simpro, the optional order number check finds an existing job for the customer and you choose whether to leave it or update it. It needs an order number on the work order. On Fergus the order number is stored in the customer reference.
Which plan do the booking links need?
The Geosearch plan, on Simpro, Fergus and AroFlo. See Formpiece pricing, or request a personalised demo to see a link generated on a sample record.
What happens when a payload fails?
The people you list are emailed the order number and the errors. The inbox keeps the email and whatever was read from it, so the record or the parser can be fixed without asking the agency to re-send.
See the payloads on a sample record.
Request a personalised demo, or read how the same record carries on into a tenant booking.