FieldproxyIntegration guide · ZapierZapier for the tools without a native integration
Use Zapier for the tools Fieldproxy doesn't connect to directly. Five Fieldproxy events can start a Zap: new job, job status changed, job completed, new customer and new invoice. And a Zap can create or update jobs, customers and notes in Fieldproxy from any app Zapier connects to. You add a Fieldproxy API key to Zapier once and build the Zap yourself, with no code. Zapier is best for small one-way links; for two-way or high-volume syncs, use a native integration or Fieldproxy's open API and webhooks.
Fieldproxy is AI-native field service software, set up around your workflow and live within a day. It replaces your field service tool; Zapier connects it to the long tail of apps around it. One price per company, unlimited users.
See Fieldproxy connected to your tools
Tell us which tools you need to connect. We show which are native, which suit Zapier, and which need the API.
What syncs
Five triggers out. Three actions in.
Built on the Fieldproxy REST API, signed in with a Fieldproxy API key. A trigger starts a Zap when something happens in Fieldproxy; an action is something a Zap does in Fieldproxy.
| Object | Direction | When |
|---|---|---|
| New job | Fieldproxy → Zapier (trigger) | When a job is created in Fieldproxy. |
| Job status changed | Fieldproxy → Zapier (trigger) | When a job moves to another of your stages, such as scheduled or on site. |
| Job completed | Fieldproxy → Zapier (trigger) | When a job is marked complete. |
| New customer | Fieldproxy → Zapier (trigger) | When a customer is added in Fieldproxy. |
| New invoice | Fieldproxy → Zapier (trigger) | When an invoice is created in Fieldproxy. |
| Jobs | Zapier → Fieldproxy (action) | A Zap creates a job, or updates an existing one, from another app's data. |
| Customers | Zapier → Fieldproxy (action) | A Zap creates or updates a customer. |
| Notes | Zapier → Fieldproxy (action) | A Zap adds a note to a record, for example a message from another tool. |
Each Zap is one-way: a trigger on one side, actions on the other. Two Zaps pointing at each other are not a two-way sync, and can loop or overwrite each other.
The workflow
Zapier for anything without a native integration, step by step
How a team usually goes from a gap between two tools to a running Zap.
- 1
Check for a native integration first
You, with the Fieldproxy team
Accounting, payments, CRM, helpdesk, ERP, calendars, Slack, monday.com and Podium are native. See the integrations page. Native syncs are two-way where it matters and are set up with you. - 2
Pick the trigger
In Zapier
A Fieldproxy event (new job, status changed, job completed, new customer, new invoice), or an event in another app that should create or update something in Fieldproxy. - 3
Connect with your API key
Admin, once
Create a Fieldproxy API key and add it to Zapier. Every Zap after that uses the same connection. - 4
Map the fields
In Zapier
Choose which fields from the trigger go where: a form's address into the job's site, a spreadsheet's phone number into the customer, a message into a note. - 5
Add filters and steps
In Zapier
Use Zapier's own filters so the Zap only runs when it should, for example only for one job type or one region. - 6
Test with a sample job
You
Run a test job through and check both sides before turning the Zap on. - 7
Watch it, and move it if it grows
You
If the link becomes two-way or high-volume, move it to the open API and webhooks, or ask about a native integration.
Tell us your tools. We show which ones are native and which suit Zapier.
Get DemoWhat stays where
Zapier holds the link. Fieldproxy holds the records.
A Zap moves data between apps; it doesn't keep any. The jobs, customers and invoices stay in Fieldproxy, and the other app keeps its own data.
| Stays in Zapier | Lives in Fieldproxy |
|---|---|
| The Zap: its trigger, filters, steps and the other app | The job, customer and invoice records the Zap reads or writes |
| Zapier's task history and error emails | The Fieldproxy API key and what it is allowed to touch |
| Your Zapier plan and task count, billed by Zapier | Native two-way syncs for accounting, payments, CRM, helpdesk, ERP and calendars |
| One-way links to niche tools | Scheduling, dispatch, the technician app and your own stages and forms |
Two things follow from that split. First, if a Zap stops (an expired login on the other app, a renamed field, a plan limit), Zapier is where you see it, in its task history, and the Fieldproxy records are simply not created or updated until it is fixed. Someone on your team should own the Zaps for that reason. Second, the Fieldproxy API key is the only thing Zapier holds on the Fieldproxy side. Fieldproxy's API keys are scoped, so a key made for Zapier can be limited to what the Zaps need and revoked without touching anything else.
Zapier or something else
Four ways to connect Fieldproxy, and when each fits
| Route | Fits when | What to know |
|---|---|---|
| Native integration | Accounting (QuickBooks, Xero, Sage), Stripe, CRMs, helpdesks, ERPs, calendars, Slack, monday.com and Podium | Set up and maintained with you. Two-way where it matters, with one owner per field. |
| Zapier | A small, one-way link to a tool with no native integration | You build it and own it. Simple, but each Zap is a separate thing to watch. |
| Open API and webhooks | Two-way or high-volume syncs, or anything Zapier can't express | Scoped API keys, inbound webhooks to start automations, and signed outbound webhooks. Needs a developer. |
| MCP server | Asking for or changing data in plain English from Claude, ChatGPT or Copilot | Anything you can do in the app, with a preview and confirm step. Not a background sync. |
Don't Zap your accounting
Invoices and payments need a two-way sync with one owner per field. Use the native QuickBooks, Xero or Sage sync.
Do Zap the long tail
A marketing list, a niche form tool, a spreadsheet a partner shares: small, one-way links nobody would build a native integration for.
Use the API when it matters
When a link carries a lot of records, or both sides edit the same data, a developer on the open API and webhooks gives you control Zapier can't.
Worked example
Three Zaps at a demo pest control company
Demo data with fictional names. Greenleaf Pest Control uses Fieldproxy for jobs and invoicing, QuickBooks for the books (native sync), and three smaller tools nobody wants to retype into.
- Zap 1, a web form to a job: a homeowner, Carla Mendes, fills in the inspection request form on Greenleaf's website. The Zap creates a customer and a job in Fieldproxy with her address and the pest she described.
- Zap 2, job completed to a mailing list: when the job is completed, a Zap adds Carla to Greenleaf's seasonal reminder list in their email marketing tool.
- Zap 3, new invoice to a sheet: owner Rob Kerr keeps a simple sheet of invoices by suburb. A Zap adds a row each time a new invoice is created.
- Not a Zap: the invoice itself reaches QuickBooks through the native two-way sync, and the payment Carla makes by payment link comes back the same way.
- Not a Zap either: when Rob wants to know which completed jobs from last week have no invoice, he asks Claude, connected through Fieldproxy's MCP server.
Setup
Your first Zap, in four steps
The Fieldproxy side of Zapier is one API key. The native integrations around it are set up with you as part of going live within a day.
- 1
Create a Fieldproxy API key
From your Fieldproxy account, for the Zapier connection. - 2
Add it to Zapier
Connect Fieldproxy in Zapier with the key. You do this once. - 3
Build the Zap
Pick a Fieldproxy trigger or action, connect the other app and map the fields. - 4
Test with a sample job
Check both sides, then turn the Zap on. Existing data comes into Fieldproxy with free, assisted migration, not through Zaps.
Fit
Who this is for, and when it isn't the right fit
A good fit when
- You use a tool Fieldproxy has no native integration with.
- The link is one-way and the volume is modest: a form, a list, a sheet.
- Someone on the team is comfortable building and watching Zaps.
Not the right fit when
- Both systems edit the same records. Use a native integration or the API.
- The link carries accounting data. Use the native QuickBooks, Xero or Sage sync.
- You want to keep another field service system and Zap it to Fieldproxy. 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
Zapier and field service: questions we get asked
Which Fieldproxy triggers are available in Zapier?
What can a Zap do in Fieldproxy?
How do I connect Fieldproxy to Zapier?
When should I not use Zapier?
How fast does a Zap run after a Fieldproxy event?
Can I use Zapier to post Fieldproxy jobs to Slack?
Does Fieldproxy charge for Zapier?
Is there an alternative to Zapier for developers?
Can AI do the same job as a Zap?
Will you help us build the Zaps?
Related
Every other way to connect Fieldproxy
Native connections are on the integrations page. For developers, see the API and webhook docs; for AI assistants, see Fieldproxy's MCP server.
Native where it matters. Zapier for the rest.
Tell us which tools you run. We show you which connect natively and which suit a Zap.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.