Tray.io Reviews

We used and evaluated Tray.io for approximately three to six months during a proof of concept evaluation phase. During this period, our engineering and operation teams utilized the platform to build high-volume data integration pipelines, specifically syncing student enrollment data between our student information system and the LMS system that we have. While we ultimately decided to consolidate our day-to-day automation needs on Make due to its lower barrier to entry and visual ease for non-developers, our time with Tray.io gave us a solid understanding of its enterprise-grade capabilities and structure.

Our primary use case during our evaluation of Tray.io was automated student roster management and enrollment synchronization. Specifically, we needed to ensure that when a student registers for a course on our platform, their profile gets updated, and course access to the particular subject is also done across our internal database as well as our LMS systems. A specific example would be that we set up a workflow which would handle batch updates between our core student database that was running on Supabase in Postgres and our LMS system, which was using a version of Canvas during that time. The workflow operated as follows: when a dual trigger is queried, our database is queried at a specific time at night, maybe around 12:00 a.m. or 1:00 a.m., to fetch all the new student registrations and course changes that were done in the last 24 hours. Then, Tray.io received the data as a nested JSON payload. Using the Tray loop helper, the workflow iterated through each student record to map a field in each specific column for student ID, email, course name, and role based on the format required in the LMS API. The logic that was built handled different user roles; if a record indicated a teaching assistant, the workflow sent them specific permission in the LMS, and if it was a standard student, they would be assigned the standard access.

The workflow sent formatted data to the LMS API so that we could create or update enrollments. If an API call failed due to any issues such as invalid email format, Tray.io's error handling branch caught the failure, isolated this specific record, and sent us a notification in our Slack channels with the error details, allowing us to manually fix it while the rest of the batch could sync without any interruption.

In our specific use case, several features stood out particularly strong from Tray.io. There is a robust loop and data helpers when dealing with large datasets of student data. The payload structures are rarely flat; we would have nested objects throughout. Tray.io offers highly capable helpers that allow for detailed data manipulation, making the passing of nested JSON data much simpler and easier. There is comprehensive error handling and branching for business-critical workflows such as student enrollments; an important feature is that Tray.io allows us to configure advanced error handling paths for individual steps within a workflow. We can easily set up a try-catch block to define exactly what should happen when API calls fail, and based on that, we can set up the route to alert the team via Slack, which is what we are currently doing. The connector SDK is also very nice; it has a large library of pre-built connectors that can connect a lot of proprietary internal tools directly into Tray.io, allowing the developer to build, test, and deploy custom connectors using Node.js and integrate the data directly into Tray.io.

During our three to six-month evaluation pilot, automating our student enrollment sync with Tray.io delivered proper operational improvements. We reduced our manual data entry and verification work for the operations team by approximately 10 to 15 hours per week during peak registration periods. There were fewer system errors because the system-to-system data mismatch errors were reduced to near zero during our test runs. There were still issues where the student entered the wrong input; these cases were being tracked using error handlers. The pilot proved that automated near-real-time sync was feasible for our infrastructure, helping shape our long-term automation and data integration strategy.

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.

I have been working in my current field for almost four and a half to five years.

Tray.io is pretty stable.

It is quite easy to scale.

We never had a chance to interact with customer support directly.

We did not use a solution previously; we started using a different solution after using Tray.io.

We evaluated Integromat and other apps as well, but Tray.io did stand out.

I give Tray.io an eight out of ten rating mostly because of how it is developer-centric and lacks a low-code platform and the pricing. The reduction in manual data tasks had a direct positive impact on our team's daily focus. Instead of spending hours manually cross-referencing registration spreadsheets and troubleshooting discrepancies between our student databases and the LMS, our operation team directed their time towards high-priority student support. Specifically, during busy intake periods, they were able to focus on resolving complex student billing inquiries, improving onboarding material, and handling edge cases for registration requests much faster. The platform is definitely a value and worth considering for implementation.

Private Cloud

Other

My main use case for Tray.io is to conduct A/B testing for marketing initiatives that the company has undertaken. We test the deployment of different campaigns across similar cohorts and evaluate which one performs better.

Tray.io fits into my A/B testing process by analyzing the number of words used by consumers in comments and the number of times they stopped campaign videos at specific points. Through this analysis, we can investigate the attention levels of users and determine what thoughts are elicited by the campaign.

I have found that the error management in my main use case with Tray.io is not as effective as we would prefer. We would appreciate having a way to recycle cases that do not carry much value. Every user is precious in their own way, and even if a user does not provide much information, we would still value the ability to extract some information from those boundary cases.

The best features Tray.io offers include excellent visualization capabilities and a dashboard, which stand out to me the most.

