Description

This activity performs an OAuth 2.0 authorization. Returns an access token to use in other activities.

Parameters

Authorization URL

Set a value - allows you to manually specify the Authorization URL.

Calculate a value - allows you to use a special formula or a special method to determine the Authorization URL.

Save the previous step result - takes the result of the previous workflow action as the Authorization URL.

Access Token URL

Set a value - allows you to manually specify the Access Token URL.

Calculate a value - allows you to use a special formula or a special method to determine the Access Token URL.

Save the previous step result - takes the result of the previous workflow action as the Access Token URL.

Client ID

Set a value - allows you to manually specify the Client ID.

Calculate a value - allows you to use a special formula or a special method to determine the Client ID.

Save the previous step result - takes the result of the previous workflow action as the Client ID.

Client Secret

Set a value - allows you to manually specify the Client Secret.

Calculate a value - allows you to use a special formula or a special method to determine the Client Secret.

Save the previous step result - takes the result of the previous workflow action as the Client Secret.

Scope

Set a value - allows you to manually specify the Scope.

Calculate a value - allows you to use a special formula or a special method to determine the Scope.

Save the previous step result - takes the result of the previous workflow action as the Scope.

State

Set a value - allows you to manually specify the State.

Calculate a value - allows you to use a special formula or a special method to determine the State.

Save the previous step result - takes the result of the previous workflow action as the State.

Usage

OAuth 2.0 protocol requires human in the loop by design. User has to enter his credentials in the pop-up and allow robot to use the service.

Most of the services has quite long token lifetime: more than 14 days. So it'll be wise decision to keep the token and ask for user's attention only when required.

On screenshot below you can see the example of the workflow that will ask user for authorization only if old token is not valid anymore: