Forum Discussion
Spot on about the missing 'updated' triggers in Jobber's native Zapier integration, Randy. It’s exactly why we started building a direct API-to-API stability layer. Adhesion Connect is doing great work with webhooks, but we’re taking a slightly different path by focusing on 'hardcoded' fixes for the QB tax rounding and the field note transfer lag. Would love to hear your thoughts on why Jobber still hasn't addressed the record update latency in their core API.
- Randy_Warner4 days agoContributor 4
Hey winnovations! Can you clarify what you're referring to when you mention 'record update latency'? Happy to lend a guess however the best resource to provide details would be Jobber directly of course.
- winnovations3 days agoContributor 3
Hey Randy, good catch. Basically when a job status changes in Jobber — like from Complete to Invoiced — the webhook fires but the actual Visit object takes 15-30 seconds to catch up if you query the API. So you're building automations thinking the data is live, but you're always running behind. We hit this constantly when syncing to Google Calendar or pulling real-time reports. Built a workaround for it but yeah, it's the kind of thing Jobber should just fix in their core API.
You running into the same thing
- Randy_Warner8 hours agoContributor 4
For something like this winnovations I wouldn't suggest 'polling' for the data but rather 'listening' for the updates via webhook either through a direct integration via a custom app (which it sounds like you might have) or through another service like Zapier or Adhesion Connect. It doesn't sound like your use case requires an immediate need for that information if the end result is a Google Calendar update however let me know if I'm missing something here.