topic Re: What will be the best integration solution in Workato Pros Discussion Board

What will be the best integration solution

CodersArcade — Tue, 11 Jun 2024 13:19:03 GMT

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

Re: What will be the best integration solution

bkramer — Wed, 12 Jun 2024 18:26:08 GMT

Just be aware of the limitations of lookup tables:

Has a maximum of 10 columns
Has a maximum of 100,000 entries
Individual columns have a character limit of 100,000 characters

Re: What will be the best integration solution

mppowe — Thu, 13 Jun 2024 13:31:17 GMT

@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.

Re: What will be the best integration solution

CodersArcade — Mon, 01 Jul 2024 13:34:59 GMT

How would a pub sub or topics help in the above said integration?

Re: What will be the best integration solution

mppowe — Mon, 01 Jul 2024 13:39:26 GMT

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.

Re: What will be the best integration solution

LcPaJMWV — Fri, 24 Oct 2025 19:04:43 GMT

@CodersArcade wrote:
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

Re: What will be the best integration solution

girish-naralla — Thu, 30 Oct 2025 10:29:30 GMT

In my opinion, Data Tables serve as a more robust and scalable alternative to Lookup Tables, especially for use cases involving larger datasets, complex filtering, or relational-like structures.

Below, I’ve outlined the key limitations of both Lookup Tables and Data Tables. Please review them to understand which option best suits your needs. If you need further assistance or a recommendation based on your specific use case, feel free to reach out.

Lookup Table Limitations

Max 100 tables per workspace
Max 10 columns per table
Max 100,000 rows per table (enforced from June 2025)
Limited filtering and sorting capabilities
Not suitable for relational data or storing large blobs

Data Table Limitations

Max 100 tables per workspace
Max 1,000,000 rows per table
Max 100 columns per table
Max 1 GB total table size
Advanced filtering, sorting, and linking capabilities

Re: What will be the best integration solution

mppowe — Thu, 30 Oct 2025 14:10:58 GMT

I agree that Data Tables are a better option now over Lookup Tables. At the time I wrote my original responses, Data Tables were tethered to Workflow Apps, thus an add-on to be bought. Within the last couple months I noticed Data Tables present and seemingly available to us, so I think there have been some licensing changes around that. So if they're available, then yes they can make more sense depending on the use case. Lookup tables are really meant more for quick translations of values rather than data storage

Re: What will be the best integration solution

kevinmiller2443 — Fri, 27 Feb 2026 10:58:54 GMT

The best integration solution really depends on where your data is coming from and how much control you need over the flow.

If your source is a WordPress site (especially Contact Form 7), the biggest issue is usually flexibility mapping fields correctly, handling custom properties, authentication headers, and making sure data reaches the CRM or automation tool without breaking.

In that case, instead of relying only on third-party connectors, a more stable approach is sending the form data directly to the destination API. For example, with Contact Form to Any API, you can push Contact Form 7 submissions straight to any REST API endpoint with custom payload formatting. That gives you full control over field structure and reduces dependency on multiple middleware layers.

From there, you can still use tools like Workato, Zapier, or native CRM workflows if needed but your data flow starts clean and structured.

In short, the best solution is the one that gives you flexibility, reliability, and control over how your data is transmitted.