Skip to main content
Inspiring
July 27, 2021
Solved

Call a Connected System in a Process Model

  • July 27, 2021
  • 6 replies
  • 8 views

I have a connected system that needs to be manually clicked in order for it to get a token. Once you press the "Authorize" button, it somehow saves the token in Appian and then you can call an integration. Can that same functionality be replicated in a Process Model? What needs to happen for the integration to get that token in the PM? Or is there a way to get the token in a PM?

Best answer by selvakumark
I still have to press the Authorize button

For a connected system that uses the OAuth 2.0 Authorization code, user interaction is absolutely necessary. We cannot bypass it & that's where I recommended using the authorization link component to make the user authorize. 

The OAuth lesson in this academy course explains all bout it - academy.appian.com/

My other suggestion to use the Client Credential grant method is more of a kind of system-to-system communication that requires no user interaction. We just have to create a connected system of this type and use it inside an integration. Then we can call the integration at the required places - Appian will automatically generate tokens for the API calls.

6 replies

stefanhelzle0001
Brainy
July 27, 2021

That is not possible. At least not easily or out-of-the-box. This type of authentication requires the user to interact.

alexl0007Author
Inspiring
July 27, 2021

So the Connected System has to be always "Authorized" manually? Is this correct?

selvakumark
Participating Frequently
July 28, 2021

[mention:9a006fe643d44a4eab55186016d77c1f:e9ed411860ed4f2ba0265705b8793d05]

As Stefan said, it needs user interaction to get a token. You can create a user input task in the process model where the individual user can authorize their session and generate a token, Below links might be useful:

docs.appian.com/.../authorization_link_component.html
docs.appian.com/.../setting_up_an_oauth_connected_system.html

On the other hand, if you don't want the user interaction, then you can try changing the connected system to work based on OAuth 2.0: Client Credentials Grant.