Who's integrated FieldPulse with their CRM? How's it going?

Hey Brianna — we did the HubSpot integration about 6 months ago. YMMV but here's what worked for us:

• What syncs: Contacts, companies, and deals → customers and work orders in FieldPulse. We set it up so that when a deal hits "Closed Won" in HubSpot, it auto-creates the work order.
• Heads up: Custom fields don't map cleanly. We had to do some Zapier gymnastics to get our "Job Type" field from HubSpot into FieldPulse.
• The gotcha: Bidirectional sync is limited. Changes in FieldPulse don't flow back to HubSpot automatically, so our sales team still has to manually update deal status when jobs complete. Worth noting if your sales team lives in HubSpot.

Overall? Took about 2 weeks to get right, but saved us probably 5-10 hours a week of manual data entry. Happy to share more details if helpful.

We tried the Salesforce integration and abandoned it after 3 weeks. The sync was creating duplicate contact records every time a customer called from a different number, and our sales ops team couldn't keep up with the cleanup. We needed this working reliably and it wasn't.

Ended up building a simple API integration ourselves that only pushes work order status back to Salesforce — one-way, much cleaner. My team can't move forward on anything that requires constant manual intervention.

Can you share the endpoint you're hitting for work order status? Running into similar dedupe issues with the native sync.

GET /api/v2/work_orders?status=completed&updated_since=2025-07-29

Payload structure would help too.

Thanks so much Devon!!! This is exactly the kind of detail I needed. The custom fields thing is definitely a concern for us — we have a lot of specific job type codes that need to carry over. When you say "Zapier gymnastics," did you end up building a multi-step zap or was there a simpler workaround? Also curious if you've looked at the newer native integration at all — HubSpot was supposedly on their roadmap last I checked.

Not willing to share our full implementation, but the key was matching on external ID before creating records. The native integration doesn't do this aggressively enough.

Multi-step zap — HubSpot deal updated → filter for Closed Won → format job type via lookup table → create FieldPulse work order. The lookup table was the key, otherwise we were getting inconsistent values.

Haven't tried the native integration yet, though I saw the partnership announcement. Might be worth waiting if you're not in a rush. The Zapier approach is stable but definitely feels like a bridge solution.

We're in a similar spot Brianna! Our team is actually using Pipedrive (I know, not HubSpot or Salesforce) and we've been experimenting with the webhook → Zapier → FieldPulse flow. It's working okay but we keep having timing issues where the work order gets created before the customer record fully syncs, so the job ends up with missing contact info. Really appreciate you starting this thread — has anyone found a reliable way to sequence the data flow so customer records are definitely there before work orders get created? Thanks so much for any insights!!!

Yeah this one tripped me up too when I first looked at it. The webhook fires immediately on deal close, but the FieldPulse API returns 404 if the customer lookup fails.

What I ended up doing — add a 30-second delay step in Zapier (yeah I know, feels hacky), then retry the customer lookup before creating the work order. Not elegant but it works. Code version would be cleaner with exponential backoff, but if you're no-code, the delay is your friend.

There's also a lesser-known endpoint that can create both in one call:

POST /api/v2/work_orders
{
  "customer": {
    "external_id": "pipedrive_12345",
    "create_if_missing": true
  },
  ...
}

Documented but easy to miss — lets you upsert the customer inline rather than doing it as two separate calls.

Integrated with Salesforce two years ago. Still haven't gotten our sales team to actually use the data that flows back... so we've got this beautiful automated sync that nobody looks at. Worth thinking about whether your sales team actually wants field data in their CRM before you build the pipeline.

Ray makes a crucial point here — the technical integration is maybe 30% of the work. The other 70% is change management and getting people to actually use the connected data.

Another way to think about it: start by asking your sales team what field data would actually change how they work. If the answer is "nothing really," then you're solving a problem that doesn't exist. We've had much better success with a manual weekly export that goes to a shared dashboard — way less friction, and the sales team actually engages with it because it's built around what they care about.

Pro tip: Run a 2-week pilot with 2-3 salespeople before committing to full automation. You'll learn more in those two weeks than in any planning meeting.