Storing returned data from an api

Help
1

I’m using the HTTP Data Node to get a token from another cloudplatform.
The returned token is of course redacted in the debug console, but shouldn’t I be able to see it if I store it as a workflow storage?
Even if I can’t “see it”, shouldn’t I be able to use it within the same workflow run unredacted?
How does the debug console know what values to redact?

3

Hi @Lars_Andersson,

Are you having an issue storing a token in workflow storage? Are you hoping to actually see the raw value in workflow storage?

Thank you,
Heath

5

I was, but I figured out a way.

8

Reviving an old post…

I have this same issue but have not figured out a way yet. Have a two step process that includes a post request with some credentials in the body. That response will be an object that contains an accessToken. I then have to pass the accessToken into a second http POST request to perform the desired action. The response from the first request is REDACTED* and I cannot seem to pass the keys along even if I know what they should be.

Two things:

  1. Is there a way to view the redacted information to at least know that it is working?
  2. Even if I cannot see the data can it be passed to a second request?
    * I would like to save the data as well. Preferably as workflow storage but would be open to alternatives.

Regards,
Greg

9

@Greg_Bopp, here are the responses to your questions.

  1. If you would like to see the REDACTED information, use the Mutate Node to move the accessToken to another field on your payload that does not include the word token or password. For example, you can move accessToken to accessT and then you will be able to see it.
  2. Even if it is redacted, you can still use the payload path in subsequent nodes, which will use the correct value and not REDACTED. I have listed a couple ways to save the token so that it can be used in other workflows, if needed.
    • Workflow storage, as you mentioned, is a great place to save the token if you will be using it in other flows within the same workflow.
    • If you need the token in other flows outside your current workflow, then you can save it into a Data Table using the Table: Update Node (you can check a box to update the data table if the row does not exist) or save it as an Application Global (which requires using the Losant API Node with this action, Application → Globals).
2 Likes
10

Awesome information! Super speedy too. I’ve got it working. Thanks so much!