โ06-11-2024 06:19 AM
Our goal is to establish Integration A, which serves as a data repository. The data stored in Integration A is then utilized in another recipe, Integration B, to ascertain the appropriate endpoint for data transmission. What is the most effective method to accomplish this within Workato? The current proposal involves storing data in a lookup table. Are there any superior alternatives or recommendations
Solved! Go to Solution.
โ07-01-2024 06:39 AM
Because it doesn't share the same limit as a Lookup table. While the Lookup table maxes out at 10,000 records, aI'm not aware of a limit to the number of messages stored in a Pub/Sub Topic. It's essentially a message queue so it's designed to hold many messages to be consumed.
โ06-12-2024 11:26 AM
Just be aware of the limitations of lookup tables:
โ06-13-2024 06:31 AM
@bkramer makes a good point about Lookup tables. If you need more scalability, some other options could be publishing the data as Topics to a Pub/Sub integration pattern (which Workato has natively). You could also create a CSV to store in Workato FileStorage that Integration B reads (perhaps the file path is stored in your lookup table). There's also Workato Table Storage though I haven't looked at that yet, and I want to say it might be connected to Workflow Apps.
โ07-01-2024 06:34 AM
How would a pub sub or topics help in the above said integration?
โ07-01-2024 06:39 AM
Because it doesn't share the same limit as a Lookup table. While the Lookup table maxes out at 10,000 records, aI'm not aware of a limit to the number of messages stored in a Pub/Sub Topic. It's essentially a message queue so it's designed to hold many messages to be consumed.