I appreciate that it is very easy to convert the data we receive from Tray.io into dashboards from Power BI, which is extremely useful. I would also appreciate if in the future Tray.io provides a way to natively convert the data to Tableau.

Tray.io has positively impacted my organization as it provides a trusted way to organize data results and share them throughout the company at once. As a multinational and very large company, it is definitely beneficial that those of us in the UK can use the same format that colleagues use in India, and the entire data architecture is framed within a trusted system from an established organization. As far as I know, Tray.io has been operating for the last 12 years, making it a very reliable system.

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.

I started using Tray.io approximately one year ago.

In my experience, Tray.io is stable, as we have never experienced issues with it failing or being unavailable. We did not experience any downtime, compatibility issues, or system issues at all.

The scalability of Tray.io is quite good. We were able to deploy it from a small company within Tata with 200 people to what is now a multinational company with 92,000 people globally, and the people involved in using Tray.io number in the hundreds. I believe the scalability is quite good.

I have never used the customer support for Tray.io because the software is very easy to use and we never needed to contact support. However, I can tell you that the support provided through newsletters and update bulletins is quite good.

Previously, we attempted to develop an in-house solution as a company proprietary system, but we failed to achieve a good standard and quality level with that approach. We therefore looked for an established solution.

I have seen a return on investment as the company has been renewing the product for the entire 19 months we have been using it, which indicates that trust is high and they likely see value and advantage in using the system. There are no complaints in this regard.

My experience with pricing, setup cost, and licensing for Tray.io is that I did not personally follow the pricing negotiation, but I understand that the company pays a monthly fee which is very competitive. No one has complained in the finance department, and it is very rare for Tata Motors to refrain from complaining about pricing.

A few options were evaluated before choosing Tray.io, but I cannot recall which ones were proposed to me because Tray.io was identified as the most valid option since the very beginning.

My advice to others considering Tray.io is to trust the process because once the installation is complete, it is extremely easy to deploy and set up.

I have rated this product an eight out of ten.

Private Cloud

Microsoft Azure

Tray.io serves as the core iPaaS orchestration and data ingestion engine between our primary system and numerous external platforms such as ad servers like GAM, FreeWheel, Flitepath, Facebook, ERPs like SAP S/4HANA, and custom reporting MDR workflows.

We use Tray.io for scheduled daily reporting data imports, as our adjuster report trigger that runs at 2:00 AM New York time. Tray checks for active integrations, makes automated API calls to pull reporting CSVs, processes JWT tokens, transforms payloads, and ingests actualized billing and track data back into our databases and Looker analytics.

The best features Tray.io offers include the visual workflow builder and HTTP client blocks that enable rapid prototyping and deployment of complex API interactions, including raw HTTP requests, data mappers, and dynamic token generation. I also appreciate Tray Forms that allow us to create self-serve import forms, such as menu MDR forms, rate updates, and cost updates, which empower non-technical users and client partners to trigger automated ingestion pipelines safely. Additionally, callable workflows and subroutines are essential for modular architecture design, allowing us to build single-purpose, reusable workflows that can be triggered by parent workflows.

Coupled with our Looker analytic dashboards, the visual workflow builder and HTTP client blocks are a hugely underrated combination. This allows us to remove technical operation teams from middleman tasks by giving non-technical staff or clients a safe UI to submit CSV updates that execute complex API loops under the hood.

Native rate limit and auto-retry handling can be improved, as when hitting 429 errors or too many requests errors during high-volume API loops, Tray.io lacks native configured backoff and retry logic out-of-the-box, requiring complex custom while-loop workarounds. Native workflow versioning also needs improvement since there is no direct integration with GitHub version control for workflow logic, which forces teams to maintain external Git repositories or manual project exports. Additionally, deeper workspace organization should be enhanced, as the workspace organization currently limits to two structural levels, such as projects and workflows, which can make managing hundreds of client workflows challenging without strict external naming conventions.

Native UI embedding or white-labeling capabilities for Tray Forms would also be a major improvement, allowing us to embed forms directly inside third-party application iFrames seamlessly without directing users away.

I have been using Tray.io since I joined the company in 2021.

Tray.io is highly stable for daily scheduled production runs and event-driven webhooks, provided proper error handling, timeout management, and payload validation are built into the workflow steps.

Tray.io has drastically reduced manual bulk operations across our data solutions and integrations teams, transforming multi-step manual data compares and script executions into turn-key event-driven or scheduled workflows.

Tray.io is a flexible, scalable, and powerful integration platform. Our company uses it for handling high-volume data ingestion and integration orchestration between our platform and external ad services, and it maintains stability and reliability.

The ROI is clear, as it eliminates hundreds of engineer hours required to build and maintain custom integration connectors, while empowering client partners to manage complex data ingest self-sufficiently.

