Solved

Web Service return token

Forum|Forum|2 years ago
January 29, 2024
8 replies
0 views

Hello everyone!
I have to do a web service for the first time.
This web service will receive a response with a token that I must use in the next call to obtain the information I want.
Could someone guide me to do this? Do I need two web services; one to receive the touch and another once I already have the token to receive the response?

Best answer by harshitb6843

These should help -

https://docs.appian.com/suite/help/23.4/Call_Integration_Smart_Service.html

https://www.youtube.com/watch?v=l0bF0n-CCtk&ab_channel=AppianCommunity

harshitb6843

This looks like two sequential calls. You can just have two different integrations configured to do their respective works and then you can call the first one and use the response of it as input for the second one.

Are you facing any problems configuring it?

auroraj5980Author

Thank you very much, I don't really know how I could implement it. Would you be so kind as to tell me how to do it?

harshitb6843

Sure. Tell me where do you want to use it? In a process model or on an interface.

Here is a quick documentation on how you can call an integration - docs.appian.com/.../Call_an_Integration.html

mathieud0001

What kind of service are you trying to call? Normally, these steps can (and should be) taken care of by the Connected System. In this case, you'll likely be storing access tokens within the process itself which could be a security issue.

auroraj5980Author

I have to call a web service, collect the token it returns and integrate it into the next call that will return the information I need in my process. I'm considering using appian's "web API" for the calls. maybe you could do it with one connected system and two integrations?The problem is to collect that token and take it to the next integration

mathieud0001

Yeah, that is a common pattern. Auth token vs access token.

Would be 1 connected system that handles getting both and 1 integration. This way, your access token is not in plaintext in your process.

Sign up

Login with SSO

Login to the community

Login with SSO