• State Verified Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 2 views
  • Users 0 members are here
Options
Related

Connect FieldPulse to system not on integrations list

Mike Dolan

We're using some proprietary logistics software that FieldPulse obviously doesn't integrate with. Need to push work order data from FieldPulse into it when jobs complete.

Looked at Zapier but the logistics system isn't on there either. Do I need to build something custom? If so, what's the path — webhooks from FieldPulse into some middleware?

Not looking for a tutorial. Just need to know if this is feasible and roughly how much dev time I'm looking at.

Parents
  • 0

    Hey Mike — yeah this is a common pattern. The work_order.status_changed event includes the full work order object, which has customer location, assigned tech, custom fields, etc. You shouldn't need a follow-up API call just to get location data.

    Quick example of what hits your endpoint:

    {
  "event": "work_order.status_changed",
  "data": {
    "id": "wo_abc123",
    "status": "Completed",
    "customer": {
      "name": "Acme Corp",
      "address": {
        "street": "123 Industrial Way",
        "city": "Austin",
        "state": "TX"
      }
    },
    "assignee": { "id": "usr_456", "name": "Sarah Chen" },
    "completed_at": "2025-07-12T14:30:00Z"
  }
}

    Full reference: Setting Up Webhooks and webhook payload structure thread.

    One heads up: if your logistics system requires auth tokens that expire, you'll need to handle refresh in your middleware. FieldPulse webhooks don't support OAuth client credentials flow natively — the webhook just fires to your URL with a signature header for verification.

    Feel free to drop your use case in the reply if you want me to flag any other gotchas.

Reply
  • 0

    Hey Mike — yeah this is a common pattern. The work_order.status_changed event includes the full work order object, which has customer location, assigned tech, custom fields, etc. You shouldn't need a follow-up API call just to get location data.

    Quick example of what hits your endpoint:

    {
  "event": "work_order.status_changed",
  "data": {
    "id": "wo_abc123",
    "status": "Completed",
    "customer": {
      "name": "Acme Corp",
      "address": {
        "street": "123 Industrial Way",
        "city": "Austin",
        "state": "TX"
      }
    },
    "assignee": { "id": "usr_456", "name": "Sarah Chen" },
    "completed_at": "2025-07-12T14:30:00Z"
  }
}

    Full reference: Setting Up Webhooks and webhook payload structure thread.

    One heads up: if your logistics system requires auth tokens that expire, you'll need to handle refresh in your middleware. FieldPulse webhooks don't support OAuth client credentials flow natively — the webhook just fires to your URL with a signature header for verification.

    Feel free to drop your use case in the reply if you want me to flag any other gotchas.

Children
No Data