In practice, this means that you should use return values to provide additional context to your organization's transaction history. For example, if you write an action to refund a user, you might include the refund amount and the ID of the refunded user as values in the object that you return.
An action may return a primitive value like number, boolean, string, nullish values like
None, date or datetime objects, or objects or dictionaries with string keys and values of any of the previous types. Any nested keys will be stringified and flattened.
Return values are not encrypted at rest in our database, so we recommend against returning sensitive information from actions.