Forum Discussion
Yeah I built one. Mine is narrower than yours. It tracks service agreements and the visits that go against them. A few things that will bite you if Codex didn't handle them:
Refresh tokens rotate. Every time you refresh Jobber hands back a new refresh token and kills the old one. If you save the new access token but keep the old refresh token, everything works fine until the hour runs out and then the dashboard just goes dark with no obvious reason why. Save both every time.
If you set up webhooks you get about a second to acknowledge before Jobber counts it as a failure. Verify the HMAC, drop the payload on a queue, return 200. Do the real work after that.
And subscribe to APP_DISCONNECT early. If the connection ever gets revoked on Jobber's side, that webhook is the only way your side finds out.