monday.com for the project, Fieldproxy for the site visit, and the board kept up to date
Keep monday.com as the board your office plans projects on, and let Fieldproxy run the part monday.com wasn't built for: the site visit. When an item is added to a board you choose, or reaches a status such as Ready to schedule, Fieldproxy creates a job from it. The job is scheduled, dispatched and completed in Fieldproxy, and its status, assigned technician, scheduled date, notes and photo links are written back to the item. The board stays the office's live view; the field work happens in Fieldproxy.
Fieldproxy is AI-native field service software, set up around your workflow and live within a day. It replaces the field side you run today from board comments, phone calls and a shared spreadsheet; it is not a layer on top of another field service tool. One price per company, unlimited users.
See your monday.com board turn into jobs
Show us the board you plan from. We set it up on your own columns and job types before you commit.
What syncs
Items come in. Progress goes back.
Built on the monday.com GraphQL API and webhooks. The board decides when work is ready for the field; Fieldproxy decides who goes and when, and reports back to the same item.
| Object | Direction | When |
|---|---|---|
| Board items | monday.com โ Fieldproxy | A new item on a chosen board, or an item reaching a status you pick (for example Ready to schedule), creates a job with the mapped columns. |
| Status column | Fieldproxy โ monday.com | Job status (scheduled, on site, complete) updates the item's status column. |
| Assigned technician and dates | Fieldproxy โ monday.com | The scheduled date and technician fill the item's date and people columns. |
| Updates | Fieldproxy โ monday.com | Job notes and photo links are posted as item updates. |
| Edits made to the item after the job exists | Set up per account | Which column changes, if any, are read back onto an existing job is agreed at setup. |
| Subitems and several boards | Set up per account | Whether subitems become their own jobs, and which boards map to which job types, is agreed at setup. |
monday.com limits API complexity per minute, so bulk updates are spread out. The column mapping is agreed with you at setup.
The rule behind the table is one owner per field. The board owns the plan: the scope, the customer's details as sales captured them, and when the work is ready. Fieldproxy owns the visit: the date, the technician, the status on site and what was found. Because each column is written by one side only, the board and the job never fight over the same value, and a project manager can trust that the date on the item is the date the crew is booked.
The workflow
monday boards for project tracking, step by step
How a typical installation or project job runs with the connection in place. The trigger status and column mapping are agreed with you.
- 1
The project is planned on the board
Project manager, in monday.com
The item carries the customer, the site address, the scope and whatever columns your team uses. Nothing changes about how the office plans. - 2
The item reaches Ready to schedule
monday.com, read by Fieldproxy
When the item reaches the status you picked (or is added to a chosen board), Fieldproxy creates a job from it, with the mapped columns on the job. - 3
The visit is scheduled and dispatched
Dispatcher, helped by the Dispatch agent
The Dispatch agent suggests the crew by skills, location and free time. The dispatcher approves, and every change can be undone. - 4
The board shows who and when
Fieldproxy, written to monday.com
The scheduled date and technician fill the item's date and people columns, and the status column moves to scheduled. The project manager sees it without asking. - 5
The crew does the work in the app
Technician, Android or iOS
GPS check-in, the checklist for the job type, before and after photos, parts used and the customer's signature. The app works offline. - 6
Progress lands on the item
Fieldproxy, written to monday.com
The status column moves to on site and then complete, and the technician's notes and photo links post as item updates. Your monday.com automations on that status fire as usual. - 7
The job is invoiced from Fieldproxy
Office
The completed job becomes an invoice with a payment link, and syncs two-way with QuickBooks, Xero or Sage.
See your own monday.com board items become jobs.
Get DemoWhat stays where
monday.com for the plan. Fieldproxy for the visit.
monday.com is good at tracking work across a team. It wasn't built to decide which technician goes, carry a checklist to a phone without signal, count the parts on a van or produce an invoice.
| Stays in monday.com | Lives in Fieldproxy |
|---|---|
| Project plans, timelines and phases | Each site visit: schedule, technician, checklist, photos, signature |
| The board the office and project managers look at | The dispatch board and each technician's day |
| Sales handover, approvals and internal tasks | Customers, sites, assets and service history |
| monday.com's own automations and dashboards | Stock and parts, quotes, invoices and payments |
| Collaboration between office teams | The technician app: offline, GPS check-in, 27 languages |
Why not run the field from the board?
Teams that do end up with technicians updating items from a car park, photos in a chat group and no proof of when anyone arrived.
What the visit needs
Your own stages, forms and checklists, scheduling and dispatch with approval and undo, and a customer portal for the client.
Multi-visit projects
A project with several visits is tracked in Fieldproxy's projects, while the board keeps the project-level view.
Worked example
Solar installs at a demo installer
Demo data with fictional names. Sunvale Energy sells and installs rooftop solar. Sales and project management run on a monday.com board called Installs; the install crews run on the Fieldproxy app.
- Monday: project manager Leah Brooks moves the item โOkafor residence, 8 panelsโ to Ready to schedule after the permit comes through.
- Monday, shortly after: a job is created in Fieldproxy with the address, panel count and scope from the item's columns.
- Tuesday: the dispatcher books crew lead Marco Silva for Thursday. The item's date column shows Thursday, the people column shows Marco, and the status reads Scheduled.
- Thursday 08:40: Marco checks in by GPS; the item's status changes to On site.
- Thursday 15:10: Marco completes the install checklist with roof, inverter and meter photos and the customer's signature. The status reads Complete, and his notes and photo links appear as an item update.
- Thursday, straight after: Sunvale's own monday.com automation on Complete moves the item to the Commissioning group and notifies Leah.
- Friday: the office invoices the job from Fieldproxy with a payment link.
Setup
Connected and live within a day
A monday.com admin approves access. The Fieldproxy team does the mapping with you.
- 1
A short call about the board
Which board, which status means ready for the field, which columns matter, and what the project manager wants to see coming back. - 2
Connect monday.com
With OAuth or a personal API token from a monday.com admin. - 3
Choose the board and the trigger
A new item on a chosen board, or an item reaching a status you pick. - 4
Map columns and statuses
Board columns to Fieldproxy job fields, and Fieldproxy statuses to the labels on your status column. - 5
Test, then go live
Move a few real items to the trigger status, run the jobs on a phone, and check the board. Existing customers and sites come across with free, assisted migration.
Fit
Who this is for, and when it isn't the right fit
A good fit when
- Projects are sold and planned in monday.com, and the site work is done by your own crews or subcontractors.
- Project managers chase the field by phone to update the board.
- Site visits need checklists, photos, signatures and proof of arrival that a board item can't hold.
- You invoice from the completed work and want it in QuickBooks, Xero or Sage.
Not the right fit when
- Your field work is a handful of visits a month by office staff. A monday.com board may be enough.
- You want monday.com to stay the place technicians work. Fieldproxy runs the visit in its own app.
- You want to keep another field service system and add monday.com to it. Fieldproxy replaces the field service tool rather than sitting on top of one.
See it built around how your team already works.
Get DemoStraight answers
monday.com and field service: questions we get asked
Can a monday.com item create a field service job automatically?
What gets written back to the monday.com board?
Is the sync two-way?
Can monday.com automations react to the field?
Do technicians need a monday.com seat?
What about large boards or bulk updates?
Can different boards create different kinds of jobs?
Can I see monday.com and field data together with AI?
Can subcontractors do the site work?
How long does setup take?
Related
More on projects, dispatch and the rest of the stack
See every connection on the integrations page, or work with your field data from Claude, ChatGPT or Copilot through Fieldproxy's MCP server.
Keep the board. Give the site visit a proper home.
Show us the monday.com board you plan from. We show its items becoming jobs on your own setup.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.