This topic was automatically generated from Slack. You can find the original thread here.
Jobber connection isnt approved by Jobber and doesnt work. Any recommendation on how to get past this dillema?
Hey , thanks for raising this. I’ll check and get it approved if possible
thank you
any updates?
Hey , we’re working with Jobber team to get our app approved. Will get back to you as soon as we have updates
Thank you.
hello any luck with this?
Hey , thank you for checking in.
Jobber team requires restart the app review, so we just submitted again. Now waiting for Jobber team to review
Posted thread to Discourse: How to Resolve Unapproved Jobber Connection Issue?
Hi just checking to see if there are any updates here.
Hey , at the current state, Jobber team are testing our Pipedream - Jobber integration for the final approval. Hopefully they will get back to us soon
The current workaround is that you can create your own Jobber OAuth client on Pipedream
- The Pipedream OAuth popup will show you the redirect url
- Then you can take that redirect url to create a new OAuth client on Jobber developer site: https://developer.getjobber.com/
- Then you can add your Client ID and Client Secret to Pipedream OAuth popup
thanks i put the redirect url in the “call back url” part of the app in jobber dev portal. is that right?
That’s correct
when i go to connect, i get this. do you know what the issue could be is? i pasted in my client id and secret.
Hey , I checked and see that Pipedream received the error from Jobber: The provided client id and secret do not match an existing application
Could you make sure that you passed in your Jobber OAuth Client’s ID and Client Secret correctly to Pipedream?
I just want to double-check one thing about token persistence for production use. Since Pipedream is now handling the OAuth refresh flow automatically, am I correct that as long as I’m using the same connected account across all workflows, I’ll never have to manually reauthorize or refresh tokens again (unless Jobber invalidates them manually)?
I’m asking because I’ve built a full Supabase + dashboard system where multiple workflows read/write through the same connection — so I want to make sure the refresh cycle is handled globally across all workflows that share this OAuth client.
Appreciate the clarification — just making sure I’m setting this up the cleanest way long-term.
Hey ,
Since Pipedream is now handling the OAuth refresh flow automatically, am I correct that as long as I’m using the same connected account across all workflows, I’ll never have to manually reauthorize or refresh tokens again (unless Jobber invalidates them manually)?
This is correct. Pipedream automatically refresh the OAuth token for you in the background, for all of your connected account.
Posted thread to Discourse: How to Resolve Issue of Unapproved Jobber Connection?