My advice for others looking into using Tray.io is to modularize earlier. I recommend not building massive monolithic workflows, but rather creating single-purpose callable workflows and triggering them from parent workflows. Use environment configurations and never hard-code credentials, tokens, or base URLs inside individual connectors. Use account-level configuration data with environment prefixes and design for rate limits. If calling external APIs with strict rate limits, implement batching, pagination, and queue locking mechanisms to prevent queue overloads or HTTP timeout spikes.

When we started using Tray.io, our primary challenge was automating high-volume, multi-tenant ad server delivery reports, campaign synchronizations, and manual CSV imports without forcing engineering to build custom code for every client integration. Tray.io was selected to provide a flexible visual automation platform capable of handling webhooks, complex data transformation, and HTTP endpoint orchestration across both internal workflows and client-facing embedded workspaces. Tray.io has been excellent for that purpose and remains highly stable. I would rate this product an overall 8 out of 10.

Public Cloud

Amazon Web Services (AWS)

My main use case for Tray.io is creating workflows to work with our Zendesk and our other application services.

A specific example of a workflow I have set up with Tray.io is that we use our employee tracking system to bring that information over to Zendesk every time an employee is hired or updated. One in particular would be signature change updates for their emails; when they make a change with HR, Tray.io provides the information over to Zendesk for our Zendesk ops team to make those changes.

Setting up that workflow presented some challenges; Tray.io is not necessarily the easiest platform to work with. We have been using it for a while, and some were set up before I started with the company, so tweaking them can take a little bit of work. It is quite a learning curve even with their academy, but once we get it up and going, it functions fine. The biggest issue we have with Tray.io is that it runs out of memory space and does not process all of our workflows.

If it is not just those basic things, it is primarily the system we use to communicate between all of our other systems.

The best features Tray.io offers include the drag-and-drop workflow builder that makes it a lot easier, and I think the automation capabilities are good. However, I feel that we would like it to be a little bit better, but we are making it work.

Tray.io has positively impacted my organization by eliminating a lot of the manual work that we were having to do daily. It has given our team opportunities to work on different projects, and the automation that Tray.io provides saves us a lot of time and solves some of the issues that we were having prior to using it.

I use the drag-and-drop builder across the board; we do the same process for all of our workflows that we have, so it is not one in particular that stands out. All of our workflows are pretty much the same: look at this, bring back this, bring back that, send it to here so that we can send it over to this system. We try to keep it as simple as possible.

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.

I have been using Tray.io for three years.

Setting up that workflow presented some challenges; Tray.io is not necessarily the easiest platform to work with. We have been using it for a while, and some were set up before I started with the company, so tweaking them can take a little bit of work. It is quite a learning curve even with their academy, but once we get it up and going, it functions fine. The biggest issue we have with Tray.io is that it runs out of memory space and does not process all of our workflows.

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 estimate that we save over 40 hours a week thanks to Tray.io's automation, as it has even eliminated a position on our team because that person was no longer needed once we started the automations.

Honestly, I am not sure that we have used anything that really shows how AI helps us with Tray.io at this point. We are still at the basic level of just doing the very basics and have not used any AI features on it to really improve it.

My advice to others looking into using Tray.io is that when you are getting ready to start using it, make sure that you are aware of the technical capabilities of the person that will be administrating it to ensure it matches the work that needs to be done. I would also say that if there are any automated workflows that AI can provide with Tray.io, that would be great to know because we are not necessarily using that; we do it all manually.

I provided a review rating of five for Tray.io.

Private Cloud

Other

Tray.io's main use case for my organization is workflow automations related to user onboardings, license reconciliation, and a myriad of other tasks to improve redundant processes.

An example of a workflow that I automated with Tray.io was during a user email migration where this specific workflow would place individuals being migrated from an offshore email address to our corporate email address into a Slack message saying, 'Hey, we're getting you onboarded with a new email address', and putting them in a specific Slack channel, involving a lot of webhooks and communications.

Tray.io has positively impacted my organization by reducing the amount of redundant tasks that our team performs by approximately 80%, and the numbers are quite significant with the workflows alone, as we are working towards creating and utilizing AI within these workflows as well.

The 80% reduction in redundant tasks was measured based on the time saved, primarily for onboarding processes. We use a lot of offshore work, and Tray.io helps keep us organized in that sense.

I appreciate that Tray.io is low-code automation, meaning you do not have to be an expert in JSON to understand the components and create automations.

The best features that Tray.io offers include a lot of API connections, and we use it for Slack, with Airtable being our data and low-code database that also handles automations, where we store information. You can also connect to G Suite and many different types of environments that can be automated.

