What is the Correct OAuth Redirect URL to Use for CloudConvert Setup in Pipedream?

This topic was automatically generated from Slack. You can find the original thread here.

Hey - I am currently integrating CloudConvert into my Pipedream workflow to automate file conversions and need to set up OAuth for authentication. I’ve managed to create the OAuth client on CloudConvert, but I am unsure of the correct OAuth redirect URL to use for completing the setup in Pipedream. Little help?

For integrating CloudConvert with Pipedream using OAuth, you’ll need to specify a redirect URL in your CloudConvert OAuth client setup that matches the one provided by Pipedream. This URL is used to handle the OAuth authorization response. When you connect a new CloudConvert account in Pipedream, you should be prompted to authorize the Pipedream application to access your CloudConvert account. During this process, Pipedream handles the OAuth flow and will provide the specific redirect URL to use. Typically, this URL is part of the OAuth setup instructions when you add the CloudConvert app within Pipedream’s UI. However, if you’re looking for a general approach or the exact URL ahead of time, Pipedream’s OAuth redirect URLs usually follow a standard format and are intended to receive the code from the OAuth provider after a user authorizes the connection. While I can’t provide the exact URL without access to live data or the ability to browse external content, you can usually find this URL in the Pipedream UI during the setup process for connecting a new account. If you’re still unsure or if the setup process doesn’t make this clear, I recommend reaching out to Pipedream’s support for specific guidance on the CloudConvert OAuth setup, including the redirect URL. You can contact them directly for assistance with workflow-specific issues or integration setup at Support - Pipedream.

Hi , is there a specific reason that you’re setting up your own Cloud Convert app? We have the Cloud Convert app available on Pipedream with our own client, so you can authenticate via OAuth and use our prebuilt triggers and actions as well.

It was just an experiment I was playing with. Thanks :slight_smile: