Forum Discussion

roselvaggio's avatar
roselvaggio
Verified Community Coach
3 days ago

My newest Jobber “feature” is one I basically built myself (CEO DASHBOARD!)😂

I recently connected Jobber through a developer integration and used Codex to build a CEO dashboard for my company.

Instead of me digging through reports every day, it pulls the Jobber data I actually care about and gives me a daily snapshot of what’s happening in the business — things like client movement, revenue, scheduling/activity and the KPIs I want eyes on as the owner.

What I love about it is that Jobber is still the source of truth. I’ve just created another layer that turns all of that operational data into information I can digest quickly from a CEO perspective.

As we’ve grown, that’s become increasingly important to me. I don’t necessarily need more data — I need the right data surfaced quickly enough that I can recognize a trend and ask questions before it becomes a problem.

Curious if anyone else has built their own integrations or dashboards around Jobber?

1 Reply

  • jjd921's avatar
    jjd921
    Contributor 2
    3 days ago

    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.