What needs improvement with Tray.io?

To improve Tray.io, I wish that there was an easier way to download the information of our workflows to have it in some form of an Excel file that explains our workflows that we built, because we have been trying to find a way to document them to evaluate them, and we are basically having to use Miro to recreate the workflows there. It would be helpful to have a way for those who do not have access to Tray.io to look and see what it was doing and review whether or not we need to make some tweaks. Additionally, errors occur regularly when we have too large a number of employees that come over; for example, at the end of the year when our school staff is off for the summer, they technically go as inactive employees, and processing a large number of them bogs up the Tray.io system and leads to errors. We then have to go into all the Tray.io workflows to find out which piece broke and how to minimize it, so those limitations on how much data we can push overnight are frustrating. I would appreciate better documentation; I feel that the academy or training I took when I started with the company through Tray.io was adequate and gave us the basics, but I have not really had much experience finding support documents to help when we have problems. Although digging through the logs that Tray.io provides does help, I wish there were more in-depth help to get our systems to work easier. We kind of just bandage it together to keep it working, but it is not something that makes me say I am so glad we have Tray.io. I landed on that rating because we feel that it is mediocre; it does what we need it to do more often than not, but it does not impress us as it is not always reliable and hands-off. We do have to touch it quite often to make sure it keeps working, and I would love for it to be more powerful, particularly as we grow as a company, which is frustrating. Therefore, it is not something I would recommend to others as a great tool unless you are only moving small pieces of data. Before we wrap up, I think my additional thoughts about Tray.io mostly repeat the same points I have made previously: it is a strong workflow automation tool that works well with some of our APIs, but I just have not seen it grow and change. This could be due to the fact that we are just not using it to its greatest ability. I think that pricing-wise it is fair; I would love to see a software system be beneficial and worth the money. Right now its flexibility is beneficial since it replaced one of our other systems, so it is better than what it used to be. The complex setup of its conditions can be difficult, but the drag-and-drop feature helps. However, I think it is hard for non-technical people to learn the software, and that is the biggest challenge; you really need to know what you are doing. If you are not using it regularly, it can be difficult to come back because there is not a lot of documentation. Additionally, there is not a clear way to provide individualized documentation. The limitations on data transfer volumes at particular times are also frustrating, and without an easy debugging process, it is hard to address issues. Finding the balance between the needs of a small company and supporting larger data transfers is crucial for setting appropriate expectations regarding what the software system can do.

Tray.io is definitely a highly powerful tool, but there are three main areas that I feel could be improved. There is a steep learning curve in user accessibility; the builder is highly developer-centric, making it difficult for a non-technical team member to modify or troubleshoot workflows. Introducing a more intuitive visual interface similar to what we have in make.com right now would make the platform much more collaborative and easier to work with for any non-technical folks or newly onboarded engineers, allowing them to be briefed faster. Visual debugging is another area where troubleshooting complex nested loops can feel very abstract. Having clearer, more visual step-by-step data tracking during test runs would speed up the development and testing process. The pricing model is geared heavily towards enterprise budgets; offering more flexible mid-market pricing tiers would make it more accessible for a growing organization that wants a small start and scale up gradually. The core platform security is highly robust and easily meets our requirements for SOC 2 and GDPR compliance. However, when utilizing their AI features such as Merlin AI with sensitive student data, we maintain a very cautious approach. While Tray.io provides enterprise-grade governance guardrails and data masking capabilities, our internal compliance policies prevent us from passing any personally identifiable student information directly through AI-driven processors. We trust Tray.io's underlying infrastructure security, but we believe organizations must still enforce strict data filtering protocols on their end to ensure student privacy is maintained. During our evaluation, we tested the AI capabilities in a sandbox environment, primarily using it to generate workflow drafts and natural language prompts from web data schemas. Strength-wise, it is highly capable when it comes to translating simple text descriptions into functional workflow templates. It serves as a great accelerator, helping to map standard files quickly and reducing the initial setup time for basic integrations. For issues, in the case of highly custom APIs or deeply nested data structures, accuracy declines. We noticed occasional misinterpretation of complex schemas, meaning our developers still had to manually review and correct the outputs. It is a highly helpful productivity booster but still requires human oversight for enterprise-grade reliability.

There is not much that can be improved in Tray.io. It is a good tool, but debug can be improved further and the solutions can be improved further.

I believe Tray.io can be improved by offering integration with Tableau, which is still not available. I rated it an eight because there are still some things that can be improved, as I mentioned before.

It was not always easy to test our changes in Tray.io. In a software engineering context, you might imagine there being different branches and different environments to make changes where you can make changes and test them, but in Tray.io it does not quite work the same way. I understand there have been improvements in this regard.