You have no favorites... yet!
Use the Library tree on the left to select a Choreo to call from your gateway device.
Use the Library tree on the left to select a Choreo to call from your edge device via the gateway.
Library . Microsoft . OAuth . InitializeOAuth
Generates an authorization URL that an application can use to complete the first step in the OAuth process.
/*
TembooTask class placeholder
*/
/*
TembooTask header placeholder
*/
Since you've changed your device configuration, you'll need to tell us about this new device.
This feature is in experimental mode - pricing coming soon.
Send your code straight to a GitHub repository.
Your code will be visible by others in your repos. Keep credentials private by saving a Profile or commit code with Placeholder inputs.
The following files will be added to this repo:
You'll be able to edit and share your code from TI's CCS Cloud IDE.
The following will be sent to CCS Cloud:
/*
Your auto-generated code will appear here once you've configured your device above.
*/
/*
A header file containing your Temboo account information will appear here once you've
configured your device above.
*/
/*
Please log in to generate proxy server code for use with the JavaScript SDK.
*/
This Choreo generates an authorization URL that an application can use to complete the first step in the OAuth process. A unique and private callback URL for your account is registered with Temboo so that when you redirect your user to the AuthorizationURL returned by the Choreo, the authorization code generated by Google is stored temporarily for easy retrieval in the finalization step of the OAuth process. You can complete the OAuth process by passing the CallbackID (returned by this Choreo), to the FinalizeOAuth Choreo.
In some cases, you may want to design your application such that you don't have to wait for this Choreo to return the CallbackID. If you find yourself in this situation, you can specify a CustomCallbackID, and then your code can move onto something else. Once you've detected that your user has clicked "allow", you can pass your CustomCallbackID to the FinalizeOAuth Choreo in order to complete the process. Just remember that a CustomCallbackID should be unique. Concatenating a serial timestamp and a randomized string would be a reasonable CustomCallbackID for example.
Here's an example list of acceptable inputs:
ClientID = {YOUR MICROSOFT AZURE CLIENT ID}
ForwardingURL = http://example.com
Resource: https://analysis.windows.net/powerbi/api
Note: the Resource input is used to specify which Microsoft API your application needs to access. To access Power BI, you should specify the following Resource:
https://analysis.windows.net/powerbi/api
When going through the OAuth process for Excel Choreos, you don't need to specify a Resource. Instead, specify the desired Scope e.g.:
Files.ReadWrite
You can find a list of Microsoft Graph permission scopes here.
https://ACCOUNT_NAME.temboolive.com/callback/google
© 2025 Temboo, Inc Privacy Terms