Forum Discussion

roselvaggio's avatar
roselvaggio
Verified Community Coach
29 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?

9 Replies

  • jjd921's avatar
    jjd921
    Contributor 3

    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.

    • roselvaggio's avatar
      roselvaggio
      Verified Community Coach

      Thank you! I’ve noticed I’ve ran out of tokens during the build multiple times!

  • WiringByron's avatar
    WiringByron
    Verified Community Coach

    I built one, and I made it look like the Matrix.

    • roselvaggio's avatar
      roselvaggio
      Verified Community Coach

      Oh I love this!! Ours is just branded with our colors 🤣

    • WiringByron's avatar
      WiringByron
      Verified Community Coach

      Anthony, for myself, I actually just used Base44 to build the dashboard. I told it what I wanted, and then I integrated it with the Jobber API.

  • Dina_PJC's avatar
    Dina_PJC
    Contributor 3

    Thank you for sharing these dashboards! I have been thinking about building one for myself. Has anyone done this with Claude? Would love examples and any tips on how to get started.

    • WiringByron's avatar
      WiringByron
      Verified Community Coach

      You could totally do this with Claude.

      Go make yourself a Jobber developer account. 

      Once you're inside there, make yourself up an app.


      Down at the bottom of that app, you'll see (I believe) it is a secret key or a client ID key. Tell Claude you want to connect your app that you made to the Jobber API. It's going to ask you for this information from your app. You're going to tell Claude that information, and it should connect.




    • jjd921's avatar
      jjd921
      Contributor 3

      Wiring's steps are the right start. One thing I would change is the secret. Don't paste your client secret into the chat. Put it in a file on your computer that the code reads, and tell Claude the file name instead. Chat history is the last place you want a key sitting. After that, pick the five numbers you check most before you build anything, because a dashboard that shows everything gets ignored. Jobber also limits how much data you can pull in one go, so save the results and refresh them every few minutes instead of calling Jobber on every page load. Which numbers do you want to see each morning?