Custom action output variables show up empty

[Brian Hofmeiste]

I have a custom action that runs a rest script. Part of the script retrieves a response body on execution.  That response body shows up correctly if I place it inside gs.info but if I assign it to an output variable the variable is always empty.  Anyone experience this? I’ve tried casting the response body to string.  I’ve tried parsing it.  No matter what I do - the output variable is always empty.  

[Mike Rakvica1 · Accepted solution]

You should be using the name of the output variable.

Still curious why not use the OOB rest steps & JSON Parser as well and potentially even the Okta spoke since it seems like you're doing an Okta integration?

[Brian Hofmeiste]

I don’t know about rest steps.  I will give that a look! And the Okta spoke doesn’t work for companies using delegation of authority for user provisioning. You have to send additional fields in the rest body that are not part of the spoke 😞 

[Mike Rakvica1]

If the spoke itself doesn't have exactly what you need, you can still clone the action in the same scope as the spoke, and update the body/fields/variables etc to what you need! But it still gives you a good baseline of how to use/build Integration Hub actions for flow designer.

[Brian Hofmeiste]

This is great advice - I hadn't thought of this. Thanks Mike!