Do you use lookups in your recipes like I do? Do you struggle to find what the values actually are? You know, opening lookup tables in a new tab, finding the right one, finding the right row, forgetting why you went there... 🤯 So I had Claude build me a little Chrome extension for it. Click the icon next to a lookup and it shows the current value, plus a “Last run” tab with what it actually was in the latest job. It’s very rough, and honestly it’d be nice if this was a feature in Workato itself. 👀 Anyone else solved this some other way, or have I just been suffering alone?
I’m intrigued, I haven't used this command before. always used the lookup table job as a step and called it out as a data pull that way. Will have to take note of this and see what i can do with it. Also if you haven't already, make the switch to Data Tables. The 10 column limit is a killer in lookup tables.
Give it a try, I think one pro vs. using a separate step to get the value is optimizing task usage. Good tip, we're using data tables as well! 🙌
Mario I. Great solution from a debugging perspective. However, I do have some security concerns regarding the approach outlined below. Where the risk is:
Data exposure. “Last run” shows real job data, which at some organization can include sensitive or customer information, or confidential business data. The extension would be reading that into the page, so you need to know where it goes.
Permissions and network calls. A Chrome extension on the Workato domain can read the page, and potentially session tokens and API calls, with your access. If it sends anything to an outside server, including an AI API, that is a data leak. Check this first.
What are your thoughts on this?
