I have an application that has Quickbooks OAuth already implemented in it. It shows the user is connecting to my application which they trust and know.
If I switch to use Pipedream to use QuickBooks oAuth, I do not want it to say “PipeDream” to access you data. I still want it to show its connecting to my application.
How do I do this with Pipedream?
Thanks
Hi @matty69,
To customize the OAuth flow to display your application’s name instead of “Pipedream” when connecting to QuickBooks via OAuth, you would typically need to use your own OAuth application credentials. However, as per the provided Pipedream documentation, Pipedream operates its own OAuth application to mediate access to services like QuickBooks. This means that when users connect their account, they authorize the Pipedream application to access data in their account, and the OAuth flow is managed by Pipedream’s infrastructure.
Currently, Pipedream’s documentation does not explicitly mention the ability to customize the OAuth consent screen to display a different application name during the OAuth flow. This is likely because the OAuth consent screen is controlled by the OAuth provider (in this case, QuickBooks) and is based on the OAuth application registered with QuickBooks, which, in the context of Pipedream, is the Pipedream application.
If having your application’s name displayed during the OAuth flow is critical for your use case, you might consider the following options:
Direct Integration with QuickBooks: Continue using your own OAuth application credentials for QuickBooks. This approach requires managing the OAuth flow, storing refresh and access tokens, and making API requests directly from your application, bypassing Pipedream for the OAuth part.
Contact Pipedream Support: For specific use cases or advanced configurations, it’s a good idea to reach out to Pipedream’s support team. They might offer solutions or workarounds that are not documented publicly. You can contact them at Support - Pipedream.
Private Connected Accounts: Pipedream has introduced private connected accounts, which offer enhanced security and access management for Advanced and Business customers. While this feature focuses on access control within Pipedream, it’s worth exploring if it can be leveraged or if there are plans to support OAuth customization. More information can be found here: Private Connected Accounts.
In summary, using Pipedream’s QuickBooks integration will involve the OAuth flow indicating that the user is authorizing the Pipedream application. For customization of the OAuth consent screen, you might need to explore alternative approaches or contact Pipedream support for more guidance.
I’m a bot powered by Pipedream and GPT-4. I’m still learning, so please double-check my answers and code! Learn how to build your own.
@matty69 to confirm, are you trying to connect with your own account and use your own OAuth client within Pipedream, or did you want to interface with the Quickbooks API in Pipedream using the access token of your end users?