Win it in Pipedrive. Deliver it in Fieldproxy. See it back on the deal.
Keep Pipedrive for selling and connect it to a field service system for the work after the sale. In Fieldproxy, a deal that moves to Won (or a stage you choose) creates a job or project with the organisation, contact, address, deal value and deal products as line items. Organisations and people stay matched in both systems. As the job is scheduled, started and completed, those steps are written back to the deal as activities or notes, so sales sees the install happen without asking.
Fieldproxy is AI-native field service software set up around each company's workflow: scheduling, the Android and iOS technician app, your own forms and checklists, quotes, invoices and payments. Set up for you, live within a day, with unlimited users on one price per company.
See your Pipedrive deals turn into jobs
Tell us which pipelines lead to field work. We set it up on your own stages and fields before you commit.
Why teams connect them
Pipedrive is great until the deal is won. Then it goes quiet.
Pipedrive is built around the deal: stages, activities, follow-ups. Once a deal is Won, the work moves to the field, and Pipedrive has no technician app, no schedule board, no checklist, no stock and no invoice. So the scope is copied into a calendar or a WhatsApp message, the site address is retyped, and the salesperson has no idea whether the install went ahead.
Connecting Pipedrive to a field service system closes that gap: the won deal becomes the job, with its products and contacts, and the deal hears back as the work moves.
What syncs
What moves between Pipedrive and Fieldproxy, and when
A typical setup. You choose the pipelines and stages that start work, and every field, including your custom fields, is mapped at setup.
| Object | Direction | When it moves |
|---|---|---|
| Won deals | Pipedrive โ Fieldproxy | When a deal moves to Won (or the stage you pick), a job or project is created with the organisation, contact, address and deal value. |
| Organisations and people | Both ways | Customer and contact details stay matched, so the field team and sales see the same phone number and address. Matching is by name and email before anything new is created. |
| Deal products | Pipedrive โ Fieldproxy | Products on the deal become the job's line items, so the quote sales agreed is what the technician sees and what gets invoiced. |
| Custom fields | Pipedrive โ Fieldproxy | Mapped to job fields at setup, for example site access notes or preferred install week. |
| Job progress | Fieldproxy โ Pipedrive | Job scheduled, started and completed are written back to the deal as activities or notes. |
| Field quotes and follow-up work | Set up per account | Whether an extra quote approved on site creates or updates a deal is set up per account. |
The connection uses an API token or OAuth from a Pipedrive admin account, with Pipedrive webhooks so a won deal reaches Fieldproxy without anyone pressing sync.
See your own Pipedrive pipeline mapped to jobs before you commit.
Get DemoThe workflow
From won deal to completed job, invoice and books
For installs, one-off jobs and new maintenance contracts.
- 1
Optional: a site survey first
Deal at a survey stage
A survey job can be created at an earlier stage. The technician measures and photographs on a form that can calculate a price, and the result goes back to the deal before it is won. - 2
The deal is won
Salesperson, in Pipedrive
The deal moves to Won. Organisation, contact, address, value and products are already on it. - 3
The job is created with the deal's scope
Fieldproxy
Deal products become line items and drive the checklist for the job type. One deal creates one job, or a project with stages for bigger work. - 4
It is scheduled
Office, with the Dispatch agent
The Dispatch agent suggests who should go by skills, distance, free time and van stock. The office confirms, and the customer gets the booking. - 5
The work is done on the phone
Technician or subcontractor
GPS check-in, your checklist with required photos, parts used, extra work quoted on site, and the customer's signature. Works offline. - 6
The deal hears about it
Fieldproxy to Pipedrive
Scheduled, started and completed are written to the deal as activities or notes. - 7
Invoice and books
Fieldproxy to accounting
The invoice is built from what was done, paid by payment link or Tap to Pay, and synced to QuickBooks, Xero or Sage.
What stays where
What stays in Pipedrive, and what moves to Fieldproxy
Pipedrive owns the sale; Fieldproxy owns the work. The field tools you use today (a calendar, a forms app, an invoicing tool) are replaced, not joined on top with more zaps.
Stays in Pipedrive
- Leads, deals, pipelines and stages
- Sales activities, emails and follow-ups
- Forecasting and sales reporting
- Your web forms and lead sources
Moves to Fieldproxy
- Scheduling and dispatch, including subcontractors
- The technician app: checklists, photos, signatures, offline, GPS check-in
- Survey and inspection forms, including ones that calculate a price
- Quotes changed on site, invoices, payment links and Tap to Pay
- Service agreements and recurring visits after the install
- Sites, assets with QR codes, warehouse and van stock, purchase orders
- A customer portal for quotes, jobs and invoices
Worked example
A solar install, from won deal to handover
A residential solar installer runs sales in Pipedrive with two pipelines: Residential installs and Battery retrofits.
Demo data. The company, people and numbers are made up.
- Survey: A deal for the Harlow family reaches the Survey booked stage. Fieldproxy creates a survey job; surveyor Ana Duarte photographs the roof and switchboard on the survey form, and the result goes back to the deal.
- Won: Salesperson Josh Pryor moves the deal to Won. The deal has twelve panels, an inverter and a battery as products.
- Project: Fieldproxy creates a project with two stages (install, then commissioning). The products become line items and the install checklist.
- Stock: The panels and inverter are checked against warehouse stock, and a purchase order is raised for the battery, which is not in stock.
- Install: The crew checks in by GPS, completes the checklist with required photos of the array and the isolator, and the Harlows sign on the phone.
- On the deal: Josh sees Install scheduled, Install started and Install completed as activities on the deal, without asking the office.
- Invoice: The final invoice is sent with a payment link, the Harlows pay, and the invoice and payment sync to QuickBooks Online.
Josh never retyped the scope, and the crew never arrived without the battery.
See it built around how your team already works.
Get DemoSetup
Connected and live within a day
A Pipedrive admin is needed for a few minutes. The rest is done by Fieldproxy's team.
- 1
A short call
Which pipelines lead to field work, which stage starts it, which fields matter, and what sales wants to see back on the deal. - 2
Connect Pipedrive
An admin connects the account with an API token or OAuth. We pick the pipelines and stages that create work. - 3
Map fields and job types
Pipedrive fields, including custom fields, are mapped to the job. Each pipeline can map to its own job type and checklist. - 4
Build the field side
Forms, checklists, price list, quote and invoice templates, stock and your accounting sync. Customers and sites come across with free, assisted migration. - 5
Test, then go live
Win a test deal, complete the job on the phone, check what lands on the deal and in your books. Then switch off the old tools.
Fit
Who it's for, and when it isn't the right fit
A good fit if
- Pipedrive is where you sell, and won deals turn into installs or visits
- Your team or subcontractors need checklists, photos and signatures on site
- Deals carry products that should become the job's scope and invoice
- You want sales to see delivery progress on the deal
- You invoice through QuickBooks, Xero or Sage
Probably not the right fit if
- Your won deals are delivered remotely, with no one going to site
- You only need a shared calendar for a few visits a month
- You want Pipedrive to remain the only system your field team touches
- You want an add-on that sits on top of a field app you are keeping: Fieldproxy replaces it
The usual ways to run field work with Pipedrive, by kind of tool.
| Approach | Fits when | What you give up |
|---|---|---|
| Pipedrive alone: activities as visits | A few visits, no on-site paperwork | No technician app, no checklists, no stock, no invoicing in the field. |
| Pipedrive plus a calendar, a forms app and an invoicing tool joined with Zapier | The tools are already paid for and volume is low | Several logins and zaps that break quietly; one job lives in four places. |
| A field service system that replaces your field tools, synced both ways (Fieldproxy) | Won deals become real field work with forms, stock and invoices | A second system for the field team. Set the switch-off date for the old tools. |
Straight answers
Pipedrive and field service: questions we get asked
Does Fieldproxy integrate with Pipedrive?
Which Pipedrive stage creates the job?
Will re-winning a deal create a duplicate job?
Does it create duplicate customers?
Do Pipedrive custom fields come across?
What does sales see in Pipedrive after the deal is won?
Where do invoices go?
Can my technicians quote extra work on site?
Can I book jobs from ChatGPT or Claude?
How long does it take to set up?
Related
Where to go from here
Fieldproxy MCP server
Book jobs, quote and invoice from Claude, ChatGPT or Copilot, with a confirm step.
Keep Pipedrive. Give the won deal somewhere to go.
Tell us which pipelines lead to field work. We show it running on your own stages and fields.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.