Have you ever had that requirement where you know you can solve most of it with a workflow but the information you are after is one relationship too far away? For example:

I have a custom entity called Event Registration that is related to Contact but the discount information is placed on Account.

This article will explain how you can use an action as a placeholder for that information that is out of reach, and use it in your workflow either as a condition or to populate a field.