We Use Cookies

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with this.

See our cookie policy.

Automation Action: OAuth SignIn

Obtain a authorization token from an OAuth endpoint for use on subsequent HTTP actions.

Built-In Action

Sign in to an OAuth endpoint to obtain an authorization token.

This action can be used to obtain an authorization token from an OAuth enabled web API. The token can then be used on subsequent HTTP GET or POST actions.

Select the Type. This can be one of the ThinkAutomation connected app types, or Generic.

Enter the Name. This is simply an identifier to show in your Automation actions list. Any text can be used.

Generic OAuth

For generic OAuth you must then supply the Authorization Endpoint, Token Endpoint, Client ID, Client Secret and Scope. These settings depend on the API you want to use. Consult the API documentation for the service you want to use to obtain the correct values.

The Additional Options tab provides some additional options that your OAuth provider may require.

Some OAuth providers can provide additional parameters in the redirect request that is sent back to ThinkAutomation. One such case is for QuickBooks, which returns a realmId parameter. For these cases you can specify parameter names in the Extract Custom Redirect URL Parameters grid. In the Assign To column specify the ThinkAutomation variable to receive each parameter value. You can then use this value on subsequent actions.

Click the Sign In button to begin the sign in process. A browser session will be started to complete the sign in.

Select a variable to receive the authorization token from the Assign Authorization To list.

On any subsequent HTTP GET, HTTP POST or Read JSON Document actions you can then set the Authentication method to OAuth and then Auth Token to the variable value selected above.

ThinkAutomation will automatically refresh the authorization token when it expires.

As with all other Action settings, the Client ID and Client Secret are stored securely in the ThinkAutomation metadata database.