One way Tray.io could be improved, especially for people coming in with no real coding experience, is with more comprehensive error messages. When an automation fails, it usually provides the JSON format, and if Tray.io could include a summary of what the actual error entails, that would be quite beneficial.

I have been using Tray.io for approximately eight months.

In my experience, Tray.io is stable, considering the number of workflows we automate. I would say it is quite stable.

Tray.io's scalability is highly effective, given the amount of workflows we generate.

As for return on investment with Tray.io, I have reduced approximately 80% of our redundant tasks through Tray.io alone.

I found that Zapier is the only real similar platform to Tray.io, though in terms of scalability, Tray.io is the better option. Zapier does offer a free tier, but it does not meet the demands of a scaling company.

I would rate Tray.io overall about a seven, give or take, with a consideration of seven and a half. I chose seven for my rating mostly for cost-related reasons as I would not really recommend it for smaller companies or startups. Zapier would be a more beneficial solution for those, but if you are looking to scale up, I think it is worth the price, which is the only reason I would give it a seven rating. My overall review rating is seven.

The learning curve for new users on Tray.io is somewhat noticeable, as when you first log on having never used a low-code platform, you need to take the time to really learn how the workflows are deployed and how to connect everything. However, once you are using it every single day, it is quite easy to catch up, though there is still a bit of a learning curve.

Tray.io integrates fairly well with our existing tech stack, as we utilize Okta, Slack, Google Cloud platforms, AWS, and a multitude of software-as-a-service applications, and Tray.io automates many of these. From my experience alone, it helps with onboardings, offboardings, and title changes.

Public Cloud

Google

We run automation workflows with Tray.io to take data from our internal databases and update a third-party software that we use. Specifically, my company offers digital trade credit, and we use that software to support our collections processes.

At a high level, our systems call a webhook in Tray.io. The workflows in Tray.io then triage and process the incoming data, and finally makes API calls to the third-party service to modify objects.

I appreciate the logging features that Tray.io offers, as it is fairly intuitive to use. It is also fairly straightforward to customize debugging messages if needed.

The logging and debugging features in Tray.io have helped us considerably, especially when dealing with APIs that return errors sometimes. Errors could be a configuration issue on our side or 500 errors, and being able to go through each of the workflow steps and see what the outputs were at that particular point has been quite useful for us in terms of making our workflows more resilient and understanding what has gone wrong.

Tray.io has positively impacted my organization by helping us automate both the development and maintenance work that is needed to keep our internal database and this third-party service in sync.

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.

I have been using Tray.io for about two years.

Tray.io is stable in my experience.

As our product got more complex, we needed to adapt our Tray.io setup to match that, and that was when the benefits of it being no-code or low-code started to pale in comparison to the cost of making everything slightly more complicated. Given the limited time we have invested in it, I would say Tray.io was fine for us in terms of processing larger volumes, but it was less smooth-sailing when it came to increasing complexity.

The customer support from Tray.io is adequate. It is not great, but not terrible in my memory.

I am not in a position to comment on seeing a return on investment, but instead of paying Tray.io, we could have spent more of our engineers' time.

I think in general it has been a positive experience with Tray.io, and while there are areas where it can be improved, overall it is a good product. I rate Tray.io a seven out of ten.

My main use case for Tray.io is webhook functionality. We send webhooks from our application to Tray.io and then run workflows from Tray.io to our different use cases to send data to multiple other applications.

The best features Tray.io offers are debugging, detailed instruction, multiple webhook configuration, workflow items, and flexibility to add logics.

Out of those features, I find myself using logic and debug the most, and they have been the most valuable in my day-to-day work.

Tray.io has positively impacted my organization by helping to manage webhooks easily and workflows easily, and it has improved collaboration so that other clients can use webhooks.

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 have been using Tray.io for two years.

Tray.io is stable in my experience.

Tray.io's scalability is very good. It can be scaled very fast.

I have never had the opportunity to interact with customer support, but it should be good.

I have not used a different solution before Tray.io.

Tray.io is deployed in my organization on a public cloud. We use Tray.io itself, so there is no specific deployment. I did not purchase it myself. I think it was purchased directly from Tray.io.

I have not evaluated other options before choosing Tray.io.

I rate Tray.io an eight out of ten overall.

I gave Tray.io an eight out of ten because of minor improvements needed, some feasibility to manage and configure solutions, and a need for more flexibility to make it a ten.

Regarding Tray.io's AI capabilities, I have not used them.

I have not used Tray.io's AI capabilities regarding accuracy and reliability of output, but when I did use it, it gave me the results.

My advice to others looking into using Tray.io is to consider it, as it is a good tool that people can use. I gave this review a rating of eight out of